Skip to content

chore: omit registry URLs from catalog lockfile - #519

Open
Jamie Magee (JamieMagee) wants to merge 1 commit into
microsoft:masterfrom
JamieMagee:fix/omit-lockfile-registry-resolved
Open

chore: omit registry URLs from catalog lockfile#519
Jamie Magee (JamieMagee) wants to merge 1 commit into
microsoft:masterfrom
JamieMagee:fix/omit-lockfile-registry-resolved

Conversation

@JamieMagee

Copy link
Copy Markdown
Member

Category

  • Bug fix
  • New script
  • New sample

Instructions

  • No documentation update is needed for this lockfile-generation change.
  • Followed the contributing guidance.

Related Issues

N/A

What's in this Pull Request?

Adds tools/catalog-build/.npmrc with omit-lockfile-registry-resolved=true and regenerates the lockfile so registry feed URLs are not committed.

The regenerated lockfile removes 12 resolved fields. Dependency names, versions, integrity hashes, and platform metadata are unchanged.

Validation

  • npx --yes -p node@20 -p npm@10.9.4 -c 'node --version && npm --version && npm config get omit-lockfile-registry-resolved' returned Node v20.20.2, npm 10.9.4, and true.
  • A structural lockfile comparison found no changes outside resolved; no Microsoft feed URLs remain.
  • Repeating npm install --package-lock-only --ignore-scripts --no-audit --no-fund left SHA-256 a904c40418791dd297b4af43da19545473bf909bd9ab8e79b50cf5bec3d95500 unchanged.
  • npm ci --no-audit --no-fund installed 12 packages.
  • npm run check passed: Catalog metadata is valid for 30 resources.

Configure npm to omit registry-resolved URLs and regenerate the lockfile without changing dependency metadata.

Co-authored-by: Copilot <223556219+Copilot@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.

1 participant