CI: Attempt to let ruby/setup-ruby pick Bundler, RubyGems #587
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
|
That was quick! Closing! |
|
Yeh there are numerous bugs here. I would avoid this if I were you. This will vanish once 3.0 becomes a minimum. I do appreciate it's not very well documented. |
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.
🤔 What's changed?
This PR changes CI to let ruby/setup-ruby decide which Bundler is right and works for a given Ruby version.
⚡️ What's your motivation?
I wanted the project to have fewer settings to maintain.
🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
If there were any specific context I am missing re: keeping a specific version.
📋 Checklist: