Send the release tag with the landing dispatch#71
Conversation
The dispatch carried no payload, so the landing workflow could not name the release it was rebuilding for. Passing the tag makes its log line say which version triggered the build.
|
Warning Review limit reached
Next review available in: 43 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
The
releasedispatch to podcli-landing carried noclient_payload, so the receiving workflow could not name the release it was rebuilding for. Now it sends the tag, and the landing log line readsVercel responded 201 for podcli v2.4.3.Pairs with nmbrthirteen/podcli-landing#7, which is where the actual rebuild happens. Worth knowing why that PR exists: this dispatch has fired since v2.4.1 and never caused a rebuild, because the receiving job only commits when the docs submodule moves, and a podcli release never moves it. The step name here promised something the other repo never delivered.