is Rails itself excluded, to allow interative 4.2, 5.0, 5.1, 5.2 upgrading?

thought-driven / bummr

Update your gems in separate commits. Identify any that fail your build.

MIT License

234 stars 23 forks source link

is Rails itself excluded, to allow interative 4.2, 5.0, 5.1, 5.2 upgrading? #62

Closed jpwynn closed 3 years ago

jpwynn commented 3 years ago

Starting a 4.2 -> 5.0 -> 5.1 -> 5.2 upgrade sequence, I was looking at bummr as a way to get the current non-rails gems updated prior to the jump to the next version.

Does/can bummr exclude Rails itself from the upgrade process, to support a .X at a time upgrade workflow?

s01ipsist commented 3 years ago

You could just pin the gems you don't want to move.

gem 'rails', '4.2.11.3'