Load bundled gems on expected version #859
Merged
+20
−80
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
xjunior
force-pushed
the
setup-bundled-gems
branch
from
ad1355c to
79bd2ed
Compare
|
I have this issue and it resolved it for me. |
|
Thanks! |
|
Released in 0.65.0. |
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.
Fixes #789
psychis no longer a default gem, but current and old ruby still ships with it. When werequire 'yaml', we activate that gem in whatever version that is bundled with ruby. Later on, we load bundler, and weBundler.setup, which will then activate whatever version specified in the lock file. More often than not, they might not match.The approach in this PR is to strip the
yamldependency completely from the hook scripts, while retaining the ability to configure the Gemfile using it.