instructions/dev: publish-and-ci - Wartezeit zählt ab freiem Runner statt ab Push; offene Läufe eines früheren Pushs zuerst, Runner hält die Push-Reihenfolge nicht ein; 10.1.0-beta.20
CI / verify (push) Successful in 7m58s
CI / pwsh (push) Successful in 2m42s
Release / converters (push) Successful in 27s
Release / release (push) Successful in 38s
Release / wiki-mirror (push) Skipped

Files changed:
- CHANGES.md
- VERSION
- instructions/dev/publish-and-ci.md

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
This commit is contained in:
torbenandClaude Opus 5.5 committed 2026-10-16 12:34:26 +02:00
1 parent a37ca560fb
commit cc990dc89e
3 files changed
+8 -2

No files matched your search

+5
View File
@@ -55,6 +55,11 @@ formality after it - which is why waiting for it belongs to the phase that wrote
- Check again after about 11 minutes, then every 2 minutes.
- **Give up after 25 minutes** - twice the usual time, so a slow day is not mistaken for a
hang - and hand the open runs to the user by id and link, rather than waiting on.
- **Count from when the runner is free, not from the push.** Runs of an earlier push that are
still open when you publish run first, and the runner does not keep push order: it may take
the next push's CI before the earlier push's release run. So list the open runs right after
`publish`; when there are any, the first check and the give-up time start from the moment
the last of them finishes.
- Any shell loop that polls instead must **end on the first non-2xx status or missing field**
and print the raw response. A loop that treats an error as "not finished yet" never ends;
that happened in the #139 close-out.