Skip to content
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

Backport #1009 #1013

Closed
wants to merge 2 commits into from
Closed

Backport #1009 #1013

wants to merge 2 commits into from

Conversation

systemist
Copy link

@systemist systemist commented Aug 29, 2019

Description

This backports #1009 to v0.15.x. I'm not sure what the base branch should be since versions are just tags, so I left it as master. I just cherry-picked 27d9c93 onto v0.15.4.

Rationale

We use many third-party gems that effectively specify faraday < 1, so this allows us to continue to use those gems without warnings on Ruby 2.7 (assuming it's included in a v0.15.5 release).

@iMacTia
Copy link
Member

iMacTia commented Aug 31, 2019

Sounds reasonable.
The correct base branch for 0.15 is the one called 0.1x
If you branch out from that and cherry-pick again, the conflicts should go away.

@technoweenie technoweenie changed the base branch from master to 0.1x September 3, 2019 16:17
@technoweenie
Copy link
Member

I changed the base above to 0.1x, but I think it failed because it doesn't have our CI config. I'll work on that separately, and come back to this once I get CI working.

@technoweenie technoweenie mentioned this pull request Sep 3, 2019
@technoweenie
Copy link
Member

@Iakobos thanks again. I just pushed a 0.16.x branch for future backports. The actual v0.16.0 gem will be pushed today.

@systemist systemist deleted the backport-2_7 branch September 27, 2019 17:53
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.

None yet

4 participants