fix(promotion): bind regenerated current view - #395
Conversation
|
Droid encountered an error —— View job Droid is reviewing code and running a security check… |
|
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 selected for processing (1)
Summary by CodeRabbit
WalkthroughThe PR updates plans/shiplog-swarm/promotion-state.toml. It removes a stale transition binding tied to PR ChangesPromotion state manifest update
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Summary
Why
The exact promotion planner rejected swarm/main because PR #394 regenerated current-promotion.md while the ledger still recorded its pre-#394 tree entry. This is the bounded ledger repair required for the exact current promotion target.
Proof
cargo xtask promotion-state --check— passgit diff --check— pass9d38e58a885d214301bb494315882657e5e506de— passd230065609cc6f8d738d56017a48c4c37abb4f9330920560677,Shiplog Rust Small ResultsuccessClaim boundary
This PR makes the promotion ledger truthful for the exact swarm target. It does not merge or publish the source promotion, create a tag, publish crates, or make a GitHub Release public.