SDK generation for Container Registry TypeSpec 2025-11-01 stable release

[Copilot]

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

• New resource provider.
• New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
• Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
• Update existing version to fix OpenAPI spec quality issues in S360.
• Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
• Other, please clarify:
  • SDK generation orchestration for Container Registry TypeSpec project API version 2025-11-01 (stable). No specification changes.

Overview

Automated SDK generation for Container Registry resource provider from existing TypeSpec specification at specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/Registry.

API Spec PR: #39455
Release Plan: Work Item 30544
API Version: 2025-11-01 (Stable)
Release Type: Stable (Do not release - service owner will release later)

SDK Generation Results

All pipelines completed successfully. SDK PRs created in respective language repositories:

Language	Pipeline	SDK Pull Request	Package
Java	Build 5777146	#47758	azure-resourcemanager-containerregistry-generated
JavaScript	Build 5777148	#37083	@azure/arm-containerregistry
Go	Build 5777147	#25900	sdk/resourcemanager/containerregistry/armcontainerregistry
.NET	Build 5777144	#55137	Azure.ResourceManager.ContainerRegistry
Python	Build 5777145	#44775	azure-mgmt-containerregistry

Release plan updated with SDK details. SDK PRs require review by respective language teams before merge.

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

• I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
• I have reviewed following Resource Provider guidelines, including
  ARM resource provider contract and
  REST guidelines (estimated time: 4 hours).
  I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
• A release plan has been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

• First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
  This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.
• For guidance on SDK breaking change review, refer to https://aka.ms/ci-fix.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[TypeSpec] Generate SDK for TypeSpec project specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/Registry</issue_title>
<issue_description>## SDK generate request for TypeSpec project specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/Registry

Request to generate SDK by Copilot. Do not release SDK
SDK will be released later by service owner.

Release Plan: 2058
TypeSpec project path: specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/Registry
API spec pull request link: #39455
SDK release type: Stable
API spec version: 2025-11-01
Spec Type: TypeSpec
Language: Java,JavaScript,Go,.NET,Python
Release plan work item ID: 30544

Contacts:
clarkporter

Comments:
Generate SDK using Github copilot

Generate SDK for the TypeSpec project and update the generated SDK details in the release plan using release plan work item. Generate a summary and update it back in the linked GitHub issue once SDK pull requests are generated.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [TypeSpec] Generate SDK for TypeSpec project specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/Registry #39783

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[github-actions]

Next Steps to Merge

⌛ Please wait. Next steps to merge this PR are being evaluated by automation. ⌛

Comment generated by summarize-checks workflow run.