From d8f9b44fc362f651cad143f10ebaf322335a51ec Mon Sep 17 00:00:00 2001 From: Charlie Chrisman Date: Fri, 17 Jul 2026 01:02:08 +0200 Subject: [PATCH] fix(build): move pnpm overrides to pnpm-workspace.yaml for pnpm 11 readiness (#2220) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit pnpm 10.33 warns on every install and build: [WARN] The "pnpm" field in package.json is no longer read by pnpm. The following keys were ignored: "pnpm.onlyBuiltDependencies", "pnpm.overrides" The wording overstates it for the pinned version: on pnpm 10.33 the field is still honoured, so nothing is broken today. It is a forward-looking deprecation notice, and pnpm 11 makes it real — there the overrides silently stop applying. Reproduced on pnpm 11 with the workspace pins declared only in package.json: overrides block dropped from pnpm-lock.yaml @types/node ^25.5.2 -> ^22.0.0 (25.5.2 -> 22.20.1) zod 4.3.6 -> 3.25.76 @types/node fragments into 5 versions across the workspace pnpm-workspace.yaml is the supported home and is honoured by both 10.33 and 11, so moving `overrides` there is safe on the pinned version and correct for the next major. Verified on pnpm 10.33: `pnpm install --lockfile-only` leaves pnpm-lock.yaml byte-identical and its `overrides` block is now sourced from pnpm-workspace.yaml. Verified on a minimal repro that pnpm 10.33 applies yaml overrides (ms -> 2.0.0). Scope is deliberately limited to `overrides`. `ignoredBuiltDependencies` and `onlyBuiltDependencies` are left in place: they are also honoured on 10.33 and ignored on 11, but the workspace list is not a superset of the package.json one (it omits `electron`, removed in c7641f9d when electron became a runtime dependency, and three @embedded-postgres arches outside the `supportedArchitectures` cpu list curated in 1b9dce22). Reconciling those is a maintainer call about intended behaviour, not a mechanical move, so it is left for a follow-up rather than guessed at here. No changeset: workspace/build config only, behaviour-preserving on the pinned pnpm, and it does not affect published @runfusion/fusion. ## Summary by CodeRabbit * **Chores** * Updated workspace dependency version overrides for improved consistency across packages. * Consolidated dependency configuration in the workspace settings. Co-authored-by: gsxdsm --- package.json | 6 +----- pnpm-workspace.yaml | 3 +++ 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/package.json b/package.json index 28e64fb8b0..3250b0baab 100644 --- a/package.json +++ b/package.json @@ -104,11 +104,7 @@ "esbuild", "koffi", "protobufjs" - ], - "overrides": { - "@types/node": "^25.5.2", - "protobufjs": "^7.5.8" - } + ] }, "devDependencies": { "@changesets/cli": "^2.30.0", diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml index 5797698f38..9f3114e890 100644 --- a/pnpm-workspace.yaml +++ b/pnpm-workspace.yaml @@ -15,6 +15,9 @@ onlyBuiltDependencies: - esbuild - koffi - protobufjs +overrides: + '@types/node': ^25.5.2 + protobufjs: ^7.5.8 # FNXC:DesktopEmbeddedPostgres 2026-07-14-09:30: # Desktop release jobs cross-build Intel and ARM64 artifacts on one host. Install # optional native payloads for both CPU families on the current OS so each