LegalAIDev/mike#3: fix: upgrade next from 16.0.3 to ^16.0.10 to resolve Railway build failure

fix: upgrade next from 16.0.3 to ^16.0.10 to resolve Railway build failure

✅ merged · #3 · LegalAIDev/mike ← LegalAIDev/mike · opened 27d ago by LegalAIDev · merged 27d ago by LegalAIDev · self · +16-16 across 1 file · ↗ on GitHub

From the PR description

$(cat <<'EOF'

Summary

next@16.0.3 was deprecated due to security vulnerability CVE-2025-66478, causing Railway's npm install to fail
bun install --frozen-lockfile was also failing because bun.lock still referenced the old deprecated version
Updated next to ^16.0.10 in package.json, which resolves to 16.2.4 (latest patched release)
Regenerated both package-lock.json and bun.lock to reflect the new version

Test plan

Railway build completes without npm/bun install errors
bun install --frozen-lockfile passes with the updated bun.lock
Frontend builds and runs as expected EOF )

Generated by Claude Code

Commits in this PR (1)

SHA Subject Author Date

54d5b701 fix: regenerate bun.lock with next@16.2.4 to fix frozen-lockfile error Claude 2026-04-30 ↗ GitHub

SHA	Subject	Author	Date
`54d5b701`	fix: regenerate bun.lock with next@16.2.4 to fix frozen-lockfile error	Claude	2026-04-30	↗ GitHub
bun.lock still referenced the deprecated next@16.0.3, causing Railway's bun install --frozen-lockfile to fail. Updated lockfile resolves next to 16.2.4. https://claude.ai/code/session_01Aft1gooJJZpGTXoK3u2xao

bun.lock still referenced the deprecated next@16.0.3, causing Railway's
bun install --frozen-lockfile to fail. Updated lockfile resolves next to 16.2.4.

https://claude.ai/code/session_01Aft1gooJJZpGTXoK3u2xao

Capture this PR into my fork

Download a Markdown prompt that tells Claude how to port every commit in this PR into your working tree. Run it via claude -p < capture-pull-3.md from inside the repo you want the changes in.

⬇ Download capture-pull-3.md