A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I2712
release-check treats a tag whose release run is still going as pending, not as a missing record
Where it stands
devtask.issue- Readiness
- complete completion is recorded and every required evidence token is present
- Status
- DONE
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
1- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
1of1
Moves
plan.transitionWhat it is
- Objective
- Make scripts/ci/release-check tell a tag whose release workflow is still running (or whose record branch is about to be opened by it) from a published release that nobody recorded.
- Why
- 2026-10-14 18:37Z: the structure job of #1146 (I1510) failed release-check with \"v0.26.0 is published and the layer holds no release record for it ... and no release/record-v0.26.0 branch proposes one\" while the release workflow 38613749519 for v0.26.0 was still building; the GitHub release did not exist yet. Every branch judged in that window was red for a reason that was not its own. I2054 stopped a pending tag from freezing the queue once the record branch exists; the window before the branch remained.
- Now
- release-check counts a pushed tag as published and demands a record or a record branch at once.
- Wanted
- A tag whose release run for that tag is queued or in progress, or whose GitHub release does not exist yet, is reported as pending with the run named, not as a finding; a published release with neither record nor record branch after its run concluded stays a finding.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- Between a tag push and its record branch, release-check reports the tag as pending with its run and exits 0
- After the release run concluded with no record and no record branch, it is still a finding
- Validation
bin/majordomus plan validate- Evidence required
tag_in_flight_is_pending_case- Evidence present
tag_in_flight_is_pending_case
Scope
- Touches
scripts/ci/release-checkdocs/RELEASE.mdtest/cases- Not
What the release workflow itself does- Depends on
- Priority
- p1
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-10-14
- Updated
- 2026-10-14T22:02:55Z
- Started
- 2026-10-14T22:01:24Z
- Verified
- unknown: the record declares no `verified_at`
- Completed
- 2026-10-14T22:02:55Z
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.