Frozen install rejects fresh lockfile

“A frozen install should never report "lockfile had changes" immediately after a successful non-frozen install with no edits in between.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/bun/issues/5989/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 1 a week at the late-July peak.

Frozen lockfile install rejects lockfile Bun just generated. After bun install or bun add writes bun.lock with no edits in between, bun install --frozen-lockfile exits with status 1.

Is this your bug?

File my report

Where: bun install
Error text: error: lockfile had changes, but lockfile is frozenPasted in 3 reports
Versions: 1.4.0-canary.1 to 1.4.2
Platforms: Linux
How bad: Breaks a normal workflow.

Not quite your bug?

Prune removes packages still in lockfile1 person

Original reports3, newest first

Oct 7, 2026bun add writes a bun.lock that the next bun install rewrites, so --frozen-lockfile fails right after bun add#44713
Aug 10, 2026--frozen-lockfile rejects bun's own lockfile output (1.4.0-canary)#37346
Jul 31, 2026bun install --frozen-lockfile rejects a lockfile that bun install just generated#36577

Frozen install rejects fresh lockfile

Is this your bug? What gets counted gets fixed. Pile on.

Is this your bug?

Not quite your bug?

Original reports3, newest first

Do you work on Bun?