Make v2 releases product-impact aware #152
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-compose#152
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Parent: #142
Outcome
Keep main validation on every push while publishing binaries and package-manager updates only when shipped product inputs change. Prepare package metadata and the documented manual-major path for v2.0.
Acceptance
Live release dispatch and package publication remain an operator action after the PR stack and independent evaluation gates land.
Implementation is complete and remotely recoverable at
026436din PR #153.Every main push still runs the full validation gate. Only shipped product inputs proceed to tag/build/upload/package publication. Documentation and scored-result-only changes now stop after validation. A tracked
.release-majorholds automatic publication for the breaking v2 stack, while manual dispatch remains the explicit major and exact-tag path. Homebrew and Scoop render successfully at a fixturev2.0.0.Full Ward test, smoke, lint, actionlint, shellcheck, secret scan, release-impact fixtures, and package-render fixtures pass. Live dispatch remains outside this issue and gated on #150 plus the parent release conditions.