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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Be aware that declaring
expiration
indeprecate_info
will break the release pipeline if it is forgotten: #27792.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's by design because I won't want to miss next breaking change window.
And as you may noticed, I didn't leverage the upcoming breaking change framework
azure-cli/src/azure-cli-core/azure/cli/core/breaking_change.py
Lines 584 to 586 in b3199bd
And @ReaNAiveD said that I will lose version info if I use default old
deprecated_info
rather thanregister_command_group_deprecate
. That's another reason I explicitly declareexpiration
here