Release 0.10.3 — re-pin README links to v0.10.3#31
Merged
Conversation
Bumps the package to 0.10.3 and re-points the README's tag-pinned repository links from v0.10.2 to v0.10.3. At the frozen v0.10.2 tag, the trust model, toolkit positioning, and CLI example gallery docs were last modified by the v0.10.0 commit, whose CI predated a trust-check fix, so each file page rendered a failing-CI badge. The v0.10.3 tag includes the passing-CI commit that re-touched those docs, so the re-pinned links resolve to a green status. - pyproject.toml / __init__.py: 0.10.2 -> 0.10.3 - README.md / README_KR.md: version surfaces and tag-pinned links - docs/generated/claims*: regenerated - docs/claim_ledger* / docs/launch_note*: version references - CHANGELOG.md: 0.10.3 section - docs/release-notes/v0.10.3.md: new Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
What
Cuts the 0.10.3 release. Bumps the package version and re-pins the README's tag-pinned repository links from
v0.10.2tov0.10.3.Why
The README links are pinned to
blob/v0.10.2/.... Thev0.10.2tag is frozen git history: at that tag, the trust model, toolkit positioning, and CLI example gallery docs are last modified by188c244("Prepare trust-first 0.10.0 release"), whose CI failed (trust-check jobs, fixed in the next commit). So clicking those README links lands on a file page with a red ✗ — a new commit onmaincannot change a frozen tag's history.Re-pinning the links to
v0.10.3resolves this: thev0.10.3tag's history includes278a0a1(PR #30), the passing-CI commit that re-touched those docs, so each file page renders a passing-CI badge.Changes
pyproject.toml/src/antemortem/__init__.py:0.10.2→0.10.3README.md: version surfaces, badges, and tag-pinned repository links →v0.10.3README_KR.md: version surfaces (relative links unchanged)docs/generated/claims.md/claims_kr.md: regenerated viagenerate_readme_claims.py --writedocs/claim_ledger*.md,docs/launch_note*.md: version referencesCHANGELOG.md:[0.10.3]section + compare linksdocs/release-notes/v0.10.3.md: newVerification (local)
pytest -q→ exit 0python scripts/check_repo_consistency.py→ passedpython scripts/generate_readme_claims.py --check→ currentpython scripts/check_claim_ledger.py→ passedpython scripts/release_audit.py→ passed (build, twine check, wheel smoke; wheelantemortem-0.10.3)After merge
Tag
v0.10.3on the squash commit, push the tag, publish the GitHub release. PyPI upload (twine upload) is a separate manual step.🤖 Generated with Claude Code