-
Notifications
You must be signed in to change notification settings - Fork 1k
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.
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
Update bundler module to ruby 3.3.3 #10038
Conversation
I think we'll also want to upgrade the actual version of Ruby that Dependabot uses? |
Hi @jurre, I've bumped the ruby version. Successfully rebuilt the updater-core image locally and ran a few specs to confirm it's working. I also built and ran a devcontainer successfully. I'm not sure if any further testing is needed? |
07f9350
to
acc7917
Compare
bundler/helpers/v2/monkey_patches/definition_ruby_version_patch.rb
Outdated
Show resolved
Hide resolved
bundler/helpers/v1/monkey_patches/definition_ruby_version_patch.rb
Outdated
Show resolved
Hide resolved
98cb6d7
to
ad0edb9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! ✅
Ruby 3.3.3 currently suffers from a bug where it causes bundler to remove the dependency of
Would this imapct dependabot updates? I can't tell if the tests would cover that case, or if it just irrelevant |
Great catch! I'm not fully sure if Dependabot would be affected, but it's certainly possible. I guess the issue can be tested through the CLI with a lockfile that includes these gems. The issue can be patched in the Dockerfile by manually fixing the affected gems, but we may also hold the internal Ruby upgrade ( |
In that case I've reverted this PR to its original purpose, hopefully we at least run dependabot on projects running 3.3.3 |
https://bugs.ruby-lang.org/issues/20581#note-2 contains diffs that would need to be applied for this to certainly not be a problem anymore. That would need to be applied to the gemspecs shipped with ruby by default, though I can't tell for certain where they are located. The best thing would probably to add a test lockfile containing |
I agree with @Earlopain that it's easier to wait to 3.3.4, rather than taking the time to verify if the issue affects Dependabot and if it does, to figure out the right files to patch and apply the proper patches directly from the Gemfile. This PR already allows projects using Ruby 3.3.3 to use Dependabot, so I think it's good to go without blocking on Dependabot upgrading the version it runs itself. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @DuncSmith !
And thanks for the review @deivid-rodriguez , I'm basically treating it as the necessary approval here. 😁
only one version per minor release needed and this is provided by the current ruby
This reverts commit 49845fafbd2f5cd280cb107d072a9f6028124b54.
After upgrading our rails app to ruby 3.3.3, we started to get Dependabot::Bundler::FileUpdater::RubyRequirementSetter::RubyVersionNotFound errors
This change updates the ruby requirement to 3.3.3
Trace