@prisma/composer 0.30.0-dev.2 → 0.30.0-dev.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma/composer",
-  "version": "0.30.0-dev.2",
+  "version": "0.30.0-dev.3",
   "type": "module",
   "description": "Prisma Composer — build a Prisma App by composing Modules. Core authoring, deploy pipeline, and the service-rpc/node/nextjs authoring surfaces. The command family the `prisma` CLI mounts lives in @prisma/composer-cli.",
   "exports": {
@@ -39,15 +39,15 @@
     "@prisma/management-api-sdk": "^1.80.0"
   },
   "devDependencies": {
-    "@internal/assemble": "0.30.0-dev.2",
-    "@internal/cli": "0.30.0-dev.2",
-    "@internal/core": "0.30.0-dev.2",
-    "@internal/foundation": "0.30.0-dev.2",
-    "@internal/lowering": "0.30.0-dev.2",
-    "@internal/nextjs": "0.30.0-dev.2",
-    "@internal/node": "0.30.0-dev.2",
-    "@internal/service-rpc": "0.30.0-dev.2",
-    "@internal/tsdown-config": "0.30.0-dev.2",
+    "@internal/assemble": "0.30.0-dev.3",
+    "@internal/cli": "0.30.0-dev.3",
+    "@internal/core": "0.30.0-dev.3",
+    "@internal/foundation": "0.30.0-dev.3",
+    "@internal/lowering": "0.30.0-dev.3",
+    "@internal/nextjs": "0.30.0-dev.3",
+    "@internal/node": "0.30.0-dev.3",
+    "@internal/service-rpc": "0.30.0-dev.3",
+    "@internal/tsdown-config": "0.30.0-dev.3",
     "@types/node": "^26.0.1",
     "tsdown": "^0.22.7",
     "typescript": "^6.0.3"

package/skills/prisma-composer-core-concepts/SKILL.md

@@ -2,7 +2,7 @@
 name: prisma-composer-core-concepts
 metadata:
   library: "@prisma/composer"
-  library_version: "0.30.0-dev.2"
+  library_version: "0.30.0-dev.3"
   version: 2026.9.1
 description: >-
   Use when deploying or managing an app that uses Prisma Composer
@@ -443,6 +443,7 @@ that surprise:
    changes.
    `ready` prints only once every service accepts connections on its port, except a service declared `compute({ ..., listens: false })` (one that never listens, like the cron scheduler), which counts as running once its process starts. A service that exits before it listens, or does not listen within 30 seconds, fails `dev` (and stops the app's other services) with a message naming the service, its port, and its log file: on a first start it is in the deploy engine's output, before the error that the deploy engine exited (`DEV.CONVERGE_FAILED` from the `dev` operation); on a warm start it is the `DEV.SERVICE_START_FAILED` message. `PRISMA_COMPOSER_SERVICE_READY_TIMEOUT_MS` raises the 30-second limit (milliseconds); the compute emulator reads it when it starts, so a running emulator keeps its old value until its process ends. An emulator that does not accept connections fails `dev` and `log` with `DEV.EMULATOR_UNREACHABLE` after a few seconds of retries; nothing else is retried.
 2. Ctrl-C stops the app's processes but leaves local databases, buckets, and their data up: the next `dev` is a warm start. Starting clean, wiping this app's local instances and data first, is an explicit opt-in flag. On a fresh start, each service gets the lowest free port from 3000 up, in dependency order: a service before the services that call it, otherwise provision order. A warm start keeps the ports services already have.
+   Services belong to the directory `dev` runs in: two checkouts of one app (two git worktrees) run separate processes on separate ports and never restart each other's. `.prisma-composer/dev/emulator-instances.json` records which local service backs each service. A service keeps its port in its directory across runs, even while stopped. If its local service is gone (a Composer upgrade discarded the compute emulator's state), the next `dev` re-creates it and asks for the old port; when another directory has taken it, the service gets the lowest free port and `dev` prints `[dev] service "<address>" now uses port <new>: its previous port <old> is in use`. A directory runs one app at a time: running a different app there removes the previous app's local services and prints `[dev] removed the local services of "<app>", the app run here before`. A stopped service keeps its port reserved, so a deleted checkout's services keep theirs; there is no command to remove them yet. Local databases and buckets are still keyed by the app's name, so two checkouts of one app share them.
 3. `dev` does not print service logs. The `log` operation follows the
    already-running app's merged logs; it never builds, provisions, starts, or
    stops anything: