Repository navigation
Prepares the 9.4.3 release - #243
Merged
Merged
Conversation
`@version` moves to 9.4.3 and `CHANGELOG.md` gains a dated 9.4.3 section. Everything on main since v9.4.2 is documentation, docs configuration, the gate and the release workflow; no file under lib/ or conformance/ changed, so the release is a patch. Documentation takes no `changelog.d/` fragment here and the recipe has no Unreleased section to promote, so the section is written by hand (ruled by the operator, 2026-10-05). It names what a reader of the package sees: the hexdocs sidebar grouped by kind of page, the new explanation page, the README rewritten as an introduction with a documentation map, the README examples moved into the language reference, and the README-linked pages now shipping in the package. The gate, release workflow and dev dependency changes are not user facing and get no bullet, per `changelog.d/README.md`. A patch bump, so the README install pin (`~> 9.4`) does not move. No tag is created here; the tag push publishes through the release workflow. Refs: px-g93q
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
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.
Prepares the 9.4.3 release:
@versioninmix.exsmoves to 9.4.3 andCHANGELOG.mdgains a dated 9.4.3 section. No tag and no publish here; the tag push publishes through the release workflow once this is merged.Why a patch
Every commit on main since v9.4.2 changes documentation, docs configuration, the gate or the release workflow.
git diff v9.4.2..origin/main -- lib/ conformance/is empty, so no public function, option, error reason or language behaviour changed, and nothing a host matches on gained a member.The CHANGELOG section
Documentation takes no
changelog.d/fragment in this repository (changelog.d/README.md, "Do not write a fragment for") and the release recipe has no Unreleased section to promote, so the 9.4.3 section is written by hand (ruled by the operator, 2026-10-05), under the file's existing## [X.Y.Z] - dateheading form and its existing### Documentationsub-heading. It names what a reader of the package sees:The gate stages, the dev dependency move and the release workflow are not user facing and get no bullet, per
changelog.d/README.md.README pin
A patch bump: the install pin
{:predicator, "~> 9.4"}does not move (.claude/wurk/release.md: it moves only on a major or minor bump).Gate
Full
mix qualitygreen on the committed tree: every stage passed, with Doctor, Gettext and Sobelow skipped as not installed (the expected skips).Review
In-turn review of the diff (tier: gate): each CHANGELOG bullet was checked against the commit that made the change and against the file it names on main.