Expand list of gems to install to work around conservative update #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some gems are "meta gems" that are composed of other gems locked at identical versions. For example, rails 7.0.4.3 requires activesupport =7.0.4.3, railties =7.0.4.3, and so on.
Therefore, running
bundle update --conservative rails
may not work depending on how strictly Bundler enforces "conservative" (this behavior is also slightly different in different Bundler releases). In this case, you might see a message from Bundler like:With this commit,
update-interactive
solves this problem by updating the entire suite of gems when a "meta gem" is selected for update. In other words, if you pick rails from the list of gems to update,update-interactive
will automatically include activesupport, railies, etc. as well, ensuring that the update is successful.