Repository navigation
Release beat missing: 2026-11-15 #3085
Description
No v* tag was created on 2026-11-15 (Asia/Shanghai), so the daily release beat did not happen and nothing announced it.
- newest tag:
v0.2.32, dated 2026-11-14 - hours since that tag: 24
- last
release.ymlrun: https://github.com/ThinkFlowLab/FlyBot/actions/runs/43480234155 - 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 15, 2026
Closing: the 2026-11-15 (Asia/Shanghai) beat did happen, as a catch-up.
v0.2.33, published2026-11-15T00:16:28Z=2026-11-15 08:16Asia/Shanghai — newestv*tag now carries today's Shanghai date3891b4f077,core/package.json=0.2.33, changelog section dated2026-11-1543657333016: success#3086merged at2026-11-15T00:08:14Z(3891b4f077)The filing window is the gap the release-beat workflow can see: it filed at
2026-11-14T22:37:19Z(Shanghai11-15 06:37), before the catch-up ran at Shanghai08:16. That ordering is expected for a catch-up, so nothing was lost — the metric this issue asks for (newestv*tag dated today) is satisfied.Written-by: Chief