Generate beta SDKs for ContainerRegistry 2026-01-01-preview TypeSpec spec

[Copilot]

Triggered SDK generation for all 5 languages against the merged TypeSpec spec at specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/Registry (API version 2026-01-01-preview, beta). All SDK PRs have been linked to Release Plan 2044 (work item 30176).

Generated SDK Pull Requests

Language	Package	SDK PR
.NET	Azure.ResourceManager.ContainerRegistry	azure-sdk-for-net#56401
JavaScript	@azure/arm-containerregistry	azure-sdk-for-js#37348
Python	azure-mgmt-containerregistry	azure-sdk-for-python#45312
Java	azure-resourcemanager-containerregistry	azure-sdk-for-java#48072
Go	sdk/resourcemanager/containerregistry/armcontainerregistry	azure-sdk-for-go#26040

SDKs are beta only — not to be released until service owner (@joshbaunach) approves.

Note (Go regeneration): A request to regenerate the Go SDK was received but could not be completed due to a transient "Bad credentials" error from the Azure DevOps pipeline service. Please trigger the Go SDK regeneration manually or retry the request once the credential issue is resolved.

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 triggered via Copilot for all 5 languages (JS, Go, .NET, Java, Python) against the already-merged spec PR #39535.

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: 2044
TypeSpec project path: specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/Registry
API spec pull request link: #39535
SDK release type: Beta
API spec version: 2026-01-01-preview
Spec Type: TypeSpec
Language: JavaScript,Go,.NET,Java,Python
Release plan work item ID: 30176

Contacts:
joshbaunach

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 #40649

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[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.

[tadelesh]

@copilot Regenerate Go SDK.

[Copilot]

@copilot Regenerate Go SDK.

I attempted to regenerate the Go SDK, but the pipeline trigger is currently failing with a "Bad credentials" error from Azure DevOps. This appears to be a transient authentication issue with the pipeline service. Please try triggering the Go SDK regeneration manually via the release pipeline, or retry this request once the credential issue is resolved.