[sgjholt]

Important

Merge with a merge commit, not a squash. One commit here, so a squash would probably keep the subject — but "probably" is what cost the last release its changelog entry.

Step 4 of docs/releasing.md, now that v0.5.0 is published (20:05 UTC, tag on 4c647cc).

What changed

• ## In progress — not yet released → ## Shipped in v0.5.0. The station-selection work now names a version a reader can install and check, which is the whole point of the distinction the page draws.
• The closing paragraph goes back to saying there is no in-progress section. True again — it was reworded when the section appeared, and it is the sentence on this page most likely to be left stale.
• The 1.0 criterion gets its second observation, and it is not clean either.

On that second observation

v0.5.0 renamed nothing and moved no signature. But max_radius_km cuts against true WGS84 distance now, so the same config can select a different set of stations than it did before, and three radius values that used to be accepted — zero, negative, a minimum outside the maximum — are refused when the config is read. A config is as much a caller as a call site.

Twice in a row seemed worth naming rather than logging twice: what keeps moving is not the API, it is what the API does with a setting that was already there. A deprecation cycle cannot protect against that — there is nothing to deprecate — so the upgrading guide is the only thing that does, and 1.0 will not change that.

That is a judgement about your release and your 1.0 bar, not a fact I can check. Overrule it and I will reword; the section rename and the closing paragraph stand on their own.

Verification

pytest tests/test_release_config.py   19 passed
sphinx-build                          clean (bar blocked intersphinx here)

Both roadmap checks pass on this: every version the page names has a CHANGELOG.md heading, and the page is not behind the published minor.

Release note, for the record

The hand-edited changelog survived into the published release. https://github.com/sgjholt/SpecMod/releases/tag/v0.5.0 carries the acquire entries pointing at 2af57e8, under Features and Bug Fixes, rather than release-please's generated line calling the work documentation. So the PR body is what becomes the release notes, and therefore what Zenodo archives — worth knowing for next time.

🤖 Generated with Claude Code

---

Generated by Claude Code