docs(agents): record that a green release run can still publish nothing - #351
Conversation
chart-releaser pushes one gh-pages commit per chart, and pushes seconds apart get throttled: the Pages build is rejected before it runs (errored, duration 0) while the release workflow stays green and the GitHub Release is created, so charts.api7.ai keeps serving the previous index with no alert anywhere. Hit today releasing gateway 3.10.12 and 3.9.10 together, and on 2026-08-06 before that; both recovered on a plain rebuild of the same commit.
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 49 minutes Limit details: You’ve used the included review currently available. Your 61 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. You’re in a promotional period — use the checkbox below to run this review for free:
On-demand reviews are free for the next 31 days. After that, they cost $0.25 per reviewed file. How can I continue?Run this review now using the option above, or comment You can also wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Comment |
Releasing
gateway3.10.12 (#348) and 3.9.10 (#349) together surfaced a gap inthe release docs: both release runs went green, both GitHub Releases were created,
gh-pagesgot bothindex.yamlcommits — andcharts.api7.aistill served theindex from three days earlier, so neither chart was installable.
The cause is throttling. chart-releaser pushes one
gh-pagescommit per chart, andthe two pushes landed 30s apart; GitHub Pages rejected both builds before running
them (
status: errored,duration: 0). Nothing surfaces that — the workflow, thereleases, and the branch all look correct.
gh api .../pages/buildsshowed the samepattern on 2026-08-06, where a later rebuild of the identical commit succeeded, and
a plain
POST .../pages/buildsfixed it again today (built,duration 42238).Adds a bullet to the release mechanism section: how to spot it, how to fix it, and
which copy of
index.yamlanswers which question.