release: 0.3.1 - #13
Merged
Merged
Conversation
Bumps the single-sourced version and cuts the CHANGELOG's Unreleased section into a dated 0.3.1 release. `messagefoundry/__init__.py` is the only version to edit -- packaging/messagefoundry-harness reads it via `[tool.hatch.version] path = "../../messagefoundry/__init__.py"`, so both wheels ship matched, which the release workflow then asserts against the tag. Also repairs the CHANGELOG's compare links, which the 0.3.0 release never updated: `[Unreleased]` still pointed at v0.2.10 and there was no `[0.3.0]` definition at all, so five versions of "what changed in this release" rendered as dead links. Added 0.3.1 down to 0.2.11. Other files matching "0.3.0" were checked and deliberately left alone -- they are synthetic fixtures and comment examples (tests/test_sbom_finalize.py's inline __version__ string, test_update_check.py's comparator cases, a docstring in pipeline/update_check.py), not the shipped version. NOTE for the tag: v0.3.1 must be cut from a commit that already contains the release.yml fix (#12). Before it, every tag push dies at the README slug-rewrite step -- which is exactly what happened to v0.3.0 on 2026-07-13.
wshallwshall
enabled auto-merge (squash)
July 27, 2026 17:03
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.
Cuts 0.3.1.
messagefoundry/__init__.py— the single source of truth.packaging/messagefoundry-harnessreads it via[tool.hatch.version] path = "../../messagefoundry/__init__.py", so both wheels ship matched and the release workflow asserts that against the tag.CHANGELOG.md— the[Unreleased]section becomes[0.3.1] — 2026-07-27, with a fresh empty[Unreleased]above it.Also repairs the compare links
The 0.3.0 release never updated them:
[Unreleased]still pointed atv0.2.10and there was no[0.3.0]definition at all, so several releases' "what changed" links were dead. Added0.3.1down to0.2.11.Deliberately not changed
Other files matching
0.3.0are synthetic fixtures and comment examples, not the shipped version —test_sbom_finalize.py's inline__version__string,test_update_check.py's comparator cases, a docstring inpipeline/update_check.py.Ordering
v0.3.1must be tagged from a commit that already contains #12. Before that fix, every tag push dies at the README slug-rewrite step — which is exactly what happened tov0.3.0on 2026-07-13.🤖 Generated with Claude Code