fix(containerregistry): added preview version decorator to properties incorrectly flagged as stable#39455
Conversation
… incorrectly flagged as stable
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.Comment generated by summarize-checks workflow run. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
|
@CodeJourneys could you wait for us to further confirm if there's any more additional preview features being added into the stable version? @kazrael2119 could provide further investigation result. |
|
Sorry for my mistake of introducing breaking changes when doing typespec conversion. |
|
@CodeJourneys Operation In your old swagger, you added this example under |
Thanks for the review @kazrael2119 and no worries about the miss. It's a good learning for all of us. I'm not sure I understand your question about the example file As far as I understand, in the PR to release 2025-11-01 stable, there was an orphaned examples file RegistryCreateAbac.json, which was present, but not referenced in the API swagger json, as shown here. However, in the latest version of the 2025-11-01 swagger, it is referenced as an example for Registries_Create (put). This reference was added in one of the Typespec conversion PRs, as shown here. Are you asking whether adding the reference as an example is okay, rather than intentionally leaving it orphaned? I'm not aware of any reason we would ever want an orphaned example, but perhaps I'm missing something. cc: @lizMSFT in case I may be missing context on the RegistryCreateAbac example specifically |
|
@kazrael2119 Thanks for catching this! We do need this example for Registries_Create: I missed including this example in the Swagger file previously |
|
@mcgallan told me that we have some description diff in 2025-06-01-preview during typespec conversion: 2: description in Do you have any concerns about these description diff? |
… JS-5777148 (#37083) Configurations: 'specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/Registry/tspconfig.yaml', API Version: 2025-11-01, SDK Release Type: stable, and CommitSHA: 'eb320d1d85f5b46c3cfe6cf60a1f0de4ef3b01d9' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5777148 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. **Release plan link:** [https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=1857cf38-61f6-f011-8406-000d3a5c46b0](https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=1857cf38-61f6-f011-8406-000d3a5c46b0) **Submitted by**: clarkporter@microsoft.com ## Release Plan Details - Release Plan: https://aka.ms/sdk-release-planner?release-plan-id=1857cf38-61f6-f011-8406-000d3a5c46b0 Spec pull request: Azure/azure-rest-api-specs#39455 Spec API version: 2025-11-01 --------- Co-authored-by: kazrael2119 <98569699+kazrael2119@users.noreply.github.com>
This PR corrects several properties in the ContainerRegistry control plane API specification that were missing the versioning decorator, incorrectly causing these preview properties to show as stable. These are corrected in this PR.