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

[skywing918]

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

[github-actions]

🎯 Agentic Issue Triage

Summary: This issue requests synchronization of the eng/tools/js-sdk-release-tools directory in this repository with changes from Azure/azure-sdk-tools PR #16224, following the same recurring pattern of cross-repo tooling sync requests.

📋 Issue Details

Package: N/A — engineering tooling (eng/tools/js-sdk-release-tools)
Affected API: N/A
Scenarios:

• Sync the local eng/tools/js-sdk-release-tools directory to incorporate upstream changes from azure-sdk-tools PR investigate clock skew support #16224

Root ask: Apply changes from azure-sdk-tools PR #16224 into the corresponding directory of this repository.

🔎 Debugging / Reproduction Notes

This is a cross-repo sync request, not a bug report. The referenced azure-sdk-tools PR contains changes to js-sdk-release-tools that must be reflected here.

Suggested investigation steps:

1. Review Azure/azure-sdk-tools#16224 to understand the scope of changes.
2. Compare eng/tools/js-sdk-release-tools in this repo against the changed files in that PR.
3. Apply the relevant file changes and verify any associated tests or scripts still pass.

Similar issues: This follows the same pattern as #38779, #39055, and other prior sync issues filed by the same author for different azure-sdk-tools PRs.

🏷️ Label Confidence

• Category: Central-EngSys (tentative) — The issue targets eng/tools/js-sdk-release-tools, which is squarely in the /eng folder and relates to release engineering tooling/infrastructure, matching the "Central-EngSys" definition.
• Service: EngSys (tentative) — Confirmed by similar issues Sync eng\tools\js-sdk-release-tools directory with azure-sdk-tools for PR 16143 #39055 and [js-automation] stop clearing package directory before SDK generation #36804 which carry the EngSys service label for the same directory.
• Confidence: Low — Central-EngSys is an excluded category label that requires human judgment and cannot be applied by automated triage. Because the predicted category is excluded, no category or service labels were applied. needs-triage was added for manual review.

👥 Owner Routing

• Matched CODEOWNERS entry: None — CODEOWNERS lookup was skipped because label prediction fell back to needs-triage (predicted Central-EngSys is an excluded category).
• AzureSdkOwners: None
• ServiceOwners: None
• Routing action: Added needs-triage for manual review by the team.
• Scan notes: CODEOWNERS scan not performed; no confident label pair was available to drive the scan.

Generated by Agentic Triage for issue #39141 · 37.9 AIC · ⌖ 10.8 AIC · ⊞ 10.2K · ◷