Jump to last bundler version how doesn't break on CircleCI #2027
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
You mean TravisCI? 😂? |
|
Oups. My bad. This is what's happening when you work on both the same day. |
On bundle 1.16.3 we start seeing fail builds: - rspec#2013 (comment) This is related to: - rspec#2013 (comment) As mentionned this has been fixed in 1.16.4: - rubygems/bundler#6629 (comment)
benoittgt
force-pushed
the
bump_bundler_to_last_version_again
branch
from
06518ec
to
f14e2db
Compare
|
Easy slip :) |
JonRowe
added a commit
that referenced
this pull request
Oct 23, 2018
…again Jump to last bundler version how doesn't break on CircleCI
sebjacobs
pushed a commit
to futurelearn/rspec-rails
that referenced
this pull request
Mar 15, 2019
…sion_again Jump to last bundler version how doesn't break on CircleCI
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On bundle 1.16.3 we start seeing fail builds:
This is related to:
As mentionned this has been fixed in 1.16.4: