Commit ef6e2e1
chore(js): restore missing
The 0.14.1 release commit (05e4ad7) bumped all eight platform packages
in `package.json` to `0.14.1`, but `pnpm-lock.yaml` ended up missing
`impit-linux-arm64-musl` entirely instead of bumping it. This leaves the
lockfile out of sync with `package.json`, so every `pnpm install
--frozen-lockfile` in CI fails with `ERR_PNPM_OUTDATED_LOCKFILE`.
The package itself published fine — the lockfile was regenerated by the
release workflow ~12s after `impit-linux-arm64-musl@0.14.1` was
published, before the npm registry had propagated it. Since these are
optional dependencies, pnpm silently omitted the one it couldn't resolve
and still exited 0, so the incomplete lockfile got committed.
This regenerates the lockfile now that the package has propagated,
restoring the missing entry. `pnpm install --frozen-lockfile` passes
locally. The workflow change to prevent recurrence is in a follow-up PR.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>impit-linux-arm64-musl in lockfile (#467)1 parent 4d308ba commit ef6e2e1
1 file changed
Lines changed: 13 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments