diff --git a/package-lock.json b/package-lock.json
index 6e665262..c68e1a80 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -32,7 +32,7 @@
         "typescript": "^5.9.3"
       },
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "node_modules/@aashutoshrathi/word-wrap": {
@@ -12368,7 +12368,7 @@
       "version": "4.2.1",
       "license": "MIT",
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "packages/client-metrics-web": {
@@ -12379,7 +12379,7 @@
         "aws-rum-web": "^1.25.0"
       },
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "packages/crash-handler": {
@@ -12390,7 +12390,7 @@
         "@dotcom-reliability-kit/log-error": "^5.1.6"
       },
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "packages/errors": {
@@ -12398,7 +12398,7 @@
       "version": "4.2.0",
       "license": "MIT",
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "packages/eslint-config": {
@@ -12409,7 +12409,7 @@
         "@types/eslint": "^8.56.6"
       },
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       },
       "peerDependencies": {
         "eslint": ">=8.27.0"
@@ -12430,7 +12430,7 @@
         "undici": "^7.18.2"
       },
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "packages/log-error": {
@@ -12447,7 +12447,7 @@
         "@types/express": "^5.0.6"
       },
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "packages/logger": {
@@ -12466,7 +12466,7 @@
         "@types/lodash.clonedeep": "^4.5.9"
       },
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       },
       "peerDependencies": {
         "pino-pretty": ">=7.0.0 <11.0.0"
@@ -12477,7 +12477,7 @@
       "version": "1.1.0",
       "license": "MIT",
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "packages/middleware-log-errors": {
@@ -12492,7 +12492,7 @@
         "express": "^5.2.1"
       },
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "packages/middleware-render-error-info": {
@@ -12509,7 +12509,7 @@
         "@types/express": "^5.0.6"
       },
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "packages/opentelemetry": {
@@ -12533,7 +12533,7 @@
         "express": "^5.2.1"
       },
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "packages/serialize-error": {
@@ -12541,7 +12541,7 @@
       "version": "4.2.0",
       "license": "MIT",
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "packages/serialize-request": {
@@ -12552,7 +12552,7 @@
         "@types/express": "^5.0.6"
       },
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "resources/logos": {
@@ -12568,7 +12568,7 @@
         "@types/svgo": "^3.0.0"
       },
       "engines": {
-        "node": "22.x || 24.x"
+        "node": "^22.12 || ^24"
       }
     },
     "resources/splunk-dashboards": {
diff --git a/package.json b/package.json
index 4f4266fd..ff30a502 100644
--- a/package.json
+++ b/package.json
@@ -45,7 +45,7 @@
     "typescript": "^5.9.3"
   },
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "volta": {
     "node": "24.12.0"
diff --git a/packages/app-info/docs/migration.md b/packages/app-info/docs/migration.md
index b2a4d93f..1a03d1de 100644
--- a/packages/app-info/docs/migration.md
+++ b/packages/app-info/docs/migration.md
@@ -16,6 +16,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v4 to v5](#migrating-from-v4-to-v5)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -44,3 +45,7 @@ Emoji           | Label             | Meaning
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/app-info/package.json b/packages/app-info/package.json
index 7e126ce7..049cb646 100644
--- a/packages/app-info/package.json
+++ b/packages/app-info/package.json
@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: app-info\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts"
diff --git a/packages/client-metrics-web/docs/migration.md b/packages/client-metrics-web/docs/migration.md
index 6b169eeb..e26aa540 100644
--- a/packages/client-metrics-web/docs/migration.md
+++ b/packages/client-metrics-web/docs/migration.md
@@ -11,6 +11,7 @@ Emoji           | Label             | Meaning
 
 * [Migrating from v0 to v1](#migrating-from-v0-to-v1)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v0 to v1
@@ -18,3 +19,7 @@ Emoji           | Label             | Meaning
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/client-metrics-web/package.json b/packages/client-metrics-web/package.json
index a0d054a5..611576e8 100644
--- a/packages/client-metrics-web/package.json
+++ b/packages/client-metrics-web/package.json
@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: client-metrics-web\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts",
diff --git a/packages/crash-handler/docs/migration.md b/packages/crash-handler/docs/migration.md
index f54f5268..cb3dfd06 100644
--- a/packages/crash-handler/docs/migration.md
+++ b/packages/crash-handler/docs/migration.md
@@ -19,6 +19,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v5 to v6](#migrating-from-v5-to-v6)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -73,3 +74,7 @@ You can safely migrate to this version of Crash Handler if your app is either _n
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/crash-handler/package.json b/packages/crash-handler/package.json
index 942e546e..e31d6db3 100644
--- a/packages/crash-handler/package.json
+++ b/packages/crash-handler/package.json
@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: crash-handler\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts",
diff --git a/packages/errors/docs/migration.md b/packages/errors/docs/migration.md
index 4029e5bb..3013f13f 100644
--- a/packages/errors/docs/migration.md
+++ b/packages/errors/docs/migration.md
@@ -16,6 +16,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v4 to v5](#migrating-from-v4-to-v5)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -44,3 +45,7 @@ Emoji           | Label             | Meaning
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/errors/package.json b/packages/errors/package.json
index b3f14bfd..053f53e5 100644
--- a/packages/errors/package.json
+++ b/packages/errors/package.json
@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: errors\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts"
diff --git a/packages/eslint-config/docs/migration.md b/packages/eslint-config/docs/migration.md
index 448d1ec9..556f503d 100644
--- a/packages/eslint-config/docs/migration.md
+++ b/packages/eslint-config/docs/migration.md
@@ -16,6 +16,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v4 to v5](#migrating-from-v4-to-v5)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -52,3 +53,7 @@ You may need to make changes to your code if these linting errors are found.
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/eslint-config/package.json b/packages/eslint-config/package.json
index 583a9dc1..a33e017f 100644
--- a/packages/eslint-config/package.json
+++ b/packages/eslint-config/package.json
@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: eslint-config\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts",
diff --git a/packages/fetch-error-handler/docs/migration.md b/packages/fetch-error-handler/docs/migration.md
index 4a0d583a..e5187498 100644
--- a/packages/fetch-error-handler/docs/migration.md
+++ b/packages/fetch-error-handler/docs/migration.md
@@ -11,6 +11,7 @@ Emoji           | Label             | Meaning
 
 * [Migrating from v1 to v2](#migrating-from-v1-to-v2)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -18,3 +19,7 @@ Emoji           | Label             | Meaning
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/fetch-error-handler/package.json b/packages/fetch-error-handler/package.json
index 03f971ff..211b199c 100644
--- a/packages/fetch-error-handler/package.json
+++ b/packages/fetch-error-handler/package.json
@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: fetch-error-handler\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts",
diff --git a/packages/log-error/docs/migration.md b/packages/log-error/docs/migration.md
index e2786247..6f29687c 100644
--- a/packages/log-error/docs/migration.md
+++ b/packages/log-error/docs/migration.md
@@ -19,6 +19,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v5 to v6](#migrating-from-v5-to-v6)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -72,3 +73,7 @@ logHandledError({
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/log-error/package.json b/packages/log-error/package.json
index f4d24256..4d0376c4 100644
--- a/packages/log-error/package.json
+++ b/packages/log-error/package.json
@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: log-error\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts",
diff --git a/packages/logger/docs/migration.md b/packages/logger/docs/migration.md
index 84c9752e..2434ab34 100644
--- a/packages/logger/docs/migration.md
+++ b/packages/logger/docs/migration.md
@@ -38,6 +38,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v4 to v5](#migrating-from-v4-to-v5)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from n-logger
@@ -311,3 +312,7 @@ If neither of the above is true, this should be a safe update with no code chang
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/logger/package.json b/packages/logger/package.json
index 1fa0425d..270d56f1 100644
--- a/packages/logger/package.json
+++ b/packages/logger/package.json
@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: logger\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts",
diff --git a/packages/middleware-allow-request-methods/docs/migration.md b/packages/middleware-allow-request-methods/docs/migration.md
index d2d2a1a4..6f0e357c 100644
--- a/packages/middleware-allow-request-methods/docs/migration.md
+++ b/packages/middleware-allow-request-methods/docs/migration.md
@@ -11,6 +11,7 @@ Emoji           | Label             | Meaning
 
 * [Migrating from v1 to v2](#migrating-from-v1-to-v2)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -18,3 +19,7 @@ Emoji           | Label             | Meaning
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/middleware-allow-request-methods/package.json b/packages/middleware-allow-request-methods/package.json
index 721fc222..daa91046 100644
--- a/packages/middleware-allow-request-methods/package.json
+++ b/packages/middleware-allow-request-methods/package.json
@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: middleware-allow-request-methods\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts"
diff --git a/packages/middleware-log-errors/docs/migration.md b/packages/middleware-log-errors/docs/migration.md
index e4b10703..15b394ec 100644
--- a/packages/middleware-log-errors/docs/migration.md
+++ b/packages/middleware-log-errors/docs/migration.md
@@ -19,6 +19,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v5 to v6](#migrating-from-v5-to-v6)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -75,3 +76,7 @@ You can safely migrate to this version of the error logging middleware if your a
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/middleware-log-errors/package.json b/packages/middleware-log-errors/package.json
index 853e4bfa..ed83c414 100644
--- a/packages/middleware-log-errors/package.json
+++ b/packages/middleware-log-errors/package.json
@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: middleware-log-errors\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts",
diff --git a/packages/middleware-render-error-info/docs/migration.md b/packages/middleware-render-error-info/docs/migration.md
index f3d6cec0..c62f252b 100644
--- a/packages/middleware-render-error-info/docs/migration.md
+++ b/packages/middleware-render-error-info/docs/migration.md
@@ -21,6 +21,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v6 to v7](#migrating-from-v6-to-v7)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -71,3 +72,7 @@ You can safely migrate to this version of the error logging middleware if your a
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/middleware-render-error-info/package.json b/packages/middleware-render-error-info/package.json
index aa5d3d62..c65b05aa 100644
--- a/packages/middleware-render-error-info/package.json
+++ b/packages/middleware-render-error-info/package.json
@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: middleware-render-error-info\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts",
diff --git a/packages/opentelemetry/docs/migration.md b/packages/opentelemetry/docs/migration.md
index 12b899c3..0c10bc43 100644
--- a/packages/opentelemetry/docs/migration.md
+++ b/packages/opentelemetry/docs/migration.md
@@ -15,6 +15,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v3 to v4](#migrating-from-v3-to-v4)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -49,3 +50,7 @@ If you're using the `--require` method or importing `@dotcom-reliability-kit/ope
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/opentelemetry/package.json b/packages/opentelemetry/package.json
index 2eb9320a..d0a9a64c 100644
--- a/packages/opentelemetry/package.json
+++ b/packages/opentelemetry/package.json
@@ -11,7 +11,7 @@
 	"bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: opentelemetry\"",
 	"license": "MIT",
 	"engines": {
-		"node": "22.x || 24.x"
+		"node": "^22.12 || ^24"
 	},
 	"main": "lib/index.js",
 	"types": "types/index.d.ts",
diff --git a/packages/serialize-error/docs/migration.md b/packages/serialize-error/docs/migration.md
index 93870b49..6aaa0353 100644
--- a/packages/serialize-error/docs/migration.md
+++ b/packages/serialize-error/docs/migration.md
@@ -16,6 +16,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v4 to v5](#migrating-from-v4-to-v5)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -44,3 +45,7 @@ Emoji           | Label             | Meaning
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/serialize-error/package.json b/packages/serialize-error/package.json
index 01653118..6364c6d5 100644
--- a/packages/serialize-error/package.json
+++ b/packages/serialize-error/package.json
@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: serialize-error\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts"
diff --git a/packages/serialize-request/docs/migration.md b/packages/serialize-request/docs/migration.md
index 2e8f0fb1..94384798 100644
--- a/packages/serialize-request/docs/migration.md
+++ b/packages/serialize-request/docs/migration.md
@@ -16,6 +16,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v4 to v5](#migrating-from-v4-to-v5)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -44,3 +45,7 @@ Emoji           | Label             | Meaning
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).
diff --git a/packages/serialize-request/package.json b/packages/serialize-request/package.json
index 71d842ae..1c817e8c 100644
--- a/packages/serialize-request/package.json
+++ b/packages/serialize-request/package.json
@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: serialize-request\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts",
diff --git a/resources/logos/package.json b/resources/logos/package.json
index 19d87cbe..4183a03b 100644
--- a/resources/logos/package.json
+++ b/resources/logos/package.json
@@ -12,7 +12,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "scripts": {
     "build": "./scripts/build.js"