chore(cli-engine): bump to 0.6.0 and carry the engine transition exceptions forward

0.5.0 reached the registry after #233, so the changed engine ships
under 0.6.0. The recorded engine-pin exceptions move with it: they
expire when the families release peering 0.6.0 and the follow-up bump
pins those releases.

The conformance task now also depends on the prisma package build.
The import-purity sweep reads packages/prisma/dist, but nothing in the
shell depends on that package, so turbo could run the sweep before the
build finished and report that no built JavaScript was swept.

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

Author: wmadden-electric

packages/cli-engine/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma/cli-engine",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "description": "The execution engine of the unified Prisma CLI.",
   "type": "module",
   "exports": {

packages/cli/package.json

@@ -49,7 +49,7 @@
   },
   "dependencies": {
     "@manypkg/tools": "^2.1.2",
-    "@prisma/cli-engine": "workspace:0.5.0",
+    "@prisma/cli-engine": "workspace:0.6.0",
     "@prisma/composer-cli": "0.21.0",
     "@prisma/compute-sdk": "0.42.0",
     "@prisma/management-api-sdk": "1.69.0",

packages/cli/scripts/conformance.ts

@@ -113,25 +113,25 @@ async function tarball(): Promise<readonly Finding[]> {
       // in flight: the engine must publish before a family can peer it,
       // so the mismatch is real until both families release against it.
       // The entries expire with the versions they name, and the PR that
-      // pins the families' 0.5.0-peering releases removes them; while
+      // pins the families' 0.6.0-peering releases removes them; while
       // they stand, a release could ship the two-engine install they
       // describe, which is why they must not outlive the transition.
       exceptions: [
         {
           familyPackage: "@prisma/composer-cli",
           familyPin: "0.4.0",
-          shellPin: "0.5.0",
-          reason: "engine 0.5.0 must publish before composer-cli can peer it",
+          shellPin: "0.6.0",
+          reason: "engine 0.6.0 must publish before composer-cli can peer it",
           removeWhen:
-            "composer-cli releases peering 0.5.0 and the follow-up bump PR pins that release",
+            "composer-cli releases peering 0.6.0 and the follow-up bump PR pins that release",
         },
         {
           familyPackage: "@prisma/orm-toolchain",
           familyPin: "0.4.0",
-          shellPin: "0.5.0",
-          reason: "engine 0.5.0 must publish before orm-toolchain can peer it",
+          shellPin: "0.6.0",
+          reason: "engine 0.6.0 must publish before orm-toolchain can peer it",
           removeWhen:
-            "orm-toolchain releases peering 0.5.0 and the follow-up bump PR pins that release",
+            "orm-toolchain releases peering 0.6.0 and the follow-up bump PR pins that release",
         },
       ],
       channel: CHANNEL,

packages/prisma/package.json

@@ -50,7 +50,7 @@
   },
   "dependencies": {
     "@manypkg/tools": "^2.1.2",
-    "@prisma/cli-engine": "workspace:0.5.0",
+    "@prisma/cli-engine": "workspace:0.6.0",
     "@prisma/composer-cli": "0.21.0",
     "@prisma/compute-sdk": "0.42.0",
     "@prisma/management-api-sdk": "1.69.0",

pnpm-lock.yaml

@@ -49,8 +49,10 @@
     "conformance": {
       // Packs and installs the real tarballs, so never cached; the
       // package's own build is a dependency because the entry reads
-      // dist/ before packing rebuilds it.
-      "dependsOn": ["build"],
+      // dist/ before packing rebuilds it, and so is the prisma
+      // package's, whose dist/ the import-purity sweep reads too but
+      // which nothing here depends on.
+      "dependsOn": ["build", "prisma#build"],
       "cache": false,
       // turbo passes only declared variables to a task, and the
       // dev-build check answers differently per channel. Undeclared, it