fix(ci): block every other release job behind a test gate #1035

Merged
coilyco-ops merged 5 commits from issue-999 into main 2026-07-11 01:30:09 +00:00
Member

Every other ward CI step now blocks behind the test job.

A push to main used to tag and publish a release even when the test workflow failed: test.yml and release.yml are independent workflows, and Forgejo Actions has no cross-workflow needs. release.yml now opens with a test gate job running the same vet/test/lint checks as .forgejo/workflows/test.yml (which still runs independently, covering pull requests), and the release job needs it. Every other job already needs: release directly or via publish-binaries, so the whole pipeline - tag, binaries, kdl tiers, tap, scoop - blocks transitively.

Also repairs pre-existing comment-discipline violations in cmd/ward/configsource.go (a 5-line comment block plus a dead docs/ward-specs.md reference) that had landed on main past the hooks and blocked any commit here; the detail moved to docs/config-source.md.

closes #999

ward.workflow: pull-requests-and-merge

Every other ward CI step now blocks behind the `test` job. A push to `main` used to tag and publish a release even when the test workflow failed: `test.yml` and `release.yml` are independent workflows, and Forgejo Actions has no cross-workflow `needs`. `release.yml` now opens with a `test` gate job running the same vet/test/lint checks as `.forgejo/workflows/test.yml` (which still runs independently, covering pull requests), and the `release` job `needs` it. Every other job already `needs: release` directly or via `publish-binaries`, so the whole pipeline - tag, binaries, kdl tiers, tap, scoop - blocks transitively. Also repairs pre-existing comment-discipline violations in `cmd/ward/configsource.go` (a 5-line comment block plus a dead `docs/ward-specs.md` reference) that had landed on `main` past the hooks and blocked any commit here; the detail moved to `docs/config-source.md`. closes #999 ward.workflow: pull-requests-and-merge
cmd/ward/configsource.go carried a 5-line comment block and a dead
docs/ward-specs.md reference (that page lives in aos, not ward), landed
on main past the hooks. Shrink the block to the load-bearing constraint
and move the tier-guardfile detail into docs/config-source.md.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A push to main used to tag and publish a release even when the test
workflow failed, because test.yml and release.yml are independent
workflows and Forgejo Actions has no cross-workflow needs. release.yml
now opens with a test job running the same vet/test/lint checks as
.forgejo/workflows/test.yml, and the release job needs it - every other
job already needs release, so the whole pipeline blocks transitively.

closes #999

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Merge remote-tracking branch 'origin/main' into issue-999
All checks were successful
test / test (pull_request) Successful in 26s
6f2c71f5fa
Merge branch 'main' into issue-999
All checks were successful
test / test (pull_request) Successful in 36s
6376050f3a
# Conflicts:
#	cmd/ward/configsource.go
Merge branch 'main' into issue-999
All checks were successful
test / test (pull_request) Successful in 29s
51c48cc9a0
Sign in to join this conversation.
No description provided.