Conversation
We also need a feature flag around the definition of the command in CLI so that a plugin can pick it up (or just call This also requires a |
5314137
to
e825843
Compare
|
e825843
to
60423a5
Compare
☔ The latest upstream changes (presumably #5995) made this pull request unmergeable. Please resolve the merge conflicts. |
@indirect thoughts? |
@segiddins This works for me. If @colby-swandale is too busy to finish it, can you rebase it and fix the bool key thing? |
60423a5
to
0b04562
Compare
Bye-bye @bundlerbot r+ |
📌 Commit 0b04562 has been approved by |
deprecate the bundle viz command ### What was the end-user problem that led to this PR? The `bundle viz` command is to been removed from bundler 2 and extracted into a plugin Closes #5180 ### What is your fix for the problem, implemented in this PR? Deprecate the `bundle viz` command with an error explaining that a new gem will replace it's functionality.
☀️ Test successful - status-travis |
deprecate the bundle viz command ### What was the end-user problem that led to this PR? The `bundle viz` command is to been removed from bundler 2 and extracted into a plugin Closes #5180 ### What is your fix for the problem, implemented in this PR? Deprecate the `bundle viz` command with an error explaining that a new gem will replace it's functionality. (cherry picked from commit dbb0aed)
deprecate the bundle viz command ### What was the end-user problem that led to this PR? The `bundle viz` command is to been removed from bundler 2 and extracted into a plugin Closes #5180 ### What is your fix for the problem, implemented in this PR? Deprecate the `bundle viz` command with an error explaining that a new gem will replace it's functionality. (cherry picked from commit dbb0aed)
* 1-17-stable: (38 commits) Version 1.17.0 with changelog Merge #6754 Version 1.17.0.pre.2 with changelog fix failing bundle remove specs Still document the `--force` option scope specs testing bundler 2 deprecations to bundler 1 only Merge #6718 Merge #6707 Merge #6702 Merge #6316 Auto merge of #6447 - agrim123:agr-update-error-message, r=segiddins Auto merge of #6513 - agrim123:agr-bundler-remove, r=indirect Auto merge of #6318 - jhawthorn:fix_incorrect_test_in_requires_sudo, r=segiddins Auto merge of #6450 - bundler:segiddins/bundle-binstubs-all, r=colby-swandale Auto merge of #6024 - gwerbin:custom-user-bundle-dir, r=colby-swandale Version 1.17.0.pre.1 with changelog Auto merge of #5964 - bundler:colby/deprecate-viz-command, r=segiddins Auto merge of #5986 - bundler:seg-jobs-count, r=indirect Auto merge of #5995 - bundler:seg-gvp-major, r=indirect Auto merge of #5803 - igorbozato:path_relative_to_pwd, r=indirect ...
What was the end-user problem that led to this PR?
The
bundle viz
command is to been removed from bundler 2 and extracted into a pluginCloses #5180
What is your fix for the problem, implemented in this PR?
Deprecate the
bundle viz
command with an error explaining that a new gem will replace it's functionality.