Keep pre-3.0.0 command names as deprecated aliases - #83
Merged
Merged
Conversation
The 3.0.0 renames now warn on stderr instead of failing; the aliases go in 4.0.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
4 tasks done
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
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.
Features and Changes
The 13 commands renamed in #82 keep their old names as cobra aliases, so 2.x scripts still run on 3.0.0 and print a stderr warning naming the replacement. The aliases are slated for removal in 4.0.0. A test fails if a future regen renames an alias target. This ships as
3.0.0-next.1, ahead of stable.Testing
teams add-team-members --dry-run-> same request asteams add-members, plus the warning on stderrteams add-members-> no warning--jq/JSON output is unaffected