Skip to content

Omit registry URLs from the smoke test lockfile - #2893

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

Omit registry URLs from the smoke test lockfile#2893
Jamie Magee (JamieMagee) wants to merge 1 commit into
microsoft:masterfrom
JamieMagee:fix/omit-lockfile-registry-resolved

Conversation

@JamieMagee

Copy link
Copy Markdown
Member

Summary

  • Add omit-lockfile-registry-resolved=true to test/smoke/.npmrc.
  • Regenerate the smoke test lockfile with npm 11.19.0.
  • Remove 176 registry resolved fields, including the Azure Artifacts proxy URLs. The GitHub dependency keeps its non-registry resolved value.

Dependency versions, integrity hashes, lockfileVersion, and platform metadata are unchanged.

Validation

  • npx --yes npm@11.19.0 config get omit-lockfile-registry-resolved returned true.
  • A second npx --yes npm@11.19.0 install --package-lock-only --ignore-scripts --no-audit --no-fund made no changes.
  • Azure Artifacts feed URLs remaining in the lockfile: 0.
  • npx --yes npm@11.19.0 ci --ignore-scripts --no-audit --no-fund passed in test/smoke.
  • npx --yes npm@11.19.0 ci --ignore-scripts --no-audit --no-fund passed at the repository root.
  • npx --yes npm@11.19.0 run compile-smoke-tests passed.

npm config reference: https://docs.npmjs.com/cli/v8/using-npm/config#omit-lockfile-registry-resolved

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

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

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