Fix promote failure after non-empty release retrigger #561

New issue

Closed

opened 2026-07-15 06:41:09 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-15 06:41:09 +00:00

Member

agentic-os release is still blocked after the promote-only release-flow work and a non-empty retrigger PR.\n\nCurrent state at 2026-07-15T06:40Z:\n\n* main: 802b77ddc7, docs: note retrigger PR diff requirement (#560)\n* release: 24980330c2, old failed release head\n* exact-head main runs for 802b77dd:\n * ci.yml 1371 success\n * mirror-to-github.yml 1372 success\n * promote.yml 1373 failure, stopped 2026-07-15T06:40:28Z\n* release still only has old release.yml 1277 failure for 24980330.\n\nPrevious attempts:\n\n* issue 553 tracked the cancelled and then failed promote.\n* issue 556 proved empty-diff retrigger PRs hit Forgejo merge 500.\n* issue 559 created a non-empty retrigger PR 560, which merged successfully.\n\nPlease diagnose the current promote.yml 1373 failure, repair the workflow or repo state, and leave main and release green under the promote-only contract.

agentic-os release is still blocked after the promote-only release-flow work and a non-empty retrigger PR.\n\nCurrent state at 2026-07-15T06:40Z:\n\n* main: 802b77ddc7735a44899c28dcc6860b3821aeef88, docs: note retrigger PR diff requirement (#560)\n* release: 24980330c233d1338be428a16a0a2750f24a3749, old failed release head\n* exact-head main runs for 802b77dd:\n * ci.yml 1371 success\n * mirror-to-github.yml 1372 success\n * promote.yml 1373 failure, stopped 2026-07-15T06:40:28Z\n* release still only has old release.yml 1277 failure for 24980330.\n\nPrevious attempts:\n\n* issue 553 tracked the cancelled and then failed promote.\n* issue 556 proved empty-diff retrigger PRs hit Forgejo merge 500.\n* issue 559 created a non-empty retrigger PR 560, which merged successfully.\n\nPlease diagnose the current promote.yml 1373 failure, repair the workflow or repo state, and leave main and release green under the promote-only contract.

coilyco-ops commented

2026-07-15 06:41:43 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-agentic-os-561 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-15T06:41:42Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/agentic-os#561 · branch issue-561 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-561 · ward v0.697.0 · dispatched 2026-07-15T06:41:27Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.697.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-agentic-os-561` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T06:41:42Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/agentic-os#561` · branch `issue-561` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-561` · ward `v0.697.0` · dispatched `2026-07-15T06:41:27Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.697.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue

2026-07-15 06:43:43 +00:00

Promote failed after non-empty release retrigger PR 560 #562

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-15 06:54:44 +00:00

fix(release): retry uv bootstrap in dev-base publish #563

coilyco-ops closed this issue

2026-07-15 07:06:36 +00:00

coilyco-ops commented

2026-07-15 07:35:06 +00:00

Author

Member

WARDED_WORKFLOW: #563

details

workflow: pull-request-and-merge; review summary: skipped because the temporary ward default pending brokered QA made the in-container review gate intentionally skipped.

The fix felt surgical. The uv bootstrap retry was added in the publish action and the Dockerfile, and the transient connection reset no longer blocks promote.

Confidence: high.
Surprise: the merge triggered a fresh release chain, so the newer run had to be watched instead of the cancelled parent.

Follow-ups: none.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/563 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped because the temporary ward default pending brokered QA made the in-container review gate intentionally skipped. The fix felt surgical. The uv bootstrap retry was added in the publish action and the Dockerfile, and the transient connection reset no longer blocks promote. Confidence: high. Surprise: the merge triggered a fresh release chain, so the newer run had to be watched instead of the cancelled parent. Follow-ups: none. </details>