Same-version API check (Swagger BreakingChange) should add VersioningReviewRequired instead of BreakingChangeReviewRequired when detecting issues on preview versions (as opposed to GA) (breaking changes confusion matrix)
#7724
Assignees
Labels
Breaking Changes
Improvements to Breaking Changes tooling
Central-EngSys
This issue is owned by the Engineering System team.
Spec PR Tools
Tooling that runs in azure-rest-api-specs repo.
Comments
konrad-jamrozik
added
Central-EngSys
This was referenced Feb 28, 2024
konrad-jamrozik
changed the title
Swagger BreakingChange) should add VersioningReviewRequired instead of BreakingChangeReviewRequired when detecting issues on preview versions (as opposed to GA)Swagger BreakingChange) should add VersioningReviewRequired instead of BreakingChangeReviewRequired when detecting issues on preview versions (as opposed to GA) (breaking changes confusion matrix)
31 tasks
|
I think I might have actually completed this already - I nee to double check the source. Update: not yet done |
konrad-jamrozik
added
the
Breaking Changes
|
github-project-automation
bot
moved this from 🐝 In Progress
to 🎊 Closed
in Spec PR Tools
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As in subject. Conversation in
breaking_changes_confusion_matrix.pptx.The goal is to make sure that the bottom left rectangle in the following diagram is
VersioningReviewRequiredinstead of the currently deployed implementation ofBreakingChangeReviewRequired:Related file:
BreakingChangeRules.ymlRelated prerequisite work in-flight:
The text was updated successfully, but these errors were encountered: