Repository navigation
Releases v0.24.2 - #271
Merged
Merged
Releases v0.24.2#271
Conversation
The upgrading page now runs from 0.13 to 0.24.2. "0.23 to 0.24" gains a "### 0.24.2" subsection whose answer is NONE: no library file differs between v0.24.1 and this release, the statifier floor stays ~> 2.9, and the ~> 0.24.0 pin already takes it. The subsection says the page is now listed in the HexDocs sidebar, under Upgrading. The migration sentence names the 0.24.2 patch beside 0.23.1 and 0.24.1. Documentation only: no changelog fragment (changelog.d/README.md excludes documentation) and no gated path. Refs: sp-l9gl
Bumps @Version to 0.24.2. The README install pin stays `~> 0.24.0`, which already admits a patch (.claude/wurk/release.md, "The README install pin"). A patch, not a minor: nothing under lib/ changed since v0.24.1, so no closed set a host matches grows. The changes since that tag are documentation (the upgrading page and its place in the HexDocs sidebar), decision-record Notes and the acceptance of ADR-0018, a contributor paragraph in CLAUDE.md, and two test files. Documentation takes no changelog.d fragment here, so changelog.d/ holds only its README and there is nothing to promote. The version section is hand-written instead, as the 0.24.1 prep did (decided by the conductor under a standing consent, 2026-10-11): a `## [0.24.2] 2026-10-11` section in the file's heading form, no `-` separator, this machine's local date, a lead naming the release kind, an upgrading line and one Changed bullet per documentation change a reader of the published docs sees. The header's changelog.d/ link moves to v0.24.2. No link-reference block is added. No published section is edited. Gate: full `mix quality` green on this exact tree (format, compile with warnings-as-errors, doc links, deps, docs, credo, 1,432 of 1,432 tests at 96.1% coverage, dialyzer), with the repo gate lock and a machine slot held across the run and this commit; Postgres answered on 5432 from a local server. `mix hex.build` built statifier_persistence 0.24.2. No tag, no publish. Refs: sp-l9gl
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
1 participant
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.
Release prep for statifier_persistence 0.24.2, a docs patch. Bead: sp-l9gl.
What this does
docs/upgrading.md(its own commit, ahead of the release commit): the title and the lead paragraph move to 0.24.2; "0.23 to 0.24" gains a "### 0.24.2" subsection answering NONE (no library code differs from 0.24.1, thestatifierfloor stays~> 2.9, the"~> 0.24.0"pin already takes it, and the page is now listed in the HexDocs sidebar under Upgrading); the migration sentence names the 0.24.2 patch beside 0.23.1 and 0.24.1.mix.exs:@version "0.24.2".CHANGELOG.md: a hand-written## [0.24.2] 2026-10-11section (lead, an upgrading line, Changed bullets for the upgrading page reaching the HexDocs sidebar and its 0.24.1 and 0.24.2 subsections), and the header'schangelog.d/link moved fromblob/v0.24.1toblob/v0.24.2. No link-reference block; no released section edited.Why a patch, and why a hand-written section
git diff v0.24.1..origin/main --stat -- libis empty, so no closed set or public union a host matches grows. The changes since v0.24.1 are documentation (the upgrading page and its HexDocs sidebar entry), decision-record Notes and ADR-0018's acceptance, a contributor paragraph in CLAUDE.md, and two test files.changelog.d/README.mdexcludes documentation, ADRs and test-only changes from fragments, sochangelog.d/holds only its README and there is nothing to promote; the section is hand-written in the shape of the 0.24.1 prep. The release itself was ruled by the operator, 2026-10-10; the hand-written section and leaving the README pin were decided by the conductor under a standing consent, 2026-10-11.The README install pin stays
~> 0.24.0: a patch leaves the pin (.claude/wurk/release.md, "The README install pin"). CLAUDE.md's "The package is released" line does not move in the prep. The release commit touches onlymix.exsandCHANGELOG.md, inside the release recipe's file table.Verification
mix qualitygreen on the final tree: format, compile with warnings as errors, doc links, deps, docs, credo, 1,432 of 1,432 tests at 96.1% coverage, dialyzer. Postgres answered on 5432 from a local server.mix hex.buildbuilt statifier_persistence 0.24.2.mix docsrenderedupgrading.htmltitled "Upgrading a host from 0.13 to 0.24.2" in the sidebar's Upgrading group, and the changelog page linkschangelog.d/atv0.24.2.No tag and no publish here: after the merge the tag
v0.24.2goes on the merge commit, and the release workflow publishes on the tag push.