fix(dev-base): make publish resumable and retryable #567

Closed
coilyco-ops wants to merge 1 commit from issue-565 into main
Member

Resumable dev-base publishing landed for tier reruns and transient registry failures. The publish helper now skips tiers that already match their checkpoint, retries the registry-sensitive operations, and keeps the tier DAG intact for resumptions.

  • Added per-tier checkpoint checks and bounded retries in the publish helper and composite action.
  • Made promote/release workflows DAG-aware for tier-scoped reruns and non-blocking Telegram alerts.
  • Documented the checkpoint contract and added tests for the helper and workflow shape.

Tests: ward exec test -- tests/test_dev_base_image.py tests/test_dev_base_publish_workflows.py tests/test_telegram_alert_action.py tests/test_release_actions.py and ward exec pre-commit-all.

closes #565
ward.workflow: pull-request-and-merge

Resumable dev-base publishing landed for tier reruns and transient registry failures. The publish helper now skips tiers that already match their checkpoint, retries the registry-sensitive operations, and keeps the tier DAG intact for resumptions. - Added per-tier checkpoint checks and bounded retries in the publish helper and composite action. - Made promote/release workflows DAG-aware for tier-scoped reruns and non-blocking Telegram alerts. - Documented the checkpoint contract and added tests for the helper and workflow shape. Tests: `ward exec test -- tests/test_dev_base_image.py tests/test_dev_base_publish_workflows.py tests/test_telegram_alert_action.py tests/test_release_actions.py` and `ward exec pre-commit-all`. closes #565 ward.workflow: pull-request-and-merge
fix(dev-base): make publish resumable and retryable (closes #565)
All checks were successful
ci / ward-doctor (pull_request) Successful in 15s
ci / gate (pull_request) Successful in 53s
adb7b02b41
Author
Member

WARDED_WORKFLOW: blocked 🛑

details

workflow: pull-request-and-merge; review summary: skipped (in-container review gate intentionally skipped because temporary ward default pending brokered QA)
blocker: Forgejo merge stayed on 405 after repeated retries while the PR stayed green
felt: the implementation landed cleanly, the merge surface did not
confidence: medium
surprises: the only failure left was the Forgejo merge endpoint
follow-ups: retry the merge from a surface with queue access or after the Forgejo merge queue clears

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped (in-container review gate intentionally skipped because temporary ward default pending brokered QA) blocker: Forgejo merge stayed on 405 after repeated retries while the PR stayed green felt: the implementation landed cleanly, the merge surface did not confidence: medium surprises: the only failure left was the Forgejo merge endpoint follow-ups: retry the merge from a surface with queue access or after the Forgejo merge queue clears </details>
coilyco-ops closed this pull request 2026-07-15 09:47:02 +00:00
All checks were successful
ci / ward-doctor (pull_request) Successful in 15s
ci / gate (pull_request) Successful in 53s

Pull request closed

Sign in to join this conversation.
No description provided.