{Core} Update Next Breaking Change Release Version Number #30288
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
ReaNAiveD
requested review from
bebound,
calvinhzy,
evelyn-ys,
jiasli,
jsntcy,
kairu-ms,
necusjz and
zhoxing-ms
as code owners
️✔️AzureCLI-FullTest
|
|
Hi @ReaNAiveD, |
️✔️AzureCLI-BreakingChangeTest
|
Collaborator
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
microsoft-github-policy-service
bot
added
Auto-Assign
ReaNAiveD
modified the milestones:
December 2024 (2024-12-10),
November 2024 (2024-11-19)❗ Breaking change release ❗
bebound
reviewed
Nov 11, 2024
| logger = get_logger() | ||
|
|
||
| NEXT_BREAKING_CHANGE_RELEASE = '2.67.0' | ||
| NEXT_BREAKING_CHANGE_RELEASE = '2.73.0' |
Contributor
There was a problem hiding this comment.
We use 2.74 in this PR: https://github.com/Azure/azure-cli/pull/30091/files#diff-4e144054c791bf4f8c57a14e455f64cd81b89021be6075fc60f12d75002ac02bR42
Please double confirm the version number.
Member
Author
There was a problem hiding this comment.
I reached out to Yong regarding the next breaking change version number and received 2.73.0 as the response. I'm flexible with either 2.73.0 or 2.74.0, as I plan to update to the confirmed version as soon as it's finalized.
Contributor
There was a problem hiding this comment.
Find 2.73.0 in https://learn.microsoft.com/en-us/cli/azure/azure-cli-support-lifecycle too.
Hmm, #30091 might be wrong.
Contributor
There was a problem hiding this comment.
2.54.0 is 2023 ignite version, 2.61.0 is 2024 build version. They differ by 7 versions, weird.
Member
Author
There was a problem hiding this comment.
I think it's acceptable to merge this PR for now. We can create another PR once we have the finalized version.
bebound
approved these changes
Nov 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Related command
Description
Update the breaking change release version.
It is recommended to update the version during the breaking change window. This will help avoid any issues with pre-announcements that indicate changes will occur in the current version after relase.
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.