fix: regenerate bun.lock with next@16.2.4 to fix frozen-lockfile error
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
| Repository | LegalAIDev/mike |
|---|---|
| Author | Claude <noreply@anthropic.com> |
| Authored | |
| Parents | fd26f7fa |
| Stats | 1 file changed , +16 , -16 |
| Part of | Next.js 16.0.3 → 16.2.4 upgrade (CVE-2025-66478) |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-54d5b701.md
from inside the repo you want the change in.