chore(release): bump to 8.0.0-rc.5 - #207
Conversation
commit: |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review. Summary by CodeRabbit
WalkthroughThe release candidate version changes from Merge Risk: ⚪ Minimal · up to This release updates the dependency versions needed for the 8.0.0-rc.5 publish and reports passing conformance, grammar, and script checks; no actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 |
…#209) The check from #200 failed the rc.5 release PR (#207): `pnpm bump-version` rewrites the engine's `@repo/*` devDependencies on every release bump, and devDependencies never ship in the published tarball, so the shipped engine is byte-identical while the check saw "packages/cli-engine changed". A change to the engine's manifest now counts only when something outside `devDependencies` differs. Four new tests pin the comparison. Unblocks #207. 🤖 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>
|
Hold before merging: as of this branch, #210 fixes the pin, teaches |
The release that repairs prisma@next. It depends on @prisma/cli-engine@0.2.0, @prisma/composer-cli@0.8.0 and @prisma/orm-toolchain@8.0.0-rc.3 — every mounted family peering the exact engine this install carries, so one engine resolves (ADR 0004). The conformance exception list returns to empty, and the release-channel conformance run reports nothing. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
|
Good catch — confirmed and repaired. #210 is merged and this branch is rebased on it; the conflict resolution keeps both fixes ( |
21ed5de to
fa8940d
Compare
The release that repairs
prisma@next. rc.4 crashes on import because it was built against engine exports the registry's@prisma/cli-engine@0.1.1does not contain; this release depends on@prisma/cli-engine@0.2.0,@prisma/composer-cli@0.8.0and@prisma/orm-toolchain@8.0.0-rc.3— both families peer the exact engine this install carries, so one engine resolves (ADR 0004).node scripts/update-product-versions.mjs --channel release+pnpm bump-versionPUBLISH_CHANNEL=release pnpm check:conformance: 5 subjects checked, nothing to report.pnpm check:grammarpasses; 80 script tests pass.Merging this is the publish trigger for
8.0.0-rc.5onnext.🤖 Generated with Claude Code