Skip to content

Use packagefeedproxy for Rush pipeline bootstrapping - #321

Open
David Michon (dmichon-msft) with Copilot wants to merge 2 commits into
mainfrom
copilot/update-pipeline-npm-registry-references
Open

Use packagefeedproxy for Rush pipeline bootstrapping#321
David Michon (dmichon-msft) with Copilot wants to merge 2 commits into
mainfrom
copilot/update-pipeline-npm-registry-references

Conversation

Copilot AI commented Aug 21, 2026

Copy link
Copy Markdown

Pipeline Rush bootstrapping should resolve npm packages through packagefeedproxy.microsoft.io instead of registry.npmjs.org. install-run-rush.js should also use a committed lockfile for deterministic Rush installation.

  • Registry configuration

    • Updated Rush npm registry settings to use:
      registry=https://packagefeedproxy.microsoft.io/npm/
    • Updated matching auth-token examples in Rush npm config files.
  • Rush bootstrap lockfile

    • Added common/config/validation/rush-package-lock.json for @microsoft/rush@5.169.2.
    • Rewrote lockfile resolved URLs to the packagefeedproxy registry.
  • Pipeline wiring

    • Set INSTALL_RUN_RUSH_LOCKFILE_PATH for GitHub Actions and Azure Pipelines Rush bootstrap invocations:
      INSTALL_RUN_RUSH_LOCKFILE_PATH: <repo>/common/config/validation/rush-package-lock.json

Copilot AI and others added 2 commits August 21, 2026 23:16
Co-authored-by: dmichon-msft <26827560+dmichon-msft@users.noreply.github.com>
Co-authored-by: dmichon-msft <26827560+dmichon-msft@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants