Skip to content

docs: retract an unfounded claim v2.4.1's notes made about v2.3.9 #431

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

Merged
doublegate merged 1 commit into from
Aug 20, 2026
Merged

docs: retract an unfounded claim v2.4.1's notes made about v2.3.9 #431

Show file tree
Hide file tree
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
6 changes: 4 additions & 2 deletions .github/release-notes/v2.4.1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,11 +63,13 @@ v2.3.9 cleared stale debug telemetry on a ROM change and recorded that it could

It is **not** part of the save state, and the reasoning is now on the field with a test pinning it. Serializing it would break two things silently: loading the same slot twice would restore the same generation twice, so a consumer would miss the second load; and a value from another session means nothing in this one. Because it lives outside the snapshot, `snapshot_schema_audit` cannot see it — the property that makes the design correct also means nothing mechanical would notice the reasoning being invalidated.

## Release anchors, and a claim v2.3.9 made that v2.3.9 did not ship
## The release anchors, and the gate that arrived after them

`release_anchor_audit.rs` pins **15 anchors across 10 documents** against `[workspace.package] version`, fails closed when a marker matches nothing, and asserts the CHANGELOG header parses the way `release-auto.yml` parses it.

It is described in **v2.3.9's release notes and is not in the v2.3.9 tag.** It merged in #427, after the tag was cut. The audit exists because eight documents had reached six different answers about the current version; that a release note could describe work the release does not contain is the same failure one level up, and it ships here.
It is not in the v2.3.9 tag. v2.3.9 found eight documents holding six different answers about the current version and corrected them **by hand** — which is what its notes describe, and all they claim. The standing gate merged afterwards in #427 and ships here. A hand correction fixes the instance and leaves the mechanism intact; this release is the mechanism.

**Correcting these notes as first published:** they said v2.3.9's release body *described* the audit and that the tag therefore did not contain what the notes claimed. That is wrong. The v2.3.9 body describes the manual re-synchronisation and nothing more, and that work is in its tag. The claim is retracted here rather than quietly edited out, because it was an accusation against a shipped release and it was unfounded.

## Under the surface

Expand Down
Loading
Loading