chore: keep lockfile registry-agnostic - #89
Open
peakematt wants to merge 1 commit into
Open
Conversation
peakematt
marked this pull request as ready for review
September 3, 2026 15:04
Greptile SummaryThis PR makes the committed npm lockfile registry-agnostic without changing dependency resolution.
Confidence Score: 5/5The PR appears safe to merge because the supported npm workflows can consume the registry-agnostic lockfile without changing dependency semantics. The configuration is supported by the npm versions used in repository workflows, and the lockfile change only removes registry-specific URL metadata while preserving versions, dependency relationships, and integrity hashes. Important Files Changed
Reviews (1): Last reviewed commit: "chore: keep lockfile registry-agnostic" | Re-trigger Greptile |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HELP-722 requires committed public SDK lockfiles to be independent of the registry used to generate them. The current lockfile records registry-specific
resolvedURLs, which couples it to the effective install registry.This adds
omit-lockfile-registry-resolved=trueand regenerates the existing lockfile without changing dependencies.Verification found 593 registry
resolvedentries removed and all 593 integrity values preserved. Versions, package records, dependency relationships, non-registry resolutions, and lockfile version are unchanged. There are zero Socket Firewall host references and zero semantic verifier violations.The branch was regenerated and checked with Node
v22.23.2and npm10.9.8:npm install --package-lock-only --ignore-scripts --no-audit --no-fund npm ci --registry=https://registry.npmjs.org/ npm run prettier npm run lint npm run build npm test -- --coverageThe clean public-registry install left the lockfile unchanged. This draft should remain unmerged until the earlier
workos-noderollout and downstream lockfile-command validation are complete; no reviewer action is requested yet.HELP-722: https://linear.app/workos/issue/HELP-722