deps(cli): composer 0.6.0-dev.16, and the node floor follows it down

composer 0.6.0-dev.16 pins @prisma/cli-engine 0.0.9, the first published
engine carrying `installsPackages` on CommandDefinition. That is what the
mount in packages/cli/src/v8/cli.ts needs, so `pnpm typecheck` goes from
failing to clean with no change to the mount itself.

dev.16 also drops composer's own Node requirement from >=24 to >=22.18.0.
This branch had raised @prisma/cli to >=24 only because composer demanded
it, so that raise and everything it dragged along come back down:

- packages/cli/package.json engines: >=24 -> >=22.18.0, matching composer
  exactly.
- root package.json engines: >=24 -> >=22.18.0. Not the >=22.13.0 it was
  before, because the workspace has to be developable against its highest
  package floor, and that is now @prisma/cli at 22.18.0.
- .node-version: back to 22.22.3, the version main still uses, which
  satisfies every floor in the repo.
- CONTRIBUTING.md, README.md, docs/onboarding/getting-started.md and
  packages/cli/README.md: "Node.js 24 or newer" -> "Node.js 22.18 or
  newer".

@prisma/cli-engine keeps its own >=22.12.0. composer depends on the
engine, so raising the engine's floor would push that floor back onto
composer through the dependency.

CI needs no change. The workflows reading .node-version follow it back to
22.22.3, and test.yml, test-e2e.yml and publish-compute.yml pin
node-version: 24 directly, which predates this branch and still satisfies
every floor.

An install still resolves two engine copies, not one: the packed CLI
depends on @prisma/cli-engine 8.0.0-rc.1, its own workspace build, while
composer pins the published 0.0.9. Two exact pins on two release lines
cannot dedupe, so dev.16's move from 0.0.7 to 0.0.9 does not change the
count.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

Author: wmadden-electric

.node-version

@@ -1 +1 @@
-24.19.0
+22.22.3

CONTRIBUTING.md

@@ -10,7 +10,7 @@ is unclear, update the relevant product doc before changing the command surface.
 
 Requirements:
 
-- Node.js 24 or newer
+- Node.js 22.18 or newer
 - pnpm 10
 
 Install dependencies:

README.md

@@ -47,7 +47,7 @@ pnpm prisma app deploy
 
 Requirements:
 
-- Node.js 24 or newer
+- Node.js 22.18 or newer
 - pnpm 10+
 
 Install dependencies:

docs/onboarding/getting-started.md

@@ -4,7 +4,7 @@ This guide gets a local checkout ready for CLI development.
 
 ## Requirements
 
-- Node.js 24 or newer
+- Node.js 22.18 or newer
 - pnpm 10
 
 ## Install

package.json

@@ -3,7 +3,7 @@
   "version": "8.0.0-rc.1",
   "private": true,
   "engines": {
-    "node": ">=24"
+    "node": ">=22.18.0"
   },
   "packageManager": "pnpm@11.6.0",
   "scripts": {

packages/cli/README.md

@@ -104,7 +104,7 @@ npx prisma-cli app promote <deployment-id>
 
 ## Beta notes
 
-- Requires Node.js 24 or newer.
+- Requires Node.js 22.18 or newer.
 - This is a beta package and may change quickly.
 - Official beta releases publish as `@prisma/cli`.
 - The package binary is `prisma-cli`, not `prisma`, during beta.

packages/cli/package.json

@@ -18,7 +18,7 @@
     "access": "public"
   },
   "engines": {
-    "node": ">=24"
+    "node": ">=22.18.0"
   },
   "keywords": [
     "prisma",
@@ -47,7 +47,7 @@
   "dependencies": {
     "@clack/prompts": "1.5.0",
     "@prisma/cli-engine": "workspace:8.0.0-rc.1",
-    "@prisma/composer": "0.6.0-dev.15",
+    "@prisma/composer": "0.6.0-dev.16",
     "@prisma/compute-sdk": "0.39.0",
     "@prisma/credentials-store": "^7.8.0",
     "@prisma/management-api-sdk": "1.55.0",