[TypeSpec to SDK release] Cases we should block user to create the 2nd release plan
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 130
Description
Azure Policy created two release plans for Beta release. However per offline communication, service team has confirmed they want the release on both 2026-01-01-preview for Beta and 2026-07-01 for GA.
[Release plan #35307](https://azsdk-releaseplan-dashboard-hveph5aqhhcfhtgu.westus-01.azurewebsites.net/?filter=35307)
[Release plan #36262](https://azsdk-releaseplan-dashboard-hveph5aqhhcfhtgu.westus-01.azurewebsites.net/?filter=36262)
Even when release plans target different API versions of the same resource provider (RP), creation of a second release plan should be blocked in the following cases:
• No API version is specified. If regeneration is triggered, the default API version may change and cause duplicate releases.
• An older API version is specified while SDK pull requests already exist for a newer version. Releases based on an older API version should always be blocked.
By doing so, there could be no more cases like Azure Policy.
Contributor guide
Assessment
This issue has not been assessed yet.