Errors with Bun: "lockfile had changes, but lockfile is frozen"

[rohitpaulk]

Copying from GitHub:

Redis challenge, using TypeScript

while running tests my repo suddenly returns:

This test run was cancelled because it was waiting on a build that failed.
The build failed with the following error:
Detected changes to language_pack (old: bun-1.1, new: deno-1.42).
This isn't supported. If you're trying to upgrade to a new language version, please try creating a new repository.
If you think this is a CodeCrafters bug, please contact us at hello@codecrafters.io.

I created a new repository, and on the second step, I get this error now:

...
remote: [build] Step 10 complete.
remote: [build] Step 11 complete.
remote: [build] > bun install v1.1.4 (fbe2fe0c)
remote: [build] >  Resolving dependencies
remote: [build] >  Resolved, downloaded and extracted [8]
remote: [build] > error: lockfile had changes, but lockfile is frozen
remote: [build] > note: try re-running without --frozen-lockfile and commit the updated lockfile
remote: [build] Error: process "/bin/sh -c bun install --frozen-lockfile" did not complete successfully: exit code: 1.
remote: [build] > bun install v1.1.4 (fbe2fe0c)
remote: [build] >  Resolving dependencies
remote: [build] >  Resolved, downloaded and extracted [8]
remote: [build] > error: lockfile had changes, but lockfile is frozen
remote: [build] > note: try re-running without --frozen-lockfile and commit the updated lockfile
remote: [build] Build failed. Check the logs above for the reason.
remote: [build] If you think this is a CodeCrafters error, please contact us at hello@codecrafters.io.
remote: 

[rohitpaulk]

To anyone seeing this: this happens when package.json is updated but bun.lockb is not. You’ll need to run bun install locally so that bun.lockb is updated.

We use this flag so that builds are reproducible, i.e. so that we’re using the exact same versions of dependencies that you’re using locally.