chore: release 0.9.0 (docs follow-up — README + KR sync + sdist fix)#25
Conversation
- README_KR.md synced with 0.8.0/0.9.0 changes (Gemini callout + Troubleshooting in Korean) - sdist.include now lists README_KR.md (was previously omitted, causing GitHub-only KR docs) - pyproject + __init__ version 0.8.0 -> 0.9.0 (minor bump for PyPI page visibility) - CHANGELOG entry for 0.9.0 0.8.0 PyPI page showed pypi-0.6.0 badge (pre-#24 README). 0.9.0 republishes with the corrected README + KR sync + sdist fix. No code changes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
f3e007e to
3cb1d3f
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3cb1d3fe0f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| [project] | ||
| name = "antemortem" | ||
| version = "0.8.0" | ||
| version = "0.9.0" |
There was a problem hiding this comment.
Align release docs with published 0.9.0 version
This release now publishes the package as 0.9.0, but the READMEs that will be shown to users still advertise the PyPI badge as pypi-0.8.0 (rg 'pypi-0.8.0|0.9.0' shows the mismatch in both README files). When this version is uploaded, the PyPI page will again display a stale version badge, which is the exact release problem described in the changelog; update the badge/release text to match the version being published or keep the package version at the documented patch release.
Useful? React with 👍 / 👎.
Docs follow-up to 0.8.0. No code changes; minor bump for PyPI page visibility (0.8.0 page rendered with stale README, badge stuck at 0.6.0).
🤖 Generated with Claude Code