fix(ci): block every other release job behind a test gate #1035
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/ward!1035
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-999"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Every other ward CI step now blocks behind the
testjob.A push to
mainused to tag and publish a release even when the test workflow failed:test.ymlandrelease.ymlare independent workflows, and Forgejo Actions has no cross-workflowneeds.release.ymlnow opens with atestgate job running the same vet/test/lint checks as.forgejo/workflows/test.yml(which still runs independently, covering pull requests), and thereleasejobneedsit. Every other job alreadyneeds: releasedirectly or viapublish-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 deaddocs/ward-specs.mdreference) that had landed onmainpast the hooks and blocked any commit here; the detail moved todocs/config-source.md.closes #999
ward.workflow: pull-requests-and-merge
testjob #999testjob #999