Skip to content

Follow the products' released versions: @prisma/composer-cli 0.24.0 -> 0.25.0; @prisma/composer 0.24.0 -> 0.25.0 - #323

Merged
prisma-bot merged 1 commit into
mainfrom
product-versions/20260929100227
Sep 29, 2026
Merged

prisma-bot merged 1 commit into
mainfrom
product-versions/20260929100227

Conversation

@prisma-bot

Copy link
Copy Markdown
Collaborator

Opened automatically by update-product-versions.yml, following the products' release dist-tags (@prisma/composer-cli 0.24.0 -> 0.25.0; @prisma/composer 0.24.0 -> 0.25.0). Merging publishes a dev version of the CLI; the conformance checks on this pull request are what stand between a product release and that dev build.

…> 0.25.0; @prisma/composer 0.24.0 -> 0.25.0

Opened automatically (update-product-versions.yml); merging ships a dev version of the CLI. A real release stays a human act.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
@prisma-bot
prisma-bot enabled auto-merge (squash) September 29, 2026 10:02
@coderabbitai

coderabbitai Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

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: 0f293733-10f2-4f39-8d4b-da1e997ef2d8

📥 Commits

Reviewing files that changed from the base of the PR and between e42f478 and e55d601.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • packages/cli/package.json
  • packages/prisma/package.json

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 internal package versions. No user-facing behavior changes are included in this update.

Walkthrough

The CLI package updates its @prisma/composer-cli runtime dependency and @prisma/composer development dependency from version 0.24.0 to 0.25.0. The Prisma package updates its @prisma/composer-cli dependency from version 0.24.0 to 0.25.0.

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to e55d6

This updates the CLI and Prisma Composer dependencies to 0.25.0. The selected versions and Node requirements align with the repository’s Node 24 workflows, so no actionable merge-blocking risk is evident.

Architecture Summary

Architecture risk: 🔵 Low · up to e55d6

The change affects 2 systems.

Changed systems: packages/cli, packages/prisma

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — packages/cli (library) was modified; 1 changed file maps to changed impact.
  • observed — packages/prisma (library) was modified; 1 changed file maps to changed impact.

Before / after behavior

  • observed — Modified behavior in packages/cli/package.json: The @prisma/composer-cli dependency version changes from 0.24.0 to 0.25.0.
  • observed — Modified behavior in packages/cli/package.json: The @prisma/composer development dependency version changes from 0.24.0 to 0.25.0.
  • observed — Modified behavior in packages/prisma/package.json: The declared @prisma/composer-cli dependency version changed from 0.24.0 to 0.25.0.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes the version updates for @prisma/composer-cli and @prisma/composer from 0.24.0 to 0.25.0.
Description check ✅ Passed The description accurately explains the automated version update and its effect on the dev build and conformance checks.
Docstring Coverage ✅ Passed 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 ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
✨ Simplify code
  • Commit to this branch
  • Create a new PR

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

@pkg-pr-new

pkg-pr-new Bot commented Sep 29, 2026

Copy link
Copy Markdown

Open in StackBlitz

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

commit: e55d601

@prisma-bot
prisma-bot merged commit 6884b44 into main Sep 29, 2026
18 of 27 checks passed
@prisma-bot
prisma-bot deleted the product-versions/20260929100227 branch September 29, 2026 10:32
kristof-siket added a commit that referenced this pull request Sep 29, 2026
8.0.0-rc.18 → 8.0.0-rc.19, per
[docs/oss/versioning.md](docs/oss/versioning.md).

**Merging this PR ships the release:** the squashed push to `main`
changes the root version, the `Publish to npm` workflow publishes
`@prisma/cli-engine`, then `@prisma/cli` and `prisma`, under `latest`,
and a pre-release GitHub Release is created with generated notes. Review
the generated notes on the Release after merge.

Notable since rc.18: `@prisma/composer` / `@prisma/composer-cli` 0.25.0
(#323). Composer now peers `@prisma/orm-postgres@8.0.0-rc.13`, the same
ORM release as this CLI's `@prisma/orm-toolchain`, so projects can pin
CLI, Composer and ORM consistently again (rc.18 paired an rc.13
toolchain with Composer's rc.12 peer).

Bump via `pnpm bump-version`: `package.json` files (version +
`workspace:` specifiers; `@prisma/compute`'s own version untouched),
`pnpm-lock.yaml`, and the core-concepts skill stamp.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Signed-off-by: Kristof Siket <siket@prisma.io>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants