8e8ad6ff6c (master): [ruby/rubygems] Re-resolve when an override cuts a locked gem loose
0 views
Skip to first unread message
Hiroshi SHIBATA
12:30 AM (17 hours ago) 12:30 AM
to ruby...@g.ruby-lang.org
Hiroshi SHIBATA 2026-10-05 12:29:52 +0000 (Mon, 05 Oct 2026)
New Revision: 8e8ad6ff6c
https://github.com/ruby/ruby/commit/8e8ad6ff6c
Log:
[ruby/rubygems] Re-resolve when an override cuts a locked gem loose
Adding `to: nil` to an existing bundle left the dropped gem in the lockfile, because nothing marked the lockfile as changed. Frozen installs accepted that stale lockfile too.
https://github.com/ruby/rubygems/commit/6b3d576a8b
Co-Authored-By: Claude Opus 5.5 <nor...@anthropic.com>
Modified files:
lib/bundler/definition.rb
spec/bundler/install/gemfile/override_spec.rb
New Revision: 8e8ad6ff6c
https://github.com/ruby/ruby/commit/8e8ad6ff6c
Log:
[ruby/rubygems] Re-resolve when an override cuts a locked gem loose
Adding `to: nil` to an existing bundle left the dropped gem in the lockfile, because nothing marked the lockfile as changed. Frozen installs accepted that stale lockfile too.
https://github.com/ruby/rubygems/commit/6b3d576a8b
Co-Authored-By: Claude Opus 5.5 <nor...@anthropic.com>
Modified files:
lib/bundler/definition.rb
spec/bundler/install/gemfile/override_spec.rb
Reply all
Reply to author
Forward
0 new messages