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.

Sign up for GitHub

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

Jump to bottom

CI Failures - often Bundler/RubyGems, not setup-ruby #562

Closed
MSP-Greg opened this issue Aug 9, 2023 · 1 comment
Closed

CI Failures - often Bundler/RubyGems, not setup-ruby #562

MSP-Greg opened this issue Aug 9, 2023 · 1 comment
Labels
🤖 dependencies Dependency upgrade ✅ accepted The core team has agreed that it is a good idea to fix this

Comments

@MSP-Greg
Copy link

MSP-Greg commented Aug 9, 2023

🤔 What's the problem you've observed?

Failing CI, due to older Rubies and the Bundler/RubyGems versions that are included with them.

✨ Do you have a proposal for making it better?

One option is MSP-Greg@8a27f20. That forces a RubyGems upgrade for all Rubies. You may want to implement finer control than that, and just upgrade for Ruby 2.6.

📚 Any additional context?

See comments in:
#560
#561

and issue ruby/setup-ruby#518 (comment)
@MSP-Greg MSP-Greg changed the title CI Failures - often Bundler/RubyGems, not setup/ruby CI Failures - often Bundler/RubyGems, not setup-ruby Aug 9, 2023
@luke-hill luke-hill added 🤖 dependencies Dependency upgrade ✅ accepted The core team has agreed that it is a good idea to fix this labels Aug 10, 2023
@luke-hill
Copy link
Contributor

Fixed - will be all good in v3.0.0.rc.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🤖 dependencies Dependency upgrade ✅ accepted The core team has agreed that it is a good idea to fix this
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MSP-Greg @luke-hill