Bump to version 8.0.0-rc.17

[wmadden-electric]

Release 8.0.0-rc.16 → 8.0.0-rc.17. 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, and creates a pre-release GitHub Release with generated notes. The engine stays at 0.6.1, which is already on npm, so it is not republished. Review the generated notes on the Release after the merge.

Why rc.17, not rc.16

main was bumped to 8.0.0-rc.16 in #282, but rc.16 never reached npm. Its publish run failed the conformance check: @prisma/composer-cli 0.22.0 peered @prisma/cli-engine 0.5.0 while the CLI ships 0.6.x, so two engine copies were installed. Version numbers are never reused, so rc.16 is skipped.

What this release ships

Dependency	rc.15 (current latest)	rc.17
@prisma/cli-engine	0.4.0	0.6.1
@prisma/orm-toolchain	8.0.0-rc.11	8.0.0-rc.12
@prisma/composer-cli / @prisma/composer	0.20.0	0.23.0
@prisma/compute-sdk	0.42.0	0.43.0

• The toolchain and composer pins follow the products' latest releases, the same change update-product-versions.yml makes. Composer 0.23.0 peers engine 0.6.1, and ORM 8.0.0-rc.12 was published today.
• compute-sdk 0.43.0 needed no code changes; typecheck and tests pass.
• @prisma/management-api-sdk stays at 1.69.0. The engine's public types come from its own dev copy of that SDK. If the CLI moved to 1.76.0 alone, the engine's client type and the CLI's would no longer match. Moving the engine's copy changes its published files and needs a new engine version, which the ORM and composer both pin exactly.

Verification

Passed locally:

• pnpm build

• pnpm typecheck

• pnpm lint

• pnpm check:grammar

• pnpm check:conformance in release mode: 5 subjects, nothing to report. This is the check that stopped rc.16.

• Tests:

  Package	Tests passed
  @prisma/cli	1,021
  @prisma/cli-engine	962
  @repo/cli-conformance	66
  @repo/cli-telemetry	49

Not run locally: the prisma and @prisma/compute test runs. My local clone sits inside another vitest workspace, so vitest found the wrong root config. CI runs them normally.

🤖 Generated with Claude Code

[coderabbitai]

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: 8b519773-8d82-40e0-b37b-dbf22723a2b4

📥 Commits

Reviewing files that changed from the base of the PR and between ab506c0 and b1a7d29.

⛔ 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: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

Summary by CodeRabbit

• Release Update

  • Updated Prisma and related packages to release candidate 8.0.0-rc.17.
  • Updated the Prisma CLI’s Composer and Compute SDK components to their newer versions.

• Chores

  • Aligned internal package versions and the Prisma Platform core concepts skill metadata with the 8.0.0-rc.17 release candidate.
  • No functional changes are included in this update.

Walkthrough

Package and workspace versions were updated from 8.0.0-rc.16 to 8.0.0-rc.17. The CLI and Prisma package manifests also update composer dependencies from 0.22.0 to 0.23.0 and the compute SDK from 0.42.0 to 0.43.0. The Prisma Platform core concepts skill metadata was updated to 8.0.0-rc.17.

Merge Risk: ⚪ Minimal · up to b1a7d

The release candidate’s manifests and lockfile agree on the selected dependency and peer versions, so no concrete merge-blocking risk remains.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely identifies the primary change: bumping the release to version 8.0.0-rc.17.
Description check	✅ Passed	The description directly explains the 8.0.0-rc.17 release, dependency updates, skipped rc.16 release, verification results, and release behavior.
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

🧪 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]

Open in StackBlitz

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

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

commit: b1a7d29