Repository navigation
chore(release): 0.16.0 - #883
Open
stephrobert wants to merge 1 commit into
Open
stephrobert wants to merge 1 commit into
stephrobert wants to merge 1 commit into
Conversation
Seven merged lots had no release. The CHANGELOG carried one of them. What this release ships, and why each line is in the note rather than only in the history: the release workflow reads that section for the body of the GitHub Release, so an entry missing here is an entry nobody downloading a binary ever sees. - `feint run` owning the lab (#848), which is this release's headline and the one command a stranger types; - `feint checkpoint` and `feint reset" (#853), with a verdict drawn from what a client can observe rather than from the operation's own intention; - the Linux install route in the Quick Start (#843), proved on a clean runner against the published artefacts; - five fixes from an external audit of merged code (#871), including a reset that reported convergence while a firewall rule was missing from the interface; - two gates that could not fail (#829, #559); - the tracker agreeing with the tags (#877), the limits page catching up (#857), and the product's boundary written down (#196, #733). The French changelog carries the same entries. A change written in one file and not the other is a change a reader of one language never learns about, and TestBothChangelogsCarryTheSameUnreleasedEntries refuses it. Seven files name the version by hand -- the examples, the issue template and a demo tape -- and they moved with the heading rather than after somebody noticed. TestEveryExampleNamesTheReleasedVersion turns red the moment the CHANGELOG moves, which is how they were found here rather than by a reader downloading a 404. `mise run release:surface` reports 0 changes a release note must carry. `mise run prepush` green. Assisted-by: Claude Code (claude-opus-5)
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Step 1 of
RELEASING.md, for a release that was seven lots behind: theUnreleasedsection carried one of them.What it ships.
feint runowning the lab (#848) — the one command a stranger types.feint checkpointandfeint reset(#853), whose verdict is drawn from what a client can observe rather than from the operation's own intention. The Linux install route in the Quick Start (#843), proved on a clean runner against the published artefacts. Five fixes from an external audit of merged code (#871), including a reset that reported convergence while a firewall rule was missing from the interface. Two gates that could not fail (#829, #559). And the tracker agreeing with the tags (#877), the limits page catching up (#857) and the product's boundary written down (#196, #733).Every line is in the note rather than only in the history, because the release workflow reads that section for the body of the GitHub Release: an entry missing here is an entry nobody downloading a binary ever sees.
Both changelogs carry the same entries. A change written in one file and not the other is a change a reader of one language never learns about, and
TestBothChangelogsCarryTheSameUnreleasedEntriesrefuses it.Seven files name the version by hand — the examples, an issue template and a demo tape — and they moved with the heading.
TestEveryExampleNamesTheReleasedVersionturns red the moment the CHANGELOG moves, which is how they were found here rather than by a reader downloading a 404. That test exists because on 2026-08-18 the examples were wrong in both directions at once.What this closes once tagged: #848, whose last acceptance bullet asks for a released binary on a clean Linux host. The acceptance replays itself —
released-linux.ymltriggers on thereleaseevent and installs the published binary by following the README's own block.Type of change
Checklist
Always
mise run checkpassesinternal/corestill knows no provider — no Go file is touchedmise run testplanwas run, and what it printed was runWhen a model wrote a substantive part of this
Assisted-by:trailer names the tool and the model versionWhen a route is added or changed
N/A —
mise run release:surfacereports 0 changes a release note must carry: nothing was newly served, nothing stopped being served, and no refusal was withdrawn since v0.15.0.When behaviour a client can observe changes
docs/install.mdnow pin 0.16.0, regenerated withmise run docs:coveragein the same commit, as the procedure requiresdocs/limits.mdunchangedWhen
.github/workflows/is touchedN/A.
When a machine runtime is involved
N/A.
Related issues
Closes #848 once the tag is pushed and the clean-host acceptance has run.
🤖 Generated with Claude Code