chore: release hotdata v0.9.0 - #161
Conversation
There was a problem hiding this comment.
Release metadata is internally consistent: pyproject.toml 0.8.0 → 0.9.0, uv.lock updated to match, and CHANGELOG.md gains a ## [0.9.0] - 2026-08-11 section holding the former [Unreleased] body — the exact shape scripts/update_changelog.py produces and what scripts/check-release.py looks for. No other version string needs touching; hotdata.__version__ and Configuration.to_debug_report both read installed package metadata rather than a hardcoded literal.
Note that the release metadata check was still queued when I reviewed, so I can't report its result.
849c21f to
e9c22cb
Compare
There was a problem hiding this comment.
Release PR verified: pyproject.toml and uv.lock both at 0.9.0, CHANGELOG.md gained a ## [0.9.0] - 2026-08-11 heading with the prior Unreleased body moved under it (matching what scripts/update_changelog.py produces and what scripts/check-release.py looks for), and no stale 0.8.0 references remain outside the changelog history. hotdata.__version__ reads from package metadata, so no source constant needs bumping.
Note that release checks (Check release metadata, unit/integration tests) were still queued/in progress when this review ran — I did not verify their results.
Summary
Release hotdata v0.9.0.
Checklist
pyproject.tomlCHANGELOG.mdupdatedAfter merge, run
./scripts/release.sh publishfrom a cleanmaincheckout.