Follow the products' released versions: @prisma/composer-cli 0.26.0 -> 0.27.0; @prisma/orm-toolchain 8.0.0-rc.14 -> 8.0.0-rc.16; @prisma/composer 0.26.0 -> 0.27.0

[prisma-bot]

Opened automatically by update-product-versions.yml, following the products' release dist-tags (@prisma/composer-cli 0.26.0 -> 0.27.0; @prisma/orm-toolchain 8.0.0-rc.14 -> 8.0.0-rc.16; @prisma/composer 0.26.0 -> 0.27.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.

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 3b008cb1-b737-4be3-8ee3-9daf3c72c66f

📥 Commits

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

⛔ 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

✨ Finishing Touches

🧪 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@335

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

commit: 8be27e1

[wmadden-electric]

Superseded by #336, which moves to Composer 0.28.0 and ORM toolchain rc.16 together with engine 0.6.3. This PR keeps engine 0.6.2 while both products now peer 0.6.3, so conformance would refuse it.