From 9d8760f39a771fa0ff0e76dcab443ce143660d75 Mon Sep 17 00:00:00 2001
From: Evan Sosenko <razorx@evansosenko.com>
Date: Wed, 19 Aug 2026 12:27:40 -0700
Subject: [PATCH 1/2] fix: Remove devEngines from package.json

Dependabot's npm updater rejects devEngines.packageManager.version
ranges that use "||", failing with "Invalid package manager
specification in package.json. The packageManager field must specify
a valid semver version." This has silently broken all npm version
updates on this repo since #595 introduced the field.

engines already communicates the Node/npm requirement to contributors
and CI without hard-failing external tooling, so devEngines is dropped
rather than pinned to a single version that would need to track
whatever runtime Dependabot's sandbox happens to use.
---
 package.json | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/package.json b/package.json
index 0b104a8..9094285 100644
--- a/package.json
+++ b/package.json
@@ -17,16 +17,6 @@
     "node": ">=22.11.0",
     "npm": ">=10.9.4"
   },
-  "devEngines": {
-    "runtime": {
-      "name": "node",
-      "version": "^24.11.0 || ^22.11.0"
-    },
-    "packageManager": {
-      "name": "npm",
-      "version": "^11.0.0 || ^10.9.4"
-    }
-  },
   "devDependencies": {
     "@seamapi/blueprint": "^1.8.0",
     "@seamapi/fake-seam-connect": "2.0.4",

From 24a9f51238be510aa282c89d617f0cde7a760f58 Mon Sep 17 00:00:00 2001
From: Evan Sosenko <razorx@evansosenko.com>
Date: Wed, 19 Aug 2026 14:44:33 -0700
Subject: [PATCH 2/2] fix: Pin packageManager so Corepack can resolve
 devEngines

Corepack rejects a devEngines.packageManager.version range when no
top-level packageManager is set, failing with "Invalid package manager
specification in package.json (npm@^11.0.0 || ^10.9.4); expected a
semver version" (nodejs/corepack#729, fix PR #730 still open).

Dependabot runs npm through Corepack to respect the packageManager
setting, so that parse failure aborted every npm update run with
dependency_file_not_resolvable. No npm version update has landed since
#595 added devEngines.

Pinning packageManager to an exact version gives Corepack something it
can parse, so devEngines is kept as the declared support range. The pin
is npm 11.19.0, the newest release satisfying both devEngines and
engines; Dependabot skips its release-age cooldown on npm below 11.10.
---
 package.json | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/package.json b/package.json
index 9094285..a94d8a2 100644
--- a/package.json
+++ b/package.json
@@ -2,6 +2,7 @@
   "name": "@seamapi/python",
   "private": true,
   "type": "module",
+  "packageManager": "npm@11.19.0",
   "scripts": {
     "generate": "tsx codegen/smith.ts",
     "pregenerate": "node generate-readme-toc.js",
@@ -17,6 +18,16 @@
     "node": ">=22.11.0",
     "npm": ">=10.9.4"
   },
+  "devEngines": {
+    "runtime": {
+      "name": "node",
+      "version": "^24.11.0 || ^22.11.0"
+    },
+    "packageManager": {
+      "name": "npm",
+      "version": "^11.0.0 || ^10.9.4"
+    }
+  },
   "devDependencies": {
     "@seamapi/blueprint": "^1.8.0",
     "@seamapi/fake-seam-connect": "2.0.4",