Engine 0.2.1: ship the changed engine and carry the family transition

pnpm bump-cli-engine-version patch — the c12 resolution change is
compatible, and published engine versions are immutable, so the changed
engine needs a new version. The families on the registry still peer
engine 0.2.0, which they must until 0.2.1 publishes, so the tarball
check carries two recorded exceptions for the transition; the follow-up
PR that pins the families' 0.2.1-peering releases removes them.

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.2.0",
+  "version": "0.2.1",
   "description": "The execution engine of the unified Prisma CLI.",
   "type": "module",
   "exports": {

packages/cli/package.json

@@ -48,7 +48,7 @@
     "conformance": "tsx scripts/conformance.ts"
   },
   "dependencies": {
-    "@prisma/cli-engine": "workspace:0.2.0",
+    "@prisma/cli-engine": "workspace:0.2.1",
     "@prisma/composer-cli": "0.12.0",
     "@prisma/compute-sdk": "0.39.0",
     "@prisma/credentials-store": "^7.8.0",

packages/prisma/package.json

@@ -43,7 +43,7 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@prisma/cli-engine": "workspace:0.2.0",
+    "@prisma/cli-engine": "workspace:0.2.1",
     "@prisma/composer-cli": "0.11.0",
     "@prisma/compute-sdk": "0.39.0",
     "@prisma/credentials-store": "^7.8.0",