@prisma/composer 0.20.0-dev.8 → 0.20.0-dev.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma/composer",
-  "version": "0.20.0-dev.8",
+  "version": "0.20.0-dev.9",
   "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 @@
     "@prisma/management-api-sdk": "^1.60.0"
   },
   "devDependencies": {
-    "@internal/assemble": "0.20.0-dev.8",
-    "@internal/cli": "0.20.0-dev.8",
-    "@internal/core": "0.20.0-dev.8",
-    "@internal/foundation": "0.20.0-dev.8",
-    "@internal/lowering": "0.20.0-dev.8",
-    "@internal/nextjs": "0.20.0-dev.8",
-    "@internal/node": "0.20.0-dev.8",
-    "@internal/service-rpc": "0.20.0-dev.8",
-    "@internal/tsdown-config": "0.20.0-dev.8",
+    "@internal/assemble": "0.20.0-dev.9",
+    "@internal/cli": "0.20.0-dev.9",
+    "@internal/core": "0.20.0-dev.9",
+    "@internal/foundation": "0.20.0-dev.9",
+    "@internal/lowering": "0.20.0-dev.9",
+    "@internal/nextjs": "0.20.0-dev.9",
+    "@internal/node": "0.20.0-dev.9",
+    "@internal/service-rpc": "0.20.0-dev.9",
+    "@internal/tsdown-config": "0.20.0-dev.9",
     "@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.20.0-dev.8"
+  library_version: "0.20.0-dev.9"
   version: 2026.9.1
 description: >-
   Use when deploying or managing an app that uses Prisma Composer
@@ -422,7 +422,7 @@ provision exactly like your own:
 | `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` |
+| `auth` from `/auth` | Signup, login, sessions, and JWT verification (Better Auth in one service, own database). `auth({ signUp: 'closed' })` makes Better Auth refuse self-service sign-up; operator-created accounts go through `admin.createUser({ email, name, password?, emailVerified? })` from a service wired to `admin` (it throws on a duplicate email and sends no mail) | `api`, `session`, `admin` |
 | `email` from `/email` | Transactional email with a stored outbox (own service and database) | `send`, `outbox` |
 
 `bucket()` (imported alongside `rawPostgres`) is a raw S3-compatible bucket:
@@ -477,6 +477,15 @@ today the blocks above plus your own Modules are the whole set, so verify a
    contract columns compiles and deploys, then fails on the first timestamp
    read. Provide the global at the server entry
    (`import 'temporal-polyfill/global'`) or use string column types.
+10. **The auth module's `/api/auth/*` returns `403 MISSING_OR_NULL_ORIGIN`
+    to a Node script.** It is the browser surface: Better Auth origin-checks
+    any request carrying a cookie, an `Origin`/`Referer`, or a `Sec-Fetch-*`
+    header, and Node's built-in `fetch` sends `Sec-Fetch-Mode` on every
+    request (the same `curl` passes). Send an `Origin` equal to the module's
+    `baseUrl`, or, for provisioning, don't use that surface at all: call
+    `admin.createUser` from a service wired to the `admin` port. A deployed
+    stack's rpc ports are reachable only from inside its graph, so the app
+    exposes its own operator route that makes that call.
 
 ## What Composer doesn't do yet