chore(deps): update pnpm to v11.7.0 - #2644
Merged
Merged
Conversation
Renovate's #2601 only bumped `packageManager`, but `devEngines.packageManager` took precedence and kept CI on v10, and pnpm v11 enables `strictDepBuilds` by default which fails the install on undeclared build scripts (ERR_PNPM_IGNORED_BUILDS). Bump both version fields and declare the previously ignored build scripts via `allowBuilds` so the install matches the pnpm v10 behavior.
github-actions
Bot
added
the
t-tooling
Contributor
|
🗑️ Preview for this PR was deleted. |
With `devEngines.packageManager.onFail: warn`, pnpm v11 records the pnpm binary into pnpm-lock.yaml as a `packageManagerDependencies` document, prepending a second YAML document to the lockfile. Set `onFail: ignore` so pnpm leaves the lockfile untouched - the `packageManager` field and CI's pnpm setup already enforce the version.
Use `onFail: error` so npm/yarn refuse to install in this repo (they read `devEngines.packageManager`), disallowing other package managers. On pnpm v11 this records the pnpm binary into pnpm-lock.yaml as a `packageManagerDependencies` document - the original lockfile is preserved verbatim as the second document.
`onFail: error` makes npm refuse to run, so the `npm run test:llms-size` step failed with EBADDEVENGINES. This was the only non-pnpm invocation in the repo - switch it to pnpm, consistent with the rest of CI.
vladfrangu
reviewed
Jun 16, 2026
Comment on lines
+40
to
+46
| "@apify/ui-icons": false | ||
| "@parcel/watcher": false | ||
| "@swc/core": false | ||
| core-js: false | ||
| core-js-pure: false | ||
| postman-code-generators: false | ||
| protobufjs: false |
Member
There was a problem hiding this comment.
Pretty sure we do not want to deny these but approve, no?
Member
Author
There was a problem hiding this comment.
surely not all of them, e.g. core-js just spams with a sponsor message. i would guess if something is needed, the CI would be red? the preview also looks good to me (but i did only a quick comparison)
Member
Author
There was a problem hiding this comment.
These all ran ignored throughout the pnpm 10 era (pnpm 10 only warned, pnpm 11 errors), so false keeps the behavior production has shipped on — true would newly enable build steps we've safely skipped for ages. Checked each:
core-js/core-js-pure: postinstall is just the OpenCollective sponsor message.@swc/core,@parcel/watcher: native bindings come from prebuilt platform packages (@swc/core-*,@parcel/watcher-*); the build script only compiles from source as a fallback.@apify/ui-icons: itscreate-barrel-fileoutput (dist/index.js,index.css,index.d.ts) already ships in the published package.postman-code-generators,protobufjs: postinstalls aren't needed for the generated docs — confirmed by green CI + the preview.
Nothing here is needed at build time; if it were, the Docs build would be red.
vladfrangu
approved these changes
Jun 17, 2026
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
3 participants
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.
Updates pnpm from v10.33.4 to v11.7.0, replacing Renovate's #2601.
Renovate only bumped
packageManager, whichdevEngines.packageManageroverrides, so CI stayed on v10. This bumps both version fields and handles two pnpm v11 behavior changes:strictDepBuildsby default and fails the install on undeclared build scripts (ERR_PNPM_IGNORED_BUILDS) - the previously ignored build scripts are now declared viaallowBuildsinpnpm-workspace.yaml.devEngines.packageManager.onFailis set toerrorto disallow other package managers; the lonenpm runstep in CI is switched topnpmso it no longer tripsEBADDEVENGINES. On pnpm v11 this also records the pnpm binary intopnpm-lock.yamlas a leadingpackageManagerDependenciesdocument (intended behavior).