Fix: Update bun.lock and remove stale package-lock.json
From the PR description
Problem
The build was failing with:
error: lockfile had changes, but lockfile is frozen
The bun.lock file was out of sync with package.json. Two dependencies were declared in package.json but missing from the lockfile:
@modelcontextprotocol/sdk@^1.29.0zod@^3.25.76
Solution
- Ran
bun installin the backend directory to regeneratebun.lockwith all dependencies - Removed the stale
package-lock.jsonto prevent future confusion from mixed package manager usage
The build should now pass with the updated lockfile.
Commits in this PR (1)
| SHA | Subject | Author | Date | |
|---|---|---|---|---|
de123826 | Fix: Update bun.lock and remove stale package-lock.json | Railway Agent | 2026-06-28 | ↗ GitHub |
commit body## Problem The build was failing with: ``` error: lockfile had changes, but lockfile is frozen ``` The `bun.lock` file was out of sync with `package.json`. Two dependencies were declared in `package.json` but missing from the lockfile: - `@modelcontextprotocol/sdk@^1.29.0` - `zod@^3.25.76` ## Solution - Ran `bun install` in the backend directory to regenerate `bun.lock` with all dependencies - Removed the stale `package-lock.json` to prevent future confusion from mixed package manager usage The build should now pass with the updated lockfile. | ||||
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-1.md from
inside the repo you want the changes in.