chore(release): v0.13.0 - #256
Merged
Merged
Conversation
prisma-cli published @prisma/cli-engine@0.2.2 (config evaluation through pnpm symlink layouts in prisma-cli#222, the detectCI export in prisma-cli#224; the registry's 0.2.0 predates both, and 0.2.1 is skipped — no family released against it). Product CLI packages declare the engine as an exact peer, so composer-cli must release against the engine version the prisma bin will ship. All engine declarations move together and check-cli-engine-pin passes. pnpm bump-minor: 0.12.0 -> 0.13.0. Merging publishes the release, which unblocks the prisma-cli PR that pins it. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
wmadden
approved these changes
Aug 24, 2026
commit: |
This was referenced Aug 25, 2026
Merged
birhantprkc
pushed a commit
to birhantprkc/prisma
that referenced
this pull request
Aug 25, 2026
…ne@0.2.2 (prisma#30111) prisma-cli published `@prisma/cli-engine@0.2.2`: config evaluation works through pnpm symlink layouts that are not realpath'd (prisma/prisma-cli#222) and the engine's CI detector is exported (prisma/prisma-cli#224). The registry's 0.2.0 predates both; 0.2.1 is skipped — no family released against it. `@prisma/orm-toolchain` declares the engine as an exact peer, so it must release against the engine version the `prisma` bin will ship. - Every `@prisma/cli-engine` reference moves 0.2.0 → 0.2.2 (manifests, fixtures, examples, the init-journey harness literal). - `pnpm bump-version`: 8.0.0-rc.5 → 8.0.0-rc.6, stamped across the workspace. - Release notes at `docs/releases/v8.0.0-rc.6.md` (`check:release-notes --mode pr` passes) plus the matching `CHANGELOG.md` entry, covering prisma#30096 and prisma#30097 — the two PRs merged since rc.5 — and the engine move. - `check:upgrade-coverage` passes in both modes. Merging publishes the release under `latest`, which unblocks the prisma-cli PR that pins it and removes the engine-transition exceptions. The composer half of the train is prisma/composer#256. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Bundled `prisma-8` skills and upgrade guidance are now included in ORM package tarballs. * Skill setup is now handled through `prisma init`. * **Breaking Changes** * PostgreSQL temporal columns now use explicit `Temporal` or text representations instead of `Date`. * `prisma orm init` no longer installs skills or supports `--skip-skills`. * **Documentation** * Added `8.0.0-rc.6` release notes and upgrade instructions, including contract artifact updates and temporal migration examples. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The engine peer moves to
@prisma/cli-engine@0.2.2.prisma-cli published engine 0.2.2 (config evaluation through pnpm symlink layouts in prisma/prisma-cli#222, the
detectCIexport in prisma/prisma-cli#224; the registry's 0.2.0 predates both, and 0.2.1 is skipped — no family released against it). Product CLI packages declare the engine as an exact peer, so composer-cli must release against the engine version the prisma bin will ship.@prisma/cli-enginereference moves 0.2.0 → 0.2.2;check:cli-engine-pinpasses: exact, agreed across manifests, external in the CLI tarball, absent from the library.pnpm bump-minor: 0.12.0 → 0.13.0.Merging publishes 0.13.0 under
latest, which unblocks the prisma-cli PR that pins it and removes the transition exceptions.🤖 Generated with Claude Code