Skip to content

Hold the 0.3.1 tag and publish until the CI flake is fixed #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
HackTuah wants to merge 1 commit into from
Closed

Hold the 0.3.1 tag and publish until the CI flake is fixed #17

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions HANDOFF.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,6 +116,19 @@ Every one of these is in `slices/003-release-0-3-1/FINDINGS.md` with its measure

## To release 0.3.1

> **HELD. Do not tag and do not publish.** Owner instruction, 2026-09-08: the release waits until
> the CI test flake (SCR-289, slice 006) is fixed and merged.
>
> The reason is not the defect in `0.3.1` — there isn't one. It is that a test in this repository
> answers differently on two runs of the same commit, **measured**: PR #15's `pull_request` run
> passed and its `push` run failed on a commit containing no code. While that is true, *"gate
> green, every step line reading pass"* is a sample rather than a measurement, and that sentence
> is the whole evidence that `0.3.1` is fit to ship. Tagging now would publish on a green that
> nobody can currently distinguish from a lucky one.
>
> Lift this line when slice 006 is on `main`, then re-run the gate on the release commit and read
> the step lines before step 2 below.

1. Merge the PR to `main` (the ruleset requires two green checks).
2. Date the `[0.3.1]` heading.
3. `mix hex.publish`, then tag `v0.3.1` signed — or tag first and publish immediately after.
Expand Down
Loading