chore(release): bump to 8.0.0-rc.11 - #239
Merged
Merged
Conversation
Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
|
Warning Review limit reachedNext included review available in 42 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (9)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
commit: |
wmadden
approved these changes
Aug 26, 2026
wmadden-electric
added a commit
that referenced
this pull request
Aug 26, 2026
Main released engine 0.3.0 today carrying the SDK-peer change (#236), with composer-cli 0.15.0 and orm-toolchain 8.0.0-rc.8 peering it and the conformance exceptions emptied (#239). This branch's engine work — the config chain and the defineConfig alias removal — therefore ships as 0.4.0. The conformance transition exceptions return, naming the pins the transition actually has: families peer 0.3.0, shell 0.4.0. 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.
8.0.0-rc.10 → 8.0.0-rc.11. This is the final step of the engine-0.3.0 release chain (see docs/oss/versioning.md and release automation).
What this release ships:
@prisma/management-api-sdkbecomes a peer dependency, so one copy of the SDK's client type serves the engine and the shell, and future SDK bumps no longer force a three-repo release chain.@prisma/orm-toolchain8.0.0-rc.7 → 8.0.0-rc.8 (Bump to version 8.0.0-rc.8: the engine peer moves to @prisma/cli-engine@0.3.0 orm#30137) and@prisma/composer-cli0.14.0 → 0.15.0 (Release 0.15.0: ORM family to 8.0.0-rc.8, engine to 0.3.0 composer#263, which also lifts the ORM family from rc.4 to rc.8 and unblockscreate-prismascaffolds).PUBLISH_CHANNEL=release pnpm check:conformancereports: 5 subjects checked, nothing to report.Local verification: build, typecheck (9/9),
@prisma/clitests (960 passed, 1 skipped),check:grammar, and release-channel conformance all green.Merging this PR publishes
prisma@8.0.0-rc.11and@prisma/cli@8.0.0-rc.11underlatestand creates the matching pre-release GitHub Release.Post-merge follow-up (operator):
npm dist-tag add @prisma/cli-engine@0.3.0 latest— the engine published underdev(its version landed via a routine main push), and the release run treats an already-published engine version as done, so the tag does not move on its own.🤖 Generated with Claude Code