Skip to content

Stop recording registry URLs in the sidecar lockfile - #704

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

Stop recording registry URLs in the sidecar lockfile#704
Jamie Magee (JamieMagee) wants to merge 1 commit into
microsoft:mainfrom
JamieMagee:fix/omit-lockfile-registry-resolved

Conversation

@JamieMagee

Copy link
Copy Markdown
Member

Summary

Add omit-lockfile-registry-resolved=true to samples/nodejs/entra-agent-id-sidecar and regenerate its package lock with npm 10.9.4. This removes registry-specific resolved URLs while keeping dependency versions, integrity hashes, lockfile version 3, and platform metadata unchanged.

npm will resolve registry tarball URLs from the active registry during installation.

Tooling

I used npm 10.9.4, which is compatible with the sample's Node.js 22 or later requirement.

Validation

  • npx --yes npm@10.9.4 config get omit-lockfile-registry-resolved
  • npx --yes npm@10.9.4 install --package-lock-only --ignore-scripts --no-audit --no-fund
  • Repeated lockfile generation and confirmed a clean result
  • npx --yes npm@10.9.4 ci --ignore-scripts --no-audit --no-fund
  • npm run build

All commands passed. The lockfile checks were:

config=true
target_feed_urls=0
all_registry_resolved=0
metadata_preserved=true
second_regeneration_clean=true

Add the project npm setting and regenerate the Entra Agent ID sidecar lockfile without changing dependency metadata.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions github-actions Bot added Samples Changes to Samples From Fork labels Aug 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

From Fork Samples Changes to Samples

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant