We have updates from the Pages engineering team: Given that Bun is relatively new, and is the only tool we've had reports like this on, we are leaning towards this being a Bun issue. It looks like Bun's v1.0.29 release added reliability improvements to bun install, so I'd suggest you to try that version (or whatever is latest): https://bun.sh/blog/bun-v1.0.29 Additionally, if you would like to customize your bun install command (eg. to remove --frozen-lockfile or add --verbose), you can add the following environment variable to skip the automatic dependency installation: SKIP_DEPENDENCY_INSTALL=true{}

The code path used by --frozen-lockfile to detect whether a lockfile changed sometimes incorrectly reported that the lockfile changed when it didn't. This would cause errors like: error: lockfile had changes, but is frozen To fix this, we've changed how we define "frozen". Instead of relying on input from the filesystem which can potentially change for unrelated reasons, we've switched it to using a hash of the package names and their versions sorted alphabetically with their version numbers. We think this is a more reliable approach.