docs(ci): date the cancellation observation to 1.26.0, not the current version

The concurrency note said "this Gitea (1.26.0)" while `GET /version` now returns 1.27.2 — the instance was upgraded on 2026-08-25/26 (daniel/gitdan's runbook, gitdan#46). Swapping the number would have asserted the cancellation was observed on 1.27.2, which nobody has checked: the runs it cites were seen before the upgrade. The comment now dates the observation to 1.26.0, names the current version, and says persistence is unverified — which is why every commit gets its own group rather than trusting `cancel-in-progress`. That reasoning is unchanged; only the implied currency was wrong. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LjbhSqQf3pwnPA6MVaWcWL
2026-09-02 12:49:56 -05:00
parent b791896e03
commit 5b6acd7b3b
1 changed files with 5 additions and 4 deletions
@@ -21,10 +21,11 @@ on:
 # somebody's build, so drop it.
 #
 # `push` groups on `github.sha` rather than `github.ref`: a constant per-branch
-# group is what let this Gitea (1.26.0) cancel two of daniel/gitdan's merge
-# runs outright while `cancel-in-progress` was gated away from `push` entirely
-# — see the long note in that repo's ci.yaml for the evidence. Giving every
-# commit its own group leaves that behaviour nothing to act on.
+# group is what let this Gitea cancel two of daniel/gitdan's merge runs
+# outright while `cancel-in-progress` was gated away from `push` entirely —
+# see the long note in that repo's ci.yaml. Observed on 1.26.0; the instance
+# is 1.27.2 now and whether it persists is unverified, which is why every
+# commit gets its own group instead of trusting the flag.
 concurrency:
  group: ${{ github.workflow }}-${{ github.event_name == 'pull_request' && github.ref || github.sha }}
  cancel-in-progress: true