release: prepare 0.5.0 candidate and migration guidance - #423
Conversation
…cenarios-to-the-compa' into enhancement/307-20261003-v1-0-publish-the-post-0-4-3-fixes-under-a-new-package-versio
…cenarios-to-the-compa' into enhancement/307-20261003-v1-0-publish-the-post-0-4-3-fixes-under-a-new-package-versio
…cenarios-to-the-compa' into enhancement/307-20261003-v1-0-publish-the-post-0-4-3-fixes-under-a-new-package-versio
7 tasks done
This branch has not been deployed
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.
Prepare the immutable 0.5.0 release candidate: align VERSION and package metadata, cut the dated changelog section, document the 0.4.x migration boundary, and provide the publication/evidence checklist. The changelog validator now permits the newest VERSION-matching section to precede its tag while retaining tag checks for published history.
This draft is the final car of the 0.5.0 train, after #422. The release must also incorporate the remaining existing 0.5.0 PRs before final review. Refresh the proposed date and final changelog against the integrated release commit.
Publication is pending: independent approval, final hosted checks, TestPyPI rehearsal, annotated tag on protected main, production environment approval, PyPI/GitHub publication, and matching checksums/SBOM/attestations. No tag or package was published by this PR train. Keep the release issue open until that evidence is complete.
Refs #307.
Branch maintenance
Refs #426. Targets the branch for #422. Retarget and refresh after that parent is squash-merged; preserve the ordered stack.
The branch was refreshed without rewriting history to include
mainata576cc279739eae5e4cfc33ffab2a7fb56de24de.Current-head validation
At
96fba375a4e711bcfd99668491a8d6c53ef971d3: uv lock freshness and full aggregate (coverage, typing, style, contracts, benchmark, static and dependency security) passed locally with all declared extras. Runtime result: 661 passed, 1 warning, 294 subtests passed in 12.86s. The aggregate was run after integration; earlier package-publication evidence remains separate from this branch refresh.Hosted checks: 7/7 required checks passed; 0 checks pending; 0 unsuccessful checks at 2026-10-04T14:19:40.760978+00:00. See the PR Checks tab and #426 for subsequent results.