stack-close: wait for CI via the authenticated Gitea connection, with timings and a give-up point
Files changed: - CHANGES.md - VERSION - instructions/dev/stack-close/SKILL.md
This commit is contained in:
1 parent
6d53c55d0d
commit
919e733e21
3 files changed
+30
-2
No files matched your search
+12
-1
@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
|
||||
|
||||
---
|
||||
|
||||
## 7.1.0-beta.2 - 2026-09-25 - version bump no longer points at version release in its output
|
||||
## 7.1.0-beta.3 - 2026-09-25 - stack-close: wait for CI through the authenticated Gitea connection, with timings and a give-up point
|
||||
|
||||
**Author:** Torben Nehmer
|
||||
|
||||
@@ -69,6 +69,7 @@ concern - readable here, never shipped as something to parse.
|
||||
|
||||
**Low impact**
|
||||
- version bump no longer points at version release in its output
|
||||
- stack-close: wait for CI through the authenticated Gitea connection, with timings and a give-up point
|
||||
<!-- /wikitool:bumps -->
|
||||
|
||||
### CalDAV task-tracker provider (Nextcloud Tasks, iOS Reminders); review reports unknown-value findings instead of skipping them
|
||||
@@ -100,6 +101,16 @@ an agent read that as its own next step and fixed a candidate into a release una
|
||||
is gone: whether a candidate ships is the user's decision, as `DEVELOPMENT.md` already says for
|
||||
humans, and `instructions/dev/version-parts.md` step 7 now says so for agents.
|
||||
|
||||
### stack-close: wait for CI through the authenticated Gitea connection, with timings and a give-up point
|
||||
|
||||
Sessions kept improvising how to wait for CI before closing an issue, and one of those
|
||||
improvisations - an anonymous `curl` loop against the Actions API, which answers `401` even for
|
||||
this public repo - treated every error as "not finished yet" and never ended. `stack-close` step 2
|
||||
now names the one way to do it: read the runs through the authenticated Gitea connection, first
|
||||
check after about 4 minutes (5 with a release job), then once a minute, and hand back to the user
|
||||
after 15. Any shell loop that polls instead must end on the first unexpected response. Dev-only;
|
||||
nothing here ships to an instance.
|
||||
|
||||
---
|
||||
|
||||
## 7.0.0 - 2026-09-22 - Task-Tracker-Anbindung: Vorhaben als Seitenart, Verpflichtungsschicht, Weekly Review als Read-Time-Join
|
||||
|
||||
Reference in new issue
Block a user