(deprecation) switched from 'bundle show' to 'bundle info', get rid o… #744
Conversation
This file contains 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
…f deprecation-warning
|
yeah, works fine on 1.17 and 2.0 :) |
|
v2.30.1 |
|
thanks a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…f deprecation-warning
Running with current version of bundler gives following message:
[DEPRECATED] use 'bundle info rspec-core' instead of 'bundle show rspec-core'As far as i can see the command is used to decide if we should use 'spec' or 'rspec'. The output of 'bundle info' changed slightly but only in case of success. In case of failure the output stays the same so i think it should be safe to just migrate. :)