Repository navigation
Follow the products' released versions: @prisma/orm-toolchain 8.0.0-rc.16 -> 8.0.0-rc.17 - #340
Conversation
…c.16 -> 8.0.0-rc.17 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>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
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
WalkthroughThe CLI and Prisma package manifests update their Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to The CLI and Prisma packages select the same toolchain release, and the supplied lockfile records matching resolutions. No actionable issue is identified; the change appears ready to merge subject to normal checks. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 2 systems. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
commit: |
`8.0.0-rc.21` → `8.0.0-rc.22` This release ships the CLI on the latest Composer and ORM releases: | Package | Before | After | | --- | --- | --- | | `@prisma/composer-cli`, `@prisma/composer` | `0.28.0` | `0.29.1` | | `@prisma/orm-toolchain` | `8.0.0-rc.17` (from #340) | `8.0.0-rc.17` | | `@prisma/cli-engine` (packed) | `0.7.0` | `0.7.0` | Composer 0.29.1 and ORM rc.17 both peer engine `0.7.0`, the engine `main` packs, so the conformance check passes with no exceptions. ## Why 0.29.1 and not 0.29.0 Composer 0.29.0 moved to `alchemy@2.0.0-beta.81`. That `alchemy` declares an optional peer dependency on exactly `prisma@8.0.0-rc.15`. This CLI publishes as `prisma`, so npm nested a full `prisma@8.0.0-rc.15` (with engine `0.4.0`) inside Composer, and conformance failed. [prisma/composer#349](prisma/composer#349) (0.29.1) puts `alchemy` back on `2.0.0-beta.78`. The upstream fix is [alchemy-run/alchemy#2154](alchemy-run/alchemy#2154). ## Checks run locally - `pnpm build`, `pnpm typecheck`, `pnpm lint`: pass. - `pnpm --filter @prisma/cli test`: 1027 passed, 1 skipped. - `pnpm check:conformance`: 5 subjects checked, nothing to report. ## Merging ships the release Merging this PR changes the root version on `main`. The `Publish to npm` workflow then publishes `@prisma/cli-engine` and `@prisma/cli` under `latest` and creates a pre-release GitHub Release with generated notes. See [`docs/oss/versioning.md`](docs/oss/versioning.md). Agent: tagore-84 🤖 Generated with [Claude Code](https://claude.com/claude-code) Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Opened automatically by update-product-versions.yml, following the products' release dist-tags (@prisma/orm-toolchain 8.0.0-rc.16 -> 8.0.0-rc.17). Merging publishes a
devversion of the CLI; the conformance checks on this pull request are what stand between a product release and that dev build.