Skip to content

fix(ci): regenerate the npm wrapper lock with CI's npm major #234

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Mikola Lysenko (mikolalysenko) wants to merge 2 commits into
base: main
Choose a base branch
from
+9 −25
Open

fix(ci): regenerate the npm wrapper lock with CI's npm major #234

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
640a0a5
fix(ci): regenerate the npm wrapper lock with CI's npm major
mikolalysenko Aug 28, 2026
731d322
fix(ci): pin the npm wrapper lock refresh to npm@10 via npx
mikolalysenko Aug 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 0 additions & 24 deletions npm/socket-patch/package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

10 changes: 9 additions & 1 deletion scripts/version-sync.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,17 @@ node -e "
# Refresh the npm wrapper lockfile so package-lock.json stays in sync with the
# bumped package.json (own version, optionalDependencies). Uses --package-lock-only
# so node_modules is untouched.
#
# The npm major is pinned: the lock's byte shape depends on it (npm >= 11 adds
# `libc` arrays to platform-package entries that npm 10 omits), and
# release-lint.sh compares the regenerated lock byte-for-byte against the
# committed one on every PR. An unpinned npm makes that gate depend on
# whichever npm the runner or developer happens to have. Bumping this pin
# requires refreshing the committed lock in the same commit.
NPM_LOCK_REFRESH_VERSION="10"
(
cd "$REPO_ROOT/npm/socket-patch"
npm install --package-lock-only --ignore-scripts >/dev/null
npx --yes "npm@$NPM_LOCK_REFRESH_VERSION" install --package-lock-only --ignore-scripts >/dev/null
)

# Update all per-platform npm package versions
Expand Down
Loading