Bump to version 8.0.0-rc.21

[wmadden-electric]

8.0.0-rc.20 → 8.0.0-rc.21

This release ships CLI engine 0.6.3 with the products that peer it:

Package	Before	After
@prisma/cli-engine (packed)	0.6.2	0.6.3
@prisma/composer-cli, @prisma/composer	0.26.0	0.28.0
@prisma/orm-toolchain	8.0.0-rc.14	8.0.0-rc.16

Why

Engine 0.6.3 fixes prisma orm init and prisma contract emit failing on a valid contract in fresh Bun installs: engine 0.6.2 required ArkType 2.2.3 exactly, so the ORM packages got their own ArkType copy. 0.6.3 accepts ^2.2.7. It was published from the branch of #332, which then closed unmerged, so main still packed 0.6.2.

The conformance check requires every product this CLI mounts to peer exactly the engine it packs. ORM rc.16 (prisma/orm#30632) and Composer 0.28.0 (prisma/composer#342) are the first releases that peer 0.6.3, so this release moves all three together.

Commits

1. Engine 0.6.3 on main. Recreates fix(engine): allow ArkType to dedupe with ORM packages #332's engine change: arktype 2.2.3 → ^2.2.7, and pnpm bump-cli-engine-version 0.6.3. The engine packed from this commit is identical, file for file, to the published @prisma/cli-engine@0.6.3 tarball, so the publish run finds that version already on the registry and skips it.
2. Product versions, written by scripts/update-product-versions.mjs --channel release.
3. The version bump, by pnpm bump-version: every lockstep manifest, the lockfile and the skill's library_version. @prisma/compute's own version is untouched; only its @repo/tsconfig workspace pin moves, as in earlier bumps.

Checks run locally

• pnpm build and pnpm typecheck.
• pnpm conformance in packages/cli: 5 subjects checked, nothing to report. No exceptions are recorded.
• The engine's tests (1,025) and the CLI's tests (1,027) pass.
• One ArkType copy in the lockfile, and no @prisma/cli-engine peer warning.

Merging this PR ships the release: the squashed push to main changes the root version with the release marker, the Publish to npm workflow publishes @prisma/cli-engine (already published, skipped) and then @prisma/cli and prisma under latest, and a pre-release GitHub Release is created with generated notes. See docs/oss/versioning.md.

Agent: grendel-61

🤖 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: 4db77012-2c78-4aa6-8389-385dba47e264

📥 Commits

Reviewing files that changed from the base of the PR and between 471474a and ae6a7e0.

⛔ 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

• Updates
  • Updated Prisma packages and associated command-line tooling to release candidate 8.0.0-rc.21, with related package versions aligned.
  • This release contains version updates only; no end-user feature or behavior changes are noted.

Walkthrough

Package versions and dependency references were updated for the 8.0.0-rc.21 release. The cli-engine arktype dependency range changed from 2.2.3 to ^2.2.7. The platform core concepts skill metadata now specifies library version 8.0.0-rc.21.

Priority: ➖ Normal

Merge Risk: ⚪ Minimal · up to ae6a7

The release metadata is consistent with the lockfile, and the reported changes reveal no current merge-blocking risk.

Architecture Summary

Architecture risk: 🔵 Low · up to ae6a7

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.20 to 8.0.0-rc.21.
• observed — Modified behavior in packages/cli-conformance/package.json: The package version changed from 8.0.0-rc.20 to 8.0.0-rc.21.
• observed — Modified behavior in packages/cli-conformance/package.json: The @repo/tsconfig workspace dependency changed from 8.0.0-rc.20 to 8.0.0-rc.21.
• observed — Modified behavior in packages/cli-engine/package.json: The package version changes from 0.6.2 to 0.6.3.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the primary change: bumping the project to version 8.0.0-rc.21.
Description check	✅ Passed	The description explains the version bump, related package updates, and the reason for the release. It is directly related to the changeset.
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

• Autopilot · 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@336

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

commit: ae6a7e0

[wmadden-electric]

About the red engine-version check. It reports that packages/cli-engine changed while its version, 0.6.3, is already on the registry. That is true and expected here, and it does not block the release:

• @prisma/cli-engine@0.6.3 was published on 2026-10-06 from the branch of fix(engine): allow ArkType to dedupe with ORM packages #332 (npm provenance names commit bb37e738), and fix(engine): allow ArkType to dedupe with ORM packages #332 then closed unmerged. This PR brings that engine to main.
• The engine packed from this branch's engine commit is identical, file for file, to the published 0.6.3 tarball. Since that commit, the engine's manifest differs from bb37e738 only in the @repo/* dev dependencies the version bump sweeps, which the check itself treats as not shipping.
• engine-version is not a required check (Test, Type Check and Lint are). At publish, scripts/publish-packages.sh finds 0.6.3 already on the registry and continues, and verify-published.mjs only confirms that it resolves.

#332's branch has a commit, 79a63e3, that teaches the check to accept an already-published version whose engine source is unchanged since the commit its provenance records. I left it out: it changes the release pipeline's rules and was never reviewed. If you want the check green instead, I can add it to this PR.

Agent: grendel-61