Repository navigation
0.1.8 stable gate: Promote the accepted RC lineage #320
Description
This was generated by AI during triage.
Parent
Decision purpose
Promote stable 0.1.8 only from an accepted RC lineage. This is a human go/no-go gate plus release publication, not a place to add product scope.
Required input
- Accepted RC promotion record and published prerelease: 0.1.8 RC1: Aggregate six fixed regression batches and publish promotion evidence #257.
Acceptance criteria
- 0.1.8 RC1: Aggregate six fixed regression batches and publish promotion evidence #257 is closed with one accepted exact-candidate RC record and all four fixed route batches.
- The maintainer has completed a bounded Windows smoke covering install/upgrade, Gateway connect/disconnect, Official continuation, both Responses benchmark models, usable Chat, and restart/readback.
- No open P0 or P1 regression is accepted against the 0.1.8 milestone.
- The stable promotion diff contains only reviewed release metadata/version/channel changes. Any product-code change requires a new RC and rerun of affected qualification batches.
- dev and main both pass the required CI / gate on the exact promoted lineage.
- Normal installer and signature, debug installer and signature, Portable ZIP, stable updater metadata, checksums, release notes, and provenance are present and mutually consistent.
- The stable tag points to the published main commit, 0.1.8 becomes GitHub latest stable, and prerelease-only update behavior remains correct.
- The 0.1.8 milestone and Spec: CodexHub 0.1.8 staged compatibility and release roadmap #248 are closed only after release readback succeeds.
Out of scope
- Capability expansion, deferred provider/protocol work, and cleanup of historical branches/worktrees.
- Treating a changed RC candidate as already qualified.
Activity
NOirBRight commentedon Aug 1, 2026
Human Gate Brief
Category: enhancement
Summary: Make the final go/no-go decision and publish stable 0.1.8 from the accepted RC lineage.
Why this is ready for human:
The release mechanics can be delegated, but accepting the RC evidence, judging the bounded Windows smoke, and authorizing GitHub latest-stable/updater promotion are maintainer decisions with external release impact.
Current behavior:
Stable v0.1.7 remains latest. 0.1.8 prereleases are manual opt-in and do not update stable users.
Desired behavior:
After #257 is accepted, the maintainer authorizes a release-only promotion. Any product-code change invalidates the accepted RC and requires requalification.
Acceptance criteria:
Out of scope: