Skip to content

Conversation

@deivid-rodriguez
Copy link
Contributor

What was the end-user or developer problem that led to this PR?

We may have been a little too aggressive here. Users running Ruby 2.7 which is still supported for a few months are getting this warning.

What is your fix for the problem, implemented in this PR?

Don't show the warning on Ruby 2.7. We can reintroduce this once Ruby 2.7 reaches end of life.

Make sure the following tasks are checked

We can reintroduce this once Ruby 2.7 reaches end of life.
@indirect
Copy link
Contributor

I think this is good, and it is ok to trail ruby-core a little bit on support. In the old days, we supported all the way back to Ruby 1.8, mostly because it benefits us to be able to upgrade even very old users to new bundler version fixes or improvements. 👍🏻

@deivid-rodriguez deivid-rodriguez merged commit d2da51c into master Dec 24, 2022
@deivid-rodriguez deivid-rodriguez deleted the undo-warning branch December 24, 2022 15:48
deivid-rodriguez added a commit that referenced this pull request Dec 24, 2022
Allow Bundler to run on old RubyGems + Ruby 2.7 without warnings

(cherry picked from commit d2da51c)
dentarg added a commit to spinels/overman that referenced this pull request Dec 25, 2022
Apparently the tests are sensitive to the output, like what happened in ruby/setup-ruby#420

Saw this option in ruby/rubygems#6187
dentarg added a commit to spinels/overman that referenced this pull request Feb 7, 2025
Apparently the tests are sensitive to the output, like what happened in ruby/setup-ruby#420

Saw this option in ruby/rubygems#6187
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants