Repository navigation
Releases v0.5.1 - #46
Merged
Merged
Conversation
- `mix.exs` moves `@version` from 0.5.0 to 0.5.1. A PATCH: the changes since 0.5.0 are documentation, docs configuration and tests, and no module, function or shipped schema changes. - `CHANGELOG.md` gains a `## [0.5.1] 2026-10-05` section - the local date - written by hand, since documentation takes no changelog.d fragment here and there was none to promote (ruled by the operator, 2026-10-05). It names the explanation page added, the README rewritten as an introduction, and the hexdocs sidebar grouped by kind of page. - `README.md`'s install pin stays `~> 0.5.0`: a patch keeps the minor, and the pin is written in the `.0` form. No tag and no publish here: the tag follows the merge, and the release workflow publishes on the tag push. Refs: sd-4o6
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_datamodel 0.5.1, a documentation release.
What changes
mix.exs:@versionmoves from 0.5.0 to 0.5.1.CHANGELOG.md: a hand-written## [0.5.1] 2026-10-05section, in the file's existing heading form and dated with the local date. Documentation takes no changelog.d fragment in this repository, so there was no fragment to promote and the section is written by hand (ruled by the operator, 2026-10-05). It names the explanation page added ("Why the family shares one type registry"), the README rewritten as an introduction with a documentation map, and the hexdocs sidebar grouped by kind of page with the decision records no longer published as pages.README.md: unchanged. The install pin is~> 0.5.0, which a patch keeps.No other file changes;
.claude/wurk/release.mdnames no second version carrier.Why a patch
Every change since v0.5.0 is documentation, docs configuration, decision records, CI, agent instructions or tests:
git diff v0.5.0..origin/main -- lib/ priv/is empty, so no closed set or public union grows.Gate and review
The full
mix qualityran green on the exact tree this commit carries, with the repo gate lock and a machine slot held across the run and the commit. Review is the in-turn review a release prep takes: each changelog sentence was checked against the merged commits and the README on main.No tag and no publish in this request: once it is merged, the tag
v0.5.1goes on the merged commit and the release workflow publishes on the tag push.Refs: sd-4o6