Skip to content

fix: faraday dependency version #67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

fix: faraday dependency version #67

wants to merge 1 commit into from

Conversation

CiTroNaK
Copy link

@CiTroNaK CiTroNaK commented Feb 7, 2020

Related with #55

I was not able to install it due to conflict with another gem that uses faraday.

@PikachuEXE
Copy link

If gem author is not comfortable for not testing with multiple versions of gems

appraisal can be used
Example: https://github.com/fnando/i18n-js (Appraisals & Rakefile)

@sabman
Copy link
Member

sabman commented Apr 17, 2020

I'll need to merge this into a version branch and release as master has move on to faraday 1.0

@sabman
Copy link
Member

sabman commented May 16, 2020

I'd like to get this into a version 0.0.x branch and release 0.0.8. However, I'm not quite sure how to maintain two parallel version branches. Anyone know any best practices guide out there for this?

If not I was gonna branch off the pre release 1.0.0 commit 1c94223 call the branch version-0.0.x then merge this in and release a new version. What do people think?

@dividinglimits
Copy link
Contributor

This PR should be closed as outdated release 1.0.1 upgrades the faraday dependency.

@sabman sabman closed this Aug 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants