@prisma/composer 0.17.0-dev.3 → 0.17.0-dev.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma/composer",
-  "version": "0.17.0-dev.3",
+  "version": "0.17.0-dev.5",
   "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 `prisma-composer` CLI lives in @prisma/composer-cli.",
   "exports": {
@@ -40,15 +40,15 @@
   },
   "devDependencies": {
     "@effect/vitest": "4.0.0-rc.112",
-    "@internal/assemble": "0.17.0-dev.3",
-    "@internal/cli": "0.17.0-dev.3",
-    "@internal/core": "0.17.0-dev.3",
-    "@internal/foundation": "0.17.0-dev.3",
-    "@internal/lowering": "0.17.0-dev.3",
-    "@internal/nextjs": "0.17.0-dev.3",
-    "@internal/node": "0.17.0-dev.3",
-    "@internal/service-rpc": "0.17.0-dev.3",
-    "@internal/tsdown-config": "0.17.0-dev.3",
+    "@internal/assemble": "0.17.0-dev.5",
+    "@internal/cli": "0.17.0-dev.5",
+    "@internal/core": "0.17.0-dev.5",
+    "@internal/foundation": "0.17.0-dev.5",
+    "@internal/lowering": "0.17.0-dev.5",
+    "@internal/nextjs": "0.17.0-dev.5",
+    "@internal/node": "0.17.0-dev.5",
+    "@internal/service-rpc": "0.17.0-dev.5",
+    "@internal/tsdown-config": "0.17.0-dev.5",
     "@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.17.0-dev.3"
+  library_version: "0.17.0-dev.5"
   version: 2026.9.1
 description: >-
   Use when deploying or managing an app that uses Prisma Composer
@@ -239,7 +239,7 @@ Two kinds of Postgres dependency:
    `prisma contract emit`) is referenced by both the dependency end
    (`deps: { db: postgres(catalogData) }`) and the resource end, which also
    names the `prisma.config.ts` path so the deploy's migration step can
-   find `migrations/`.
+   reload the emitted `contract.json` and find `migrations/`.
 
 **Deploys are replay-only**: they apply the migrations committed under
 `migrations/` and never create schema themselves. Every schema change,
@@ -256,8 +256,12 @@ If no authored path reaches the target contract, deploy (and `dev` against a
 stale local database) refuses with `MIGRATION_PATH_NOT_FOUND`; its message
 lists the two ways out: author the missing migration, or, when iterating
 against a local
-database only, `prisma db update`. Never skip step 3 before a deploy. See
-`examples/store/modules/catalog` for the complete pattern.
+database only, `prisma db update`. The tracked migration resource persists only
+compact contract identity in deploy state; if the emitted contract artifact
+named by `prisma.config.ts` is missing, unreadable, or no longer matches the
+declared `dataContract(...)` value, deploy fails before touching the database.
+Never skip step 3 before a deploy. See `examples/store/modules/catalog` for the
+complete pattern.
 
 ## Deploy model: converge, don't script
 
@@ -407,7 +411,7 @@ provision exactly like your own:
 
 | Import | What it provisions | Exposes |
 | --- | --- | --- |
-| `cron` from `/cron` | An always-on scheduler firing your schedule at your runner service | nothing |
+| `cron` from `/cron` | An always-on scheduler (it holds Compute's keep-awake guard) firing your schedule at your runner service; `input` on `cron()` binds the runner's input schema | nothing |
 | `storage` from `/storage` | An S3-backed blob store (own Postgres + minted credentials) | `store` |
 | `streams` from `/streams` | Durable append-only event streams over a `store` | `streams` |
 | `auth` from `/auth` | Signup, login, sessions, and JWT verification (Better Auth in one service, own database) | `api`, `session`, `admin` |