fix(release): guard bundle jobs against transitive skip - #14
Conversation
Co-authored-by: Medulla <medulla@tinyhumans.ai>
|
Warning Review limit reached
Next review available in: 44 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: CHILL 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 |
Follow-up to #13. The artifact-only re-cut ran
Resolve release targetto success and then skippedModule bundleandCreate GitHub releaseanyway.Cause: GitHub propagates a skip transitively.
publishis skipped on theexisting_tagpath, and althoughnative-bundlesdepends only onrelease-target— which succeeded — the skipped ancestor still skips it. A job needs its ownalways()to opt out of that, whichrelease-targethad and its dependents did not.Both downstream jobs now carry
always()plus an explicit result check, so the guard is the success condition rather than the absence of a skip.