chore: Stabilize package release sync after native CLI publishing - #1252
Conversation
Wait for CLI release assets before release-please package sync gives up, and dispatch release-please again after native CLI publish completes so package PR creation recovers from push-time workflow races.
Reuse a matching package release if another release automation run creates it after the initial missing-release check. This keeps the new release-please wait path from failing when the native CLI publish workflow reaches the same sync step at the same time.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAdds dispatch of ChangesNative CLI Publish Workflow Dispatch
Package Release Sync Robustness
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
There was a problem hiding this comment.
1 issue found across 4 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
Avoid hammering GitHub release polling when the configured wait interval is non-positive by sleeping for the clamped one-second retry delay.
Summary
User Impact
Changes
Verification