revert(pipeline): roll back CFS registry config in setup.yml to unblock releases

[Elaina-Lee]

Commit Type

• feature - New functionality
• fix - Bug fix
• refactor - Code restructuring without behavior change
• perf - Performance improvement
• docs - Documentation update
• test - Test-related changes
• chore - Maintenance/tooling

Risk Level

• Low - Minor changes, limited scope
• Medium - Moderate changes, some user impact
• High - Major changes, significant user/system impact

What & Why

The CFS registry routing added in #9453 breaks the ADO release pipeline at the very first install step. "Install pnpm" (npm install -g pnpm) now resolves against the CFS feed and fails with:

npm error code E401
npm error Unable to authenticate, your authentication token seems to be invalid.

so no pipeline run can get past setup. This PR rolls .azure-pipelines/templates/setup.yml back to its exact pre-#9453 state (removes the CFS registry append step, the NpmAuthenticate@0 task, and the npm_config_registry override on the pnpm install) to unblock releases. The SFI Network Isolation (SR21) work can be re-landed once feed authentication is sorted out.

The other two files from #9453 are intentionally left as-is: the 1esmain.yml branch pin was already reverted in #9474, and the .npmrc change was only a trailing-newline fix.

Impact of Change

• Users: None.
• Developers: None (local dev and GitHub Actions never used the CFS config).
• System: The ADO release pipeline restores packages from the public npm registry again, as it did before fix(pipeline): route npm/pnpm package restores through CFS for SFI Network Isolation (SR21) #9453. SR21/SFI compliance for the pipeline is deferred until the CFS auth issue is fixed.

Test Plan

• Unit tests added/updated
• E2E tests added/updated
• Manual testing completed
• Tested in: Verified setup.yml is byte-identical to its pre-fix(pipeline): route npm/pnpm package restores through CFS for SFI Network Isolation (SR21) #9453 version (git diff 6fcbd144^ -- .azure-pipelines/templates/setup.yml is empty after the revert). Pipeline-only YAML change, not exercised by GitHub CI; validate by queueing a release pipeline run after merge.

Contributors

Screenshots/Videos

[github-actions]

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

• Current: revert(pipeline): roll back CFS registry config in setup.yml to unblock releases
• Issue: None — this is a revert PR.
• Recommendation: No action needed. Revert PRs are auto-approved by policy.

---

✅ Commit Type

• This is a revert PR, so template checks are waived.
• No further action required.

---

✅ Risk Level

• Revert PR — risk checks waived. (For reference, the change is pipeline-only and low risk, consistent with the declared Low.)

---

✅ What & Why

• Current: Clear explanation that fix(pipeline): route npm/pnpm package restores through CFS for SFI Network Isolation (SR21) #9453's CFS registry routing broke the ADO release pipeline at the pnpm install step, and this rolls setup.yml back to its pre-fix(pipeline): route npm/pnpm package restores through CFS for SFI Network Isolation (SR21) #9453 state.
• Issue: None.
• Recommendation: No action needed.

---

✅ Impact of Change

• Users, Developers, and System impact are all documented.
• Recommendation:
  • Users: As stated — none.
  • Developers: As stated — none.
  • System: As stated — ADO pipeline restores from public npm registry again.

---

✅ Test Plan

• Revert PR — test checks waived. Manual verification (byte-identical to pre-fix(pipeline): route npm/pnpm package restores through CFS for SFI Network Isolation (SR21) #9453 setup.yml) is documented.

---

✅ Contributors

• Blank, but not required. Consider crediting reviewers if applicable.

---

✅ Screenshots/Videos

• Not applicable — pipeline YAML change with no visual impact.

---

Summary Table

Section	Status	Recommendation
Title	✅	Revert PR — auto-approved
Commit Type	✅	Waived for revert
Risk Level	✅	Waived for revert
What & Why	✅	Clear and complete
Impact of Change	✅	Fully documented
Test Plan	✅	Waived for revert
Contributors	✅	Optional
Screenshots/Videos	✅	Not applicable

---

This is a revert PR and passes automatically per policy. Nice, well-documented rollback to unblock releases! ✅

---

Powered by: Copilot CLI (claude-opus-4.8) | Last updated: Wed, 29 Jul 2026 23:33:37 GMT

[github-actions]

📊 Coverage Check

No source files changed in this PR.

[Copilot]

Pull request overview

Restores the Azure DevOps release setup to the previously working public npm registry configuration.

Changes:

• Removes CFS registry configuration and authentication.
• Removes the CFS override from pnpm installation.