Make v2 releases product-impact aware #152

Closed
opened 2026-07-30 12:47:09 +00:00 by coilyco-ops · 1 comment
Member

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

  • Documentation-only and scored-result-only pushes validate but do not create a tag or release.
  • Engine, embedded Core Roster, dependency, release-build, and packaging-input changes publish normally.
  • Manual dispatch remains an explicit retry or major-version path.
  • The classifier has one owning implementation with fixture coverage and no duplicated workflow path inventory.
  • Homebrew and Scoop metadata describe the v2 Core Roster product boundary.
  • Release documentation states the classification and v2.0 operator gate.
  • Full repository validation and release packaging checks pass locally.

Live release dispatch and package publication remain an operator action after the PR stack and independent evaluation gates land.

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 * Documentation-only and scored-result-only pushes validate but do not create a tag or release. * Engine, embedded Core Roster, dependency, release-build, and packaging-input changes publish normally. * Manual dispatch remains an explicit retry or major-version path. * The classifier has one owning implementation with fixture coverage and no duplicated workflow path inventory. * Homebrew and Scoop metadata describe the v2 Core Roster product boundary. * Release documentation states the classification and v2.0 operator gate. * Full repository validation and release packaging checks pass locally. Live release dispatch and package publication remain an operator action after the PR stack and independent evaluation gates land.
Author
Member

Implementation is complete and remotely recoverable at 026436d in 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-major holds 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 fixture v2.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.

Implementation is complete and remotely recoverable at `026436d` in 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-major` holds 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 fixture `v2.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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agent-compose#152
No description provided.