Repository navigation
chore: move to pnpm 10.34.5 - #26
Merged
Merged
Conversation
The pin sat at 10.13.1, 21 minors behind, for no deliberate reason — it propagated by copying. lockfileVersion stays 9.0. Latest 10.x rather than 11: pnpm 11 stops reading the "pnpm" field in package.json and replaces onlyBuiltDependencies with an allowBuilds map, so it wants doing across the repos together with the official codemod. Deferred.
saby1101
force-pushed
the
chore/pnpm-11
branch
from
August 15, 2026 09:59
1d933e0 to
aa98e73
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
packageManagersat atpnpm@10.13.1, 21 minors behind, for no deliberate reason — the pin propagated by copying between repos.lockfileVersionstays9.0, so this is a version bump and a lockfile refresh, nothing structural.Why 10.34.5 and not 11.21.0. pnpm 11 stops reading the
pnpmfield inpackage.jsonand replacesonlyBuiltDependencieswith an explicitallowBuildsmap. Nothing in this repo uses thepnpmfield, so 11 would in fact be easy here — but wms keeps all of itsoverridesthere, including the@fastify/staticandtmpCVE fixes, and those would be silently dropped. That migration wants doing across the repos together, with the officialpnpm-v10-to-v11codemod rather than by hand. Deferred.Verified on 10.34.5: lint, build, 149 unit tests at 100% coverage, all 9 MinIO integration tests against a live container, and a clean
--frozen-lockfileinstall.