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

Try upgrading bundler on travis #244

Merged
merged 1 commit into from
Sep 15, 2017
Merged

Try upgrading bundler on travis #244

merged 1 commit into from
Sep 15, 2017

Conversation

jolynch
Copy link
Collaborator

@jolynch jolynch commented Sep 15, 2017

THis is a test to see if it fixes the 1.9 issue.

@jolynch
Copy link
Collaborator Author

jolynch commented Sep 15, 2017

Strange, not sure why this works (bundler is the same version before and after), but it does so ... strange

@jolynch
Copy link
Collaborator Author

jolynch commented Sep 15, 2017

Oh, yea, 1.7 vs 1.15, alrighty then.

@jolynch jolynch merged commit b1ef754 into master Sep 15, 2017
@greysteil
Copy link

greysteil commented Sep 15, 2017

FYI, the underlying issue here is that Bundler only introduced required_ruby_version in Bundler 1.11. As a result, with Bundler 1.7 you could get a bundle that didn't work with you Ruby version (e.g., a ActiveSupport 5.1.4 on Ruby 1.9).

Updating the Bundler version pre-install is exactly the right fix.

@panchr panchr deleted the fix_travis branch March 11, 2020 22:08
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.

2 participants