Skip to content

Use internal npm feed for API package pipeline - #1827

Merged
Bill Schnurr (bschnurr) merged 1 commit into
mainfrom
fix/npm-internal-feed
Sep 26, 2026
Merged

Bill Schnurr (bschnurr) merged 1 commit into
mainfrom
fix/npm-internal-feed

Conversation

@bschnurr

Copy link
Copy Markdown
Member

Summary

  • route API package installs through the Pylance_PublicPackages Azure Artifacts feed
  • reuse the shared Pylance-Eng npm setup template for authentication and registry configuration
  • rewrite public npm URLs in lockfiles before installing dependencies

Validation

  • parsed build/azure-pipeline.npm.yml with PyYAML
  • ran git diff --check

1ES guidance confirms that npmAuthenticate@0 alone does not redirect lockfile-pinned registry.npmjs.org downloads; the shared setup-template pattern matches the sibling VS Code extension repositories.

Configure the npm publishing pipeline through the shared Pylance-Eng setup template so installs authenticate against Pylance_PublicPackages and lockfile URLs are redirected from the public registry.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 16c019ed-4e8f-4460-ad18-3b8cd11ea04b
@bschnurr
Bill Schnurr (bschnurr) merged commit f0648b9 into main Sep 26, 2026
168 of 172 checks passed
@bschnurr
Bill Schnurr (bschnurr) deleted the fix/npm-internal-feed branch September 26, 2026 05:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

debt Code quality issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants