[wmadden-electric]

8.0.0-rc.23 → 8.0.0-rc.24

$ prisma dev module.ts --detach         # returns once every service answers
$ curl "$(prisma dev url gateway)"      # a pipe gets the bare URL
$ prisma emulator list | cut -f2,3      # instance id and URL, tab-separated
$ prisma project list --json | jq '.envelope.result.items[].id'
$ prisma dev stop

This release ships the CLI on these product versions:

Package	Before	After
@prisma/composer-cli, @prisma/composer	0.30.0	0.32.0 (#355, #357)
@prisma/orm-toolchain	8.0.0-rc.18	8.0.0-rc.18
@prisma/cli-engine (packed)	0.7.0	0.9.0 (#349, #353)

What ships since rc.23

• Breaking for scripts: piping a prisma command gives its plain data, and JSON needs --json (feat!: piping a prisma command gives its plain data; JSON needs --json #353). Until rc.23, the CLI printed JSON whenever stdout was not a terminal. Now a pipe gets the command's data lines:

  • a list prints one tab-separated line per item;
  • a show prints key<TAB>value lines;
  • a command that returns one value, such as a URL or a new id, prints that value alone.

  Errors in a pipe are human errors on stderr, with the same exit code. A script that parsed piped output as JSON must now pass --json (or --format json).

• prisma dev url, prisma dev stop, prisma emulator list and prisma dev --detach, from Composer 0.32.0 (feat: add prisma dev url, prisma dev stop and prisma emulator list (Composer 0.31.0) #355, Follow the products' released versions: @prisma/composer-cli 0.31.0 -> 0.32.0; @prisma/composer 0.31.0 -> 0.32.0 #357).

  • prisma dev url <address> prints the local URL of a service, database or bucket that prisma dev runs from this directory.
  • prisma dev stop stops that app, keeping its data and ports.
  • prisma emulator list lists the local emulators (the programs on this machine that run your services, databases and buckets in place of Prisma Cloud) and every instance they hold.
  • prisma dev --detach starts the app, returns once every service answers, and leaves it running until prisma dev stop.

• prisma dev is both a command and a group (feat(engine): a command can also have subcommands, so prisma dev <entry> and prisma dev url can coexist #349). prisma dev <entry> still runs the app, and prisma dev url and prisma dev stop sit beneath it. A child command's name wins over the entry argument; prisma dev -- url passes url as the entry.

• The DEV.* error codes these commands raise are in the error reference (Follow Composer 0.32.0, and list the DEV error codes so their docs links resolve #356), so the docs link in each of those errors now leads to an entry.

• The npm READMEs name Prisma Postgres and Prisma Compute (docs(readme): name Prisma Postgres and Prisma Compute in the npm READMEs #348).

See docs/oss/versioning.md. Merging this PR ships the release:

• The squashed push to main changes the root version.
• The Publish to npm workflow then publishes @prisma/cli and prisma under latest. @prisma/cli-engine 0.9.0 was already published when feat!: piping a prisma command gives its plain data; JSON needs --json #353 merged, so that step does nothing for the engine.
• A pre-release GitHub Release is created with generated notes. This repo has no committed release-notes file; review the generated notes on the Release after merge.

Checks run locally: typecheck, CLI tests, check:conformance, check:grammar, check:error-reference, check:skill-packaging, the engine version check and Biome. Conformance passes with its existing allowed exceptions: Composer and the ORM toolchain still peer CLI engine 0.7.0, while the shell ships 0.9.0.

Agent: attila-51

🤖 Generated with Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: ce180e89-8757-4cc7-8a51-6adc02a8433c

📥 Commits

Reviewing files that changed from the base of the PR and between 8c50b9e and 8b8ba96.

⛔ Files ignored due to path filters: 1

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing: 9

• package.json
• packages/cli-conformance/package.json
• packages/cli-engine/package.json
• packages/cli-telemetry/package.json
• packages/cli/package.json
• packages/compute/package.json
• packages/prisma/package.json
• packages/tsconfig/package.json
• skills/prisma-platform-core-concepts/SKILL.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Summary by CodeRabbit

• Chores
  • Updated the release version from 8.0.0-rc.23 to 8.0.0-rc.24 across the project.
  • Synchronized internal package references and development tooling with the new release version.
  • Updated Prisma platform skill metadata to reference the latest release candidate.

Walkthrough

Package versions and workspace dependency references were updated from 8.0.0-rc.23 to 8.0.0-rc.24. The Prisma platform core concepts skill metadata now targets 8.0.0-rc.24.

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to 8b8ba

No actionable merge-blocking risk was identified.

Architecture risk: 🔵 Low · up to 8b8ba

The change affects 9 systems.

Changed systems: package.json, packages/cli, packages/cli-conformance, packages/cli-engine, packages/cli-telemetry, packages/compute, packages/prisma, packages/tsconfig, skills

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — package.json (service) was modified; 1 changed file maps to changed impact.
• observed — packages/cli (library) was modified; 1 changed file maps to changed impact.
• observed — packages/cli-conformance (library) was modified; 1 changed file maps to changed impact.
• observed — packages/cli-engine (library) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in package.json: The package version changed from 8.0.0-rc.23 to 8.0.0-rc.24.
• observed — Modified behavior in packages/cli-conformance/package.json: The package version was updated from 8.0.0-rc.23 to 8.0.0-rc.24.
• observed — Modified behavior in packages/cli-conformance/package.json: The workspace @repo/tsconfig development dependency was updated from 8.0.0-rc.23 to 8.0.0-rc.24.
• observed — Modified behavior in packages/cli-engine/package.json: Both workspace devDependencies now use release 8.0.0-rc.24 instead of 8.0.0-rc.23.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly and concisely describes the primary change: updating the CLI to version 8.0.0-rc.24.
Description check		The description is directly related to the version bump and details the release contents, package versions, publishing behavior, and validation checks.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (9 skipped: 9 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

✨ Simplify code

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[pkg-pr-new]

Open in StackBlitz

npx https://pkg.pr.new/@prisma/cli@358

npx https://pkg.pr.new/@prisma/cli-engine@358

commit: 8b8ba96