fix(dev-base): split core publish into visible steps #590

Merged

coilyco-ops merged 1 commit from issue-589 into main

2026-07-15 12:39:25 +00:00

coilyco-ops commented

2026-07-15 12:34:52 +00:00

Member

Split the publish-core path in dev-base-publish.yml into first-class workflow steps so the Forgejo run page shows the failing subphase directly. The shared composite action stays in place for the sibling tiers.

This stays tightly scoped to the core publish path and keeps the publish logic intact while making director-side triage actionable without raw logs.

What changed: inlined core publish phases as named steps for source, tool bootstrap, host resolution, registry login, landed check, build, verification, and cache probe.
Why: publish-core needs a visible failure point on the run page.
Test and CI: ward exec pre-commit-all passed locally.
closes #589
ward.workflow: pull-request-and-merge

Split the `publish-core` path in `dev-base-publish.yml` into first-class workflow steps so the Forgejo run page shows the failing subphase directly. The shared composite action stays in place for the sibling tiers. This stays tightly scoped to the core publish path and keeps the publish logic intact while making director-side triage actionable without raw logs. - What changed: inlined core publish phases as named steps for source, tool bootstrap, host resolution, registry login, landed check, build, verification, and cache probe. - Why: `publish-core` needs a visible failure point on the run page. - Test and CI: `ward exec pre-commit-all` passed locally. - closes #589 - ward.workflow: pull-request-and-merge

coilyco-ops added 1 commit

2026-07-15 12:34:52 +00:00