prisma 8.0.0-rc.27-dev.169 → 8.0.0-rc.27-dev.170

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/dist/prisma.js CHANGED
@@ -14291,6 +14291,7 @@ const cliGroups = {
14291
14291
  description: "A ref is a named pointer to a contract, letting commands target a contract by a stable name. Set, list, and delete refs here."
14292
14292
  },
14293
14293
  orm: { brief: "Initialize a Prisma ORM project" },
14294
+ deploy: { brief: "Deploy your app to Prisma Cloud, and list what a stage has deployed" },
14294
14295
  dev: { brief: "Run your app on this machine, with no Prisma account. Start it, print a node's local URL, stop it" },
14295
14296
  emulator: {
14296
14297
  brief: "Inspect the local emulators: programs on this machine that stand in for Prisma Cloud during 'prisma dev'",
@@ -14359,6 +14360,7 @@ const mountedCommands = {
14359
14360
  "service domain retry": serviceDomainRetryCommand,
14360
14361
  "service domain wait": serviceDomainWaitCommand,
14361
14362
  deploy: composerCommandFamily.commands.deploy,
14363
+ "deploy list": composerCommandFamily.commands["deploy list"],
14362
14364
  dev: composerCommandFamily.commands.dev,
14363
14365
  "dev url": composerCommandFamily.commands["dev url"],
14364
14366
  "dev stop": composerCommandFamily.commands["dev stop"],
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "prisma",
3
- "version": "8.0.0-rc.27-dev.169",
3
+ "version": "8.0.0-rc.27-dev.170",
4
4
  "description": "The Prisma CLI: one binary for the ORM, Composer, and the Prisma Developer Platform.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -45,10 +45,10 @@
45
45
  "dependencies": {
46
46
  "@manypkg/tools": "^2.1.2",
47
47
  "@prisma/cli-engine": "0.9.0",
48
- "@prisma/composer-cli": "0.34.0-dev.4",
48
+ "@prisma/composer-cli": "0.35.0-dev.1",
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.20-dev.11",
51
+ "@prisma/orm-toolchain": "8.0.0-rc.20-dev.13",
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.27-dev.169",
60
+ "@prisma/cli": "8.0.0-rc.27-dev.170",
61
61
  "@prisma/credentials-store": "^7.8.0",
62
- "@repo/cli-telemetry": "8.0.0-rc.27-dev.169",
63
- "@repo/tsconfig": "8.0.0-rc.27-dev.169",
62
+ "@repo/cli-telemetry": "8.0.0-rc.27-dev.170",
63
+ "@repo/tsconfig": "8.0.0-rc.27-dev.170",
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.27-dev.169"
5
+ library_version: "8.0.0-rc.27-dev.170"
6
6
  version: 2026.9.2
7
7
  description: >-
8
8
  Use when hosting, deploying, or operating an app on the Prisma Platform:
@@ -94,6 +94,7 @@ import { defineConfig as orm } from "@prisma/orm-postgres/config";
94
94
 
95
95
  export default definePrismaConfig({
96
96
  composer: composer({
97
+ entry: "./module.ts",
97
98
  extensions: [prismaCloud(), nodeBuild()],
98
99
  state: prismaState(),
99
100
  }),
@@ -144,7 +145,7 @@ branch is the environment, and branches come into being by deploying to them:
144
145
  1. **Push a git branch** (with the GitHub integration connected and the
145
146
  deploy workflow in the repository): the workflow builds and deploys, and
146
147
  the platform creates the branch environment on the fly.
147
- 2. **Deploy a stage from the CLI**: `prisma deploy module.ts --stage pr-42`
148
+ 2. **Deploy a stage from the CLI**: `prisma deploy --stage pr-42`
148
149
  creates a branch named `pr-42` and deploys the identical app graph into
149
150
  it. A stage name must be a valid git ref name; an invalid name is a hard
150
151
  error.
@@ -208,8 +209,11 @@ Opening a pull request does not itself deploy anything; previews track
208
209
  branch pushes. A connected repository without the workflow gets branch
209
210
  bookkeeping and preview teardown from the platform, and no builds.
210
211
 
211
- **CLI.** `prisma deploy module.ts` deploys production directly; add
212
- `--stage <name>` for a preview. Authenticate once with `prisma auth login`
212
+ **CLI.** `prisma deploy` deploys production directly; add `--stage <name>`
213
+ for a preview. It deploys the entry file named by `entry` in the `composer`
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
216
+ and URL. Authenticate once with `prisma auth login`
213
217
  (interactive), or set `PRISMA_SERVICE_TOKEN` (plus `PRISMA_WORKSPACE_ID`
214
218
  when the token can see more than one workspace) for CI and other headless
215
219
  runs. The first deploy creates the project, named after your module; the
@@ -350,7 +354,7 @@ over deploying whenever you want to show the user a change or verify your
350
354
  own work:
351
355
 
352
356
  1. Build the app exactly as you would for deploy, then run
353
- `prisma dev module.ts`. It provisions a local Prisma Postgres database,
357
+ `prisma dev` (it runs the config's `entry`, like deploy). It provisions a local Prisma Postgres database,
354
358
  applies the schema, creates local stand-ins for declared buckets, starts
355
359
  the services, and prints a local URL. It watches built output and
356
360
  restarts a service when its build changes.