Skip to content

fix(deps): resync package-lock after the automation merge - #49

Merged
oratis merged 1 commit into
mainfrom
fix/lockfile-resync
Aug 1, 2026
Merged

fix(deps): resync package-lock after the automation merge#49
oratis merged 1 commit into
mainfrom
fix/lockfile-resync

Conversation

@oratis

@oratis oratis commented Aug 1, 2026

Copy link
Copy Markdown
Owner

The automation merge left package-lock.json internally inconsistent, breaking npm ci on node:20-alpine (Cloud Build). Rebuilt from main's pre-merge baseline + resend only. Verified with a clean-room npm ci. 🤖 Generated with Claude Code

Merging the 07-05 automation branch textually combined its older
package-lock.json with main's newer one, leaving the tree internally
inconsistent: `next` pins @swc/helpers 0.5.15 while the merged lock also
carried a 0.5.23 requirement. npm 11 (local) tolerated it, but the image
builds on node:20-alpine where `npm ci` rejected it — "Missing:
@swc/helpers@0.5.23 from lock file" — so the Cloud Build failed.

Rebuilt the lock from main's pre-merge baseline plus the one genuinely new
dependency (resend), keeping the delta minimal. Verified with a clean-room
`npm ci` (not just `npm install`, which masks this class of drift).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@oratis
oratis merged commit 2a49e45 into main Aug 1, 2026
@oratis
oratis deleted the fix/lockfile-resync branch August 1, 2026 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant