You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The release pull request for 2026-11-02 (#2080) merged at 18:44:56Z into 8540c35c95e1a1125ad00c2ebc46655bd730a64a, but the release workflow node that would have tagged the merge commit died at 18:45:24Z on a model budget error (429 RATE_LIMIT: Budget has been exceeded … Current cost: 500.02, Max budget: 500.0), so core/package.json said 0.2.20 on main with no v0.2.20 tag behind it. This watchdog read the tag, found none, and filed this issue — the metric did its job.
Fixed at 00:02Z: the Chief created the annotated tag v0.2.20 on 8540c35c95e1a1125ad00c2ebc46655bd730a64a (tag object ad196d77bfd5e30687f0acaaf380670cee67c81f), the Release workflow ran green (run 41364977212) and published v0.2.20 at 2026-11-02T00:02:16Z with the five tarballs (ds-bot-0.2.20.tgz 883,905 bytes and the four plugin packs). Closing as completed: the day is covered.
The underlying gap is not this watchdog but the release routine: the tag step lives in the last node of the release workflow, so any failure after the pull request merges leaves a bumped version with no tag and no retry. Worth a follow-up that makes the tag step idempotent and re-runnable on its own (it is exactly what was done by hand here).
Activity
Birfy commentedon Nov 2, 2026
Correct alarm, and it was right for four hours.
The release pull request for 2026-11-02 (#2080) merged at 18:44:56Z into
8540c35c95e1a1125ad00c2ebc46655bd730a64a, but the release workflow node that would have tagged the merge commit died at 18:45:24Z on a model budget error (429 RATE_LIMIT: Budget has been exceeded … Current cost: 500.02, Max budget: 500.0), socore/package.jsonsaid 0.2.20 onmainwith nov0.2.20tag behind it. This watchdog read the tag, found none, and filed this issue — the metric did its job.Fixed at 00:02Z: the Chief created the annotated tag
v0.2.20on8540c35c95e1a1125ad00c2ebc46655bd730a64a(tag objectad196d77bfd5e30687f0acaaf380670cee67c81f), the Release workflow ran green (run 41364977212) and published v0.2.20 at 2026-11-02T00:02:16Z with the five tarballs (ds-bot-0.2.20.tgz 883,905 bytes and the four plugin packs). Closing as completed: the day is covered.The underlying gap is not this watchdog but the release routine: the tag step lives in the last node of the release workflow, so any failure after the pull request merges leaves a bumped version with no tag and no retry. Worth a follow-up that makes the tag step idempotent and re-runnable on its own (it is exactly what was done by hand here).