Skip to content

Send the release tag with the landing dispatch#71

Merged
nmbrthirteen merged 1 commit into
mainfrom
ci/dispatch-release-tag
Jul 8, 2026
Merged

Send the release tag with the landing dispatch#71
nmbrthirteen merged 1 commit into
mainfrom
ci/dispatch-release-tag

Conversation

@nmbrthirteen

Copy link
Copy Markdown
Owner

The release dispatch to podcli-landing carried no client_payload, so the receiving workflow could not name the release it was rebuilding for. Now it sends the tag, and the landing log line reads Vercel 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.

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.
@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@nmbrthirteen, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 43 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 01096843-02bc-4c1a-a749-91bbe0b934c8

📥 Commits

Reviewing files that changed from the base of the PR and between ba3b825 and a284c2d.

📒 Files selected for processing (1)
  • .github/workflows/release.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/dispatch-release-tag

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@nmbrthirteen nmbrthirteen merged commit a7bc212 into main Jul 8, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant