Repository navigation
Bootboot doesn't work well with new Bundler versions (>= 2.5.10) #69
Description
Activity
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.Reacted by Brendan Weibrecht
When using
bundler >= v2.5.10, runningbundle updatewill not update the next lockfile and running--conservativewill generate more changes than necessary.