prisma 8.0.0-rc.29-dev.175 → 8.0.0-rc.29-dev.176

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",
3
- "version": "8.0.0-rc.29-dev.175",
3
+ "version": "8.0.0-rc.29-dev.176",
4
4
  "description": "The Prisma CLI: one binary for the ORM, Composer, and the Prisma Developer Platform.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -48,7 +48,7 @@
48
48
  "@prisma/composer-cli": "0.36.0-dev.2",
49
49
  "@prisma/compute-sdk": "0.43.0",
50
50
  "@prisma/management-api-sdk": "1.80.0",
51
- "@prisma/orm-toolchain": "8.0.0-rc.21-dev.20",
51
+ "@prisma/orm-toolchain": "8.0.0-rc.21-dev.21",
52
52
  "@vercel/detect-agent": "^1.2.3",
53
53
  "better-result": "^2.9.2",
54
54
  "cross-spawn": "^7.0.6",
@@ -57,10 +57,10 @@
57
57
  "open": "^11.0.0"
58
58
  },
59
59
  "devDependencies": {
60
- "@prisma/cli": "8.0.0-rc.29-dev.175",
60
+ "@prisma/cli": "8.0.0-rc.29-dev.176",
61
61
  "@prisma/credentials-store": "^7.8.0",
62
- "@repo/cli-telemetry": "8.0.0-rc.29-dev.175",
63
- "@repo/tsconfig": "8.0.0-rc.29-dev.175",
62
+ "@repo/cli-telemetry": "8.0.0-rc.29-dev.176",
63
+ "@repo/tsconfig": "8.0.0-rc.29-dev.176",
64
64
  "@types/node": "^22.19.19",
65
65
  "tsdown": "^0.21.10",
66
66
  "typescript": "^6.0.3",
@@ -2,7 +2,7 @@
2
2
  name: prisma-platform-core-concepts
3
3
  metadata:
4
4
  library: "prisma"
5
- library_version: "8.0.0-rc.29-dev.175"
5
+ library_version: "8.0.0-rc.29-dev.176"
6
6
  version: 2026.9.2
7
7
  description: >-
8
8
  Use when hosting, deploying, or operating an app on the Prisma Platform:
@@ -145,10 +145,10 @@ branch is the environment, and branches come into being by deploying to them:
145
145
  1. **Push a git branch** (with the GitHub integration connected and the
146
146
  deploy workflow in the repository): the workflow builds and deploys, and
147
147
  the platform creates the branch environment on the fly.
148
- 2. **Deploy a stage from the CLI**: `prisma deploy --stage pr-42`
148
+ 2. **Deploy an environment from the CLI**: `prisma deploy --environment pr-42`
149
149
  creates a branch named `pr-42` and deploys the identical app graph into
150
- it. A stage name must be a valid git ref name; an invalid name is a hard
151
- error.
150
+ it. An environment name must be a valid git ref name; an invalid name is
151
+ a hard error.
152
152
 
153
153
  A preview branch that needs a database gets a fresh, empty one, wired in as a
154
154
  branch-scoped `DATABASE_URL`. Preview work can never touch production data
@@ -209,10 +209,10 @@ Opening a pull request does not itself deploy anything; previews track
209
209
  branch pushes. A connected repository without the workflow gets branch
210
210
  bookkeeping and preview teardown from the platform, and no builds.
211
211
 
212
- **CLI.** `prisma deploy` deploys production directly; add `--stage <name>`
212
+ **CLI.** `prisma deploy` deploys production directly; add `--environment <name>`
213
213
  for a preview. It deploys the entry file named by `entry` in the `composer`
214
214
  section of `prisma.config.ts`; `--entry <path>` overrides it. `prisma deploy
215
- list` (same `--stage`) lists each deployed node's address, kind, platform ID
215
+ list` (same `--environment`) lists each deployed node's address, kind, platform ID
216
216
  and URL. Authenticate once with `prisma auth login`
217
217
  (interactive), or set `PRISMA_SERVICE_TOKEN` (plus `PRISMA_WORKSPACE_ID`
218
218
  when the token can see more than one workspace) for CI and other headless
@@ -372,7 +372,7 @@ own work:
372
372
  shows every local instance on the machine.
373
373
  4. Deploying is the same pipeline pointed at the platform: switching from
374
374
  local to hosted is a configuration change, not a code change. Reach for
375
- `prisma deploy --stage <name>` only when you need a shareable URL or
375
+ `prisma deploy --environment <name>` only when you need a shareable URL or
376
376
  platform behaviour (sleeping, real DNS, production-like config).
377
377
  5. For pure frontend iteration the framework's own dev server also works;
378
378
  the Composer local stack is what mirrors the deployed wiring.
@@ -397,8 +397,8 @@ Windows is not supported for the local stack yet.
397
397
  6. **Production shows a stale value after an environment-variable change.**
398
398
  Variables are resolved at deploy time. Re-deploy (or promote) so the new
399
399
  value is picked up.
400
- 7. **A stage name is rejected.** Stage names must be valid git ref names;
401
- rename it.
400
+ 7. **An environment name is rejected.** Environment names must be valid git
401
+ ref names; rename it.
402
402
  8. **A resource disappeared from the platform after a deploy.** It was
403
403
  removed from `module.ts`; the module is the source of truth and deploy
404
404
  converges to it. Restore the declaration and re-deploy.
@@ -422,9 +422,9 @@ Windows is not supported for the local stack yet.
422
422
  Name the gap instead of inventing an API:
423
423
 
424
424
  1. **No branch create or delete from the CLI.** The `branch` group only
425
- lists. Branches are created by pushing or by deploying a stage, and
426
- removed by deleting the upstream git branch; there is no CLI teardown
427
- verb for a stage yet.
425
+ lists. Branches are created by pushing or by deploying an environment,
426
+ and removed by deleting the upstream git branch; there is no CLI teardown
427
+ verb for an environment yet.
428
428
  2. **No build retry.** A failed build is finished; the retry is the next
429
429
  push or the next deploy.
430
430
  3. **No reading environment-variable values back**, anywhere. This is a