Close slice S7: acceptance verified, records updated - #168
Conversation
The contract's seven acceptance items check off against source, merged PRs (#164, #166), two dry-run dispatches, and the registry itself - the operator's first real publish put both packages on npm under next the same day. The Close-out section records the evidence per item, the two publish incidents (the stale trusted-publisher workflow name; the immutable Release freezing assetless) and their dispositions, and the one deliberately amended item: Release assets hold from #166 onward, not for v8.0.0-rc.1 itself. plan.md marks the slice closed; deferred.md gains the publish-script extraction entry. 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: 30 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 (3)
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: |
2 participants
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.1and@prisma/cli-engine@8.0.0-rc.1are live undernext,latestuntouched — the project DoD's artifact exists, published by the operator's own action.The Close-out section in
specs/s7-release.mdrecords the evidence per acceptance item, the two incidents from the first real publish (npm's trusted publisher still naming the deletedpublish-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 forv8.0.0-rc.1itself.plan.mdmarks the slice closed.deferred.mdgains 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