Release beat missing: 2026-11-02 #2081
Description
No v* tag was created on 2026-11-02 (Asia/Shanghai), so the daily release beat did not happen and nothing announced it.
- newest tag:
v0.2.19, dated 2026-11-01 - hours since that tag: 24
- last
release.ymlrun: https://github.com/ThinkFlowLab/FlyBot/actions/runs/41255516975 - the routine's own catch-up (first half of A release beat can be missed whole and nobody is told: the 02:00 routine has no catch-up and no alert #1209) runs first: check whether it already re-released today
The metric here is the newest v* tag, not a workflow run: release.yml has no cron, so a missing tag produces no run at all.
Filed by .github/workflows/release-beat.yml; one issue per day.
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).