molecule-ai/molecule-core
41
0
Fork 2
Code Issues 51 Pull Requests 16 Actions 33 Packages Projects Releases Wiki Activity

fix(ci): status-reaper drops broken concurrency block (Gitea 1.22.6 cancel-cascade)

Browse Source
This commit is contained in:
Molecule AI · core-devops 2026-05-12 00:41:36 +00:00 committed by Molecule AI App-FE
parent ddff3d282a
commit b19c7fcba9
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
.gitea/workflows/status-reaper.yml
View File

@ -67,12 +67,13 @@ on:
permissions:
contents: read
# Single-flight: two reaper ticks racing would POST duplicate
# compensations. Idempotent at the API (Gitea overwrites by context
# on POST /statuses/{sha}) but cleaner to serialise.
concurrency:
group: status-reaper
cancel-in-progress: false
# NOTE: NO `concurrency:` block is intentional.
# Gitea 1.22.6 doesn't honor `cancel-in-progress: false`: queued ticks
# of the same group get cancelled-with-started=0 instead of waiting
# (DB-verified 2026-05-12, runs 16053/16085 of status-reaper.yml).
# The reaper's POST /statuses/{sha} is idempotent — Gitea de-dups by
# context — so concurrent ticks are safe; accept them rather than
# serialise via the broken mechanism.
jobs:
reap: