[Breaking Change][PR Workflow] azure-rest-api-specs PR checks should block merge of preview and stable with same version date #7294
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
mikekistler
added
the
Spec PR Tools
konrad-jamrozik
added
the
Central-EngSys
konrad-jamrozik
changed the title
|
This is one of the many improvements to be made to breaking change detection. For more, see: and issues hyperlinked within. |
konrad-jamrozik
added
the
Breaking Changes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Azure Versioning and Breaking Changes Policy requires that the version-date of a preview version be later than the most recent stable version. However, this rule does not appear to be enforced by our current PR pipeline checks, since just two months ago Cosmos DB released a stable and preview version with the same date -- 2023-09-15 and 2023-09-15-preview.
The stable 2023-09-15 version was added in PR 25266 which merged to main on Sept 22.
The preview 2023-09-15-preview version was added in PR 25326 which merged to main on Sept 20.
Since the preview merged before the stable version, the stable version merge should have been blocked as violating the Azure Versioning policy.
The text was updated successfully, but these errors were encountered: