@prisma/composer 0.25.0-dev.4 → 0.25.0-dev.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@prisma/composer",
3
- "version": "0.25.0-dev.4",
3
+ "version": "0.25.0-dev.5",
4
4
  "type": "module",
5
5
  "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.",
6
6
  "exports": {
@@ -39,15 +39,15 @@
39
39
  "@prisma/management-api-sdk": "^1.80.0"
40
40
  },
41
41
  "devDependencies": {
42
- "@internal/assemble": "0.25.0-dev.4",
43
- "@internal/cli": "0.25.0-dev.4",
44
- "@internal/core": "0.25.0-dev.4",
45
- "@internal/foundation": "0.25.0-dev.4",
46
- "@internal/lowering": "0.25.0-dev.4",
47
- "@internal/nextjs": "0.25.0-dev.4",
48
- "@internal/node": "0.25.0-dev.4",
49
- "@internal/service-rpc": "0.25.0-dev.4",
50
- "@internal/tsdown-config": "0.25.0-dev.4",
42
+ "@internal/assemble": "0.25.0-dev.5",
43
+ "@internal/cli": "0.25.0-dev.5",
44
+ "@internal/core": "0.25.0-dev.5",
45
+ "@internal/foundation": "0.25.0-dev.5",
46
+ "@internal/lowering": "0.25.0-dev.5",
47
+ "@internal/nextjs": "0.25.0-dev.5",
48
+ "@internal/node": "0.25.0-dev.5",
49
+ "@internal/service-rpc": "0.25.0-dev.5",
50
+ "@internal/tsdown-config": "0.25.0-dev.5",
51
51
  "@types/node": "^26.0.1",
52
52
  "tsdown": "^0.22.7",
53
53
  "typescript": "^6.0.3"
@@ -2,7 +2,7 @@
2
2
  name: prisma-composer-core-concepts
3
3
  metadata:
4
4
  library: "@prisma/composer"
5
- library_version: "0.25.0-dev.4"
5
+ library_version: "0.25.0-dev.5"
6
6
  version: 2026.9.1
7
7
  description: >-
8
8
  Use when deploying or managing an app that uses Prisma Composer
@@ -276,6 +276,11 @@ including the first schema of a new database, follows one loop:
276
276
  4. Commit `migrations/` with the change, then deploy. A fresh database
277
277
  replays the whole path from empty.
278
278
 
279
+ Every service that uses the database deploys only after its migration
280
+ completes: a failed migration means the new code does not ship. The old
281
+ code serves against the new schema until the new deployment is live, so
282
+ keep each migration compatible with the code it replaces.
283
+
279
284
  If no authored path reaches the target contract, deploy (and `dev` against a
280
285
  stale local database) refuses with `MIGRATION_PATH_NOT_FOUND`; its message
281
286
  lists the two ways out: author the missing migration, or, when iterating