You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bootboot doesn't work well with new Bundler versions (>= 2.5.10) #69
When using bundler >= v2.5.10, running bundle update will not update the next lockfile and running --conservative will generate more changes than necessary.
Bootboot reads Bundler::Definition's @unlock hash via instance_variable_get and uses it to keep Gemfile_next.lock in sync. In Bundler 2.5.10, the :gems and :sources keys get delete'd out of @unlock during Definition#initialize (moved into separate ivars), so by the time Bootboot reads it it no longer contains the list of updated gems.
Activity
tjvc commentedon May 26, 2026
Just adding a note on the root cause here:
Bootboot reads
Bundler::Definition's@unlockhash viainstance_variable_getand uses it to keepGemfile_next.lockin sync. In Bundler 2.5.10, the:gemsand:sourceskeys getdelete'd out of@unlockduringDefinition#initialize(moved into separate ivars), so by the time Bootboot reads it it no longer contains the list of updated gems.