diff --git a/package.json b/package.json
index 0f28ce4..d7197fb 100644
--- a/package.json
+++ b/package.json
@@ -3,7 +3,7 @@
   "version": "0.1.0",
   "private": true,
   "type": "module",
-  "packageManager": "pnpm@10.32.1",
+  "packageManager": "pnpm@11.5.3",
   "engines": {
     "node": ">=24"
   },
diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml
index be34331..23672f1 100644
--- a/pnpm-workspace.yaml
+++ b/pnpm-workspace.yaml
@@ -36,3 +36,16 @@ overrides:
   # frontmatter parser down a major version, and an unbounded `>=4.3.1` collapses
   # both lines to 5.x. The scoped form moves only the vulnerable resolution.
   js-yaml@4: "^4.3.1"
+
+# pnpm 11 turns an ignored build script into an install error where pnpm 10 only
+# warned, and it renamed the setting: the pnpm 10 spellings
+# (onlyBuiltDependencies, ignoredBuiltDependencies) are not read here and do not
+# warn about being ignored — verified by setting each and watching the install
+# fail on the same build. There is no key for "deliberately skipped", so a build
+# is either allowed or the install does not complete.
+#
+# esbuild arrives transitively through astro. Its platform binary comes from the
+# @esbuild/<platform> optional dependency, not from this script, which is why
+# pnpm 10 skipped it and the site built anyway.
+allowBuilds:
+  esbuild: true