fix(dev-base): bound ward source clone in core publish #582

Merged

coilyco-ops merged 2 commits from issue-581 into main

2026-07-15 10:27:39 +00:00

coilyco-ops commented

2026-07-15 10:16:45 +00:00

Member

This tightens the hidden dev-base-ward-builder bootstrap in docker/dev-base/core/Dockerfile so the core publish path no longer sits on an opaque source fetch. The ward source clone now has a bounded retry and explicit attempt markers, and the module download loop logs each attempt before waiting.

Why: the last failed publish-core run stalled without enough release-visible context to tell whether the wall was the ward source fetch or the Go module step.
Tests: ward pre-commit-all

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

This tightens the hidden `dev-base-ward-builder` bootstrap in `docker/dev-base/core/Dockerfile` so the core publish path no longer sits on an opaque source fetch. The ward source clone now has a bounded retry and explicit attempt markers, and the module download loop logs each attempt before waiting. - Why: the last failed publish-core run stalled without enough release-visible context to tell whether the wall was the ward source fetch or the Go module step. - Tests: `ward pre-commit-all` closes #581 ward.workflow: pull-request-and-merge

coilyco-ops added 1 commit

2026-07-15 10:16:45 +00:00

fix(dev-base): bound ward source clone in core publish

ci / ward-doctor (pull_request) Failing after 7s

Details

ci / gate (pull_request) Successful in 54s

Details

12c59365d0

coilyco-ops added 1 commit

2026-07-15 10:20:47 +00:00

fix(ci): sync ward defaults before source build

ci / ward-doctor (pull_request) Successful in 15s