Brief for the S5 cutover: retire prisma/prisma's own shell - #167
Brief for the S5 cutover: retire prisma/prisma's own shell#167wmadden-electric wants to merge 1 commit into
Conversation
…'s own shell The ports are merged but prisma-next still runs the commander shell, with the clipanion migration CLI beside it and two open PRs (#29984, #29985 in prisma/prisma) conflicting ahead of the cutover. The brief hands an agent the mandate (land the two PRs, rewire the bin, delete the old shells, keep the orm-toolchain publish surface), the reading order with absolute paths, the warning that no s5-orm.md contract exists anywhere, and the standing process rules. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
|
Warning Review limit reached
Next review available in: 47 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
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: |
Records only — no code. Follows the S3 close-out precedent (#157). ## What this records The S7 contract's seven acceptance items verified against source, merged PRs (#164, #166), two dry-run dispatches, and the registry: `@prisma/cli@8.0.0-rc.1` and `@prisma/cli-engine@8.0.0-rc.1` are live under `next`, `latest` untouched — the project DoD's artifact exists, published by the operator's own action. The Close-out section in `specs/s7-release.md` records the evidence per acceptance item, the two incidents from the first real publish (npm's trusted publisher still naming the deleted `publish-cli.yml`; the immutable Release freezing assetless before its upload) with their dispositions, and the one deliberately amended item: "Release with tarballs attached" holds from #166 onward, not for `v8.0.0-rc.1` itself. `plan.md` marks the slice closed. `deferred.md` gains the offered-but-undecided publish-script extraction. ## Out of scope here The S5 cutover (brief in #167, dispatched elsewhere), S2d and S6 (both dispatched elsewhere), S9. 🤖 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 Fable 5 <noreply@anthropic.com>
2 participants
One document:
.drive/projects/prisma-cli-v8/assets/briefs/s5-cutover-handover.md.The S5 ports are merged and the unified CLI ships the ORM family, but prisma/prisma's own
prisma-nextbin still runs the retired commander shell with the clipanion migration CLI beside it, and two port PRs (prisma/prisma #29984, #29985) sit conflicting ahead of the cutover. This brief is what the operator hands to the agent that finishes it: mandate, boundaries (no npm publishes, no engine changes, no pin bumps — all operator-owned), reading order with absolute paths into the drive directory and prisma/prisma's ADRs, the honest warning that no s5-orm.md contract file exists in either repo, and the standing process rules.🤖 Generated with Claude Code