Replace stale 0.3.1 semver examples in the README and PR template with stable 1.2.3 placeholders
Point readers to pyproject.toml on main for the current released version instead of hardcoding it in docs
Why
Release automation updates pyproject.toml, but the README and PR template were still showing 0.3.1 (actual version is 0.5.0). Using version-agnostic examples avoids this drift after every release.
Test plan
Docs-only change; no code or CI changes
Verified README prefix table and manual release section
Verified PR template bump guidance and pyproject.toml link
## Summary
- Replace stale `0.3.1` semver examples in the README and PR template with stable `1.2.3` placeholders
- Point readers to `pyproject.toml` on `main` for the current released version instead of hardcoding it in docs
## Why
Release automation updates `pyproject.toml`, but the README and PR template were still showing `0.3.1` (actual version is `0.5.0`). Using version-agnostic examples avoids this drift after every release.
## Test plan
- [x] Docs-only change; no code or CI changes
- [x] Verified README prefix table and manual release section
- [x] Verified PR template bump guidance and `pyproject.toml` link
Replace hardcoded semver examples with stable placeholders and point readers to pyproject.toml for the current version.
Co-authored-by: Cursor <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
0.3.1semver examples in the README and PR template with stable1.2.3placeholderspyproject.tomlonmainfor the current released version instead of hardcoding it in docsWhy
Release automation updates
pyproject.toml, but the README and PR template were still showing0.3.1(actual version is0.5.0). Using version-agnostic examples avoids this drift after every release.Test plan
pyproject.tomllinkTest Coverage Report: