Repository navigation
Clarify Azure policy for new-version RequiredStatusChange findings - #542
Merged
Timothee Guerin (timotheeguerin) merged 6 commits intoOct 13, 2026
Merged
Timothee Guerin (timotheeguerin) merged 6 commits into
Timothee Guerin (timotheeguerin) merged 6 commits into
Conversation
|
Azure Pipelines: Successfully started running 1 pipeline(s). There may be pipelines that require an authorized user to comment /azp run to run. |
Co-authored-by: jianingwang123 <141212663+jianingwang123@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Clarify RequiredStatusChange guidance for new-version response
Clarify Azure policy for new-version RequiredStatusChange findings
Oct 9, 2026
Jianing Wang (MSFT) (jianingwang123)
marked this pull request as ready for review
October 9, 2026 06:34
| **Description**: Checks whether an existing property's `required` status is changed from the previous specification. | ||
|
|
||
| **Cause**: This is considered a breaking change in the same api-version but not breaking in new api-version . | ||
| **Cause**: Under this rule's semantics, this is considered a breaking change in the same api-version but not in a new |
There was a problem hiding this comment.
I do find that part kind confusing still, why do we mention it is not a breaking change but right after says well maybe it is.
Should we say it is 100% a breaking change in the same api version but depends on a new api version
There was a problem hiding this comment.
Copilot pls update the doc based on this comment
Contributor
Author
There was a problem hiding this comment.
Updated in 0f0998f: the cause now states that requiredness changes are breaking in the same API version, while new-version treatment depends on wire-contract impact and Azure REST API policy. Removed the categorical claim that new-version changes are non-breaking.
Co-authored-by: jianingwang123 <141212663+jianingwang123@users.noreply.github.com>
Co-authored-by: jianingwang123 <141212663+jianingwang123@users.noreply.github.com>
Co-authored-by: jianingwang123 <141212663+jianingwang123@users.noreply.github.com>
Timothee Guerin (timotheeguerin)
approved these changes
Oct 13, 2026
Timothee Guerin (timotheeguerin)
deleted the
copilot/clarify-requiredstatuschange-guidance
branch
October 13, 2026 13:38
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
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.
The 1025 rule page implied that requiredness changes are non-breaking whenever the API version changes. Azure policy can still require breaking-change review, so a new-version finding is not inherently a tooling/documentation mismatch.
RequiredStatusChangeas breaking; recommend review rather than suppression-first guidance without evidence of an incorrect finding.