From a445e1039f1dca03d7d43ed3f4513cbe76da2c76 Mon Sep 17 00:00:00 2001
From: James Holt <15035434+sgjholt@users.noreply.github.com>
Date: Sat, 19 Sep 2026 13:40:40 -0500
Subject: [PATCH 1/2] chore(main): release 0.5.0

---
 .release-please-manifest.json |  2 +-
 CHANGELOG.md                  | 12 ++++++++++++
 2 files changed, 13 insertions(+), 1 deletion(-)

diff --git a/.release-please-manifest.json b/.release-please-manifest.json
index 2537c1f..f1c1e58 100644
--- a/.release-please-manifest.json
+++ b/.release-please-manifest.json
@@ -1,3 +1,3 @@
 {
-  ".": "0.4.0"
+  ".": "0.5.0"
 }
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 1e6c3a3..d8d09bd 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -9,6 +9,18 @@ release could have this problem — every later one has a real predecessor tag 
 so leave subsequent headings as generated. release-please only prepends to this
 file, so this edit survives. -->
 
+## [0.5.0](https://github.com/sgjholt/SpecMod/compare/v0.4.0...v0.5.0) (2026-09-19)
+
+
+### Features
+
+* **acquire:** document the station-selection release, and name its version ([b460d19](https://github.com/sgjholt/SpecMod/commit/b460d1922c21822a81b6aeb06aa6d5f7193d92e1))
+
+
+### Documentation
+
+* **roadmap:** file v0.4.0 as shipped, and the acquire work as merged ([e113abb](https://github.com/sgjholt/SpecMod/commit/e113abb97d80737a2c4a791a6543d945bdb7ba9c))
+
 ## [0.4.0](https://github.com/sgjholt/SpecMod/compare/v0.3.0...v0.4.0) (2026-09-16)
 
 

From 888a1276588edf9ad32c9135ab31bb7be8fdbe4f Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Sat, 19 Sep 2026 18:53:28 +0000
Subject: [PATCH 2/2] chore(changelog): name the acquire work the 0.5.0 tag
 actually carries
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

release-please generated the 0.5.0 section from the commits it could parse, and
the one that carries this release's behaviour changes is not among them: 2af57e8,
the squash merge of #45, has a subject that is not a Conventional Commit, so the
generated Features line described b460d19 — the commit that restored the record —
which is documentation about the change rather than the change.

Left alone, the 0.5.0 changelog and the GitHub Release minted from it would say
a radius fix, a WGS84 cut and two new config fields were "documentation". This
names them and points at the commit that carries them. `docs/releasing.md` makes
reading the changelog the review step for exactly this.

Hand-edited, like the 0.2.0 heading above it, with a comment saying why.
release-please only prepends to the file, so it survives the next release.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 CHANGELOG.md | 28 +++++++++++++++++++++++++++-
 1 file changed, 27 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index d8d09bd..16d6600 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -11,14 +11,40 @@ file, so this edit survives. -->
 
 ## [0.5.0](https://github.com/sgjholt/SpecMod/compare/v0.4.0...v0.5.0) (2026-09-19)
 
+<!-- The `acquire` entries below are edited by hand, and are the second entry
+in this file that is. The work shipped in 2af57e8, the squash merge of #45,
+whose subject is not a Conventional Commit — release-please could not parse it
+("unexpected token ' ' at 1:5") and generated nothing for it. What it did
+generate was the later commit that restored the record, which is documentation
+describing the change rather than the change. These name the change and point
+at the commit that carries it. release-please only prepends to this file, so
+the edit survives. -->
 
 ### Features
 
-* **acquire:** document the station-selection release, and name its version ([b460d19](https://github.com/sgjholt/SpecMod/commit/b460d1922c21822a81b6aeb06aa6d5f7193d92e1))
+* **acquire:** rank co-sited instruments with `channel_priorities` and
+  `location_priorities`, so a station carrying a broadband and an
+  accelerometer contributes one record rather than two
+  ([2af57e8](https://github.com/sgjholt/SpecMod/commit/2af57e8e958d474a25e34b9065f9e54d1a1a42fa))
+
+
+### Bug Fixes
+
+* **acquire:** ask for waveforms by name, so `max_radius_km` applies to the
+  download and not only to the station query — FDSN dataselect takes no
+  geographic parameters, so a wildcard request was unbounded
+  ([2af57e8](https://github.com/sgjholt/SpecMod/commit/2af57e8e958d474a25e34b9065f9e54d1a1a42fa))
+* **acquire:** cut the radius against true WGS84 distance rather than a fixed
+  111.195 km per degree, which moved the boundary by up to half a percent with
+  latitude; `min_radius_km` now applies on its own, and a non-positive radius
+  or an inverted annulus is refused
+  ([2af57e8](https://github.com/sgjholt/SpecMod/commit/2af57e8e958d474a25e34b9065f9e54d1a1a42fa))
 
 
 ### Documentation
 
+* **acquire:** upgrading notes for the station selection, and for the
+  `[smoothing] method` behaviour change in 0.4.0 ([b460d19](https://github.com/sgjholt/SpecMod/commit/b460d1922c21822a81b6aeb06aa6d5f7193d92e1))
 * **roadmap:** file v0.4.0 as shipped, and the acquire work as merged ([e113abb](https://github.com/sgjholt/SpecMod/commit/e113abb97d80737a2c4a791a6543d945bdb7ba9c))
 
 ## [0.4.0](https://github.com/sgjholt/SpecMod/compare/v0.3.0...v0.4.0) (2026-09-16)