Sync eng\tools\js-sdk-release-tools directory with azure-sdk-tools for PR 15822

[skywing918]

Sync eng\tools\js-sdk-release-tools directory with azure-sdk-tools for PR Azure/azure-sdk-tools#15822

[github-actions]

🎯 Agentic Issue Triage

Summary: This issue requests a sync of the eng/tools/js-sdk-release-tools directory in the azure-sdk-for-js repository with the corresponding directory in azure-sdk-tools, referencing a specific upstream PR/issue.

📋 Issue Details

Package: eng/tools/js-sdk-release-tools (engineering tooling, not a published SDK package)
Affected API: Release tools / SDK release toolchain
Scenarios:

• Sync changes from azure-sdk-tools into the local copy of js-sdk-release-tools
• Ensure the release tooling in this repository is up to date with upstream changes in azure-sdk-tools#15822

Root ask: Sync the eng/tools/js-sdk-release-tools directory with the upstream azure-sdk-tools repository.

🔎 Debugging / Reproduction Notes

This is a tooling sync request, not a bug report. The work involves pulling changes from the azure-sdk-tools repository into this repository's engineering tooling folder.

Suggested investigation steps:

1. Review the changes in azure-sdk-tools issue/PR [Azure Container Registry]Move the Azure Container Registry package to use core-rest-pipeline #15822 to understand what needs to be synced.
2. Compare the current state of eng/tools/js-sdk-release-tools in this repo with the upstream version.
3. Apply the relevant changes and open a PR.

🏷️ Label Confidence

• Category: Central-EngSys — The issue is about engineering systems tooling in the /eng folder, not a service SDK package.
• Service: EngSys — This is about release tooling infrastructure, not an Azure service.
• Confidence: Low — The predicted category is Central-EngSys, which is excluded from automatic triage per policy. Falling back to needs-triage for manual review.

👥 Owner Routing

• Matched CODEOWNERS entry: None — Central-EngSys category is excluded from automatic triage.
• AzureSdkOwners: none listed
• ServiceOwners: none listed
• Routing action: Added needs-triage for manual review by the engineering systems team.
• Scan notes: No CODEOWNERS scan performed because the predicted category (Central-EngSys) is on the excluded list; triage deferred to human reviewers.

Generated by Agentic Triage for issue #38779 · ● 1.4M · ◷