Release v10.3.15 fails to build with ERR_PNPM_LOCKFILE_BREAKING_CHANGE

[helge000]

Describe the Bug

Trying to build v10.3.15 fails with ERR_PNPM_LOCKFILE_BREAKING_CHANGE

See log below:

[...]
#14 [linux/arm64 builder 4/9] RUN corepack enable && corepack prepare
#14 2.711 Preparing pnpm@8.3.1...
#14 ...
#22 [linux/amd64 builder 8/9] RUN pnpm install --recursive --offline --frozen-lockfile
#22 0.429 Scope: all 22 workspace projects
#22 0.504  ERR_PNPM_LOCKFILE_BREAKING_CHANGE  Lockfile /directus/pnpm-lock.yaml not compatible with current pnpm
#22 0.504 
#22 0.504 Run with the --force parameter to recreate the lockfile.
#22 ERROR: process "/bin/sh -c pnpm install --recursive --offline --frozen-lockfile" did not complete successfully: exit code: 1
#14 [linux/arm64 builder 4/9] RUN corepack enable && corepack prepare
#14 CANCELED
------
 > [linux/amd64 builder 8/9] RUN pnpm install --recursive --offline --frozen-lockfile:
0.429 Scope: all 22 workspace projects
0.504  ERR_PNPM_LOCKFILE_BREAKING_CHANGE  Lockfile /directus/pnpm-lock.yaml not compatible with current pnpm
0.504 
0.504 Run with the --force parameter to recreate the lockfile.
------
ERROR: failed to build: failed to solve: process "/bin/sh -c pnpm install --recursive --offline --frozen-lockfile" did not complete successfully: exit code: 1

To Reproduce

1. git checkout v10.3.15
2. docker build .

Directus Version

v10.3.15

Hosting Strategy

Self-Hosted (Docker Image)

[sofiachakir]

Thanks for reporting this! You're correct - v10.3.15 has a lockfile compatibility issue.

This has been fixed in later releases. We recommend upgrading to v11.0.0 or later, which resolves this issue.

Note: v11.0.0+ requires Node.js 22. If upgrading to Node 22 is not possible for your setup, please let us know and we can look into providing a patched v10.3.x release.