chore: regenerate package-lock.json to unblock release workflow#626
Merged
Conversation
Fixes release workflow failure — npm ci complained about missing @esbuild/* optional platform packages. Someone committed a lock generated with only the local platform's esbuild binary, so CI (Linux) couldn't resolve the tree. Regenerated from a clean node_modules. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Changeset check requires either a version-bumping changeset or an explicit empty one. This PR only regenerates package-lock.json to restore cross-platform esbuild entries, so no release is needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
bokelley
force-pushed
the
bokelley/fix-lock-esbuild
branch
from
April 19, 2026 20:11
c97b80a to
003851a
Compare
Picks up GetAdCPCapabilitiesResponse.experimental_features and other drift that landed after #628's regen. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
The release workflow has been failing since #623 merged with:
```
npm error code EUSAGE
npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync.
npm error Missing: @esbuild/aix-ppc64@0.27.4 from lock file
npm error Missing: @esbuild/android-arm@0.27.4 from lock file
...
```
Root cause: the committed `package-lock.json` only contained the `@esbuild/darwin-arm64` platform binary — whoever upgraded esbuild ran `npm install` on a Mac and the resulting lock stripped the other platforms. `npm ci` on Linux CI couldn't resolve the tree.
Fix
Regenerated `package-lock.json` from a clean `node_modules` on main. Now contains all 26 `@esbuild/*` platform packages.
Side effects: net -333 lines in the lock. Spot-checked that the delta is mostly consolidated entries from the regen; no dependency version changes (same package.json).
Blast radius
Unblocks the pending #622 release PR, which was stuck because changesets action couldn't run `npm ci`. After this merges, the changesets action will refresh #622 against the post-#623 state (3 changesets → 5.2.0).
No changeset needed — lock-file only, no runtime behavior change.
🤖 Generated with Claude Code