Fix bundle show --verbose and recommend it as an alternative to bundle show --outdated
#8915
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 tasks
deivid-rodriguez
force-pushed
the
deivid-rodriguez/improve-bundle-show-outdated-deprecation
branch
from
7042a7d to
5194659
Compare
deivid-rodriguez
changed the title
bundle list --verbose equivalent to bundle show --verbose and bundle show --outdated, and recommend it as a bundle show --outdated replacementbundle show --verbose and recommend it as an alternative to bundle show --outdated
|
Ok, just more little change. I realized We can later figure out a plan to deprecate |
deivid-rodriguez
force-pushed
the
deivid-rodriguez/improve-bundle-show-outdated-deprecation
branch
from
5194659 to
98d35d6
Compare
…ndle show --outdated`
We had actually cancelled this change. After a second look though, it does seem like a reasonable plan since `bundle list` makes more sense for listing gems, and `bundle info` makes more sense for showing info about a particular gem. `bundle show` is a strange mix of both. Let's schedule this for Bundler 5.
deivid-rodriguez
force-pushed
the
deivid-rodriguez/improve-bundle-show-outdated-deprecation
branch
from
98d35d6 to
7071a1e
Compare
|
There was a pending spec that was assuming that we'd remove |
deivid-rodriguez
deleted the
deivid-rodriguez/improve-bundle-show-outdated-deprecation
branch
deivid-rodriguez
added a commit
that referenced
this pull request
Sep 4, 2025
…e-show-outdated-deprecation Fix `bundle show --verbose` and recommend it as an alternative to `bundle show --outdated` (cherry picked from commit a49d940)
deivid-rodriguez
added a commit
that referenced
this pull request
Sep 9, 2025
…e-show-outdated-deprecation Fix `bundle show --verbose` and recommend it as an alternative to `bundle show --outdated` (cherry picked from commit a49d940)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What was the end-user or developer problem that led to this PR?
In #8913, I finally understood an old plan to remove
bundle show.bundle showis a bit confusing and we have more specific commands to do what it does. When passed a specific gembundle show <gem-name>, we havebundle infoas a better alternative. When not passed a specific gem, we havebundle listas a better alternative.We could eventually deprecate
bundle show, but we should make sure all functionality has some replacement. However,bundle show --outdateddoes not have abundle listequivalent.What is your fix for the problem, implemented in this PR?
This PR copies
bundle show --outdatedimplementation tobundle list --verboseand recommends that as an alternative in the deprecation message.Make sure the following tasks are checked