Repository navigation
chore(main): release 0.5.0 - #47
Merged
sgjholt merged 2 commits intoSep 19, 2026
Merged
Conversation
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>
sgjholt
deleted the
release-please--branches--main--components--specmod
branch
September 19, 2026 20:05
Owner
Author
|
🤖 Created releases: 🌻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.5.0 (2026-09-19)
Features
channel_prioritiesandlocation_priorities, so a station carrying a broadband and an accelerometer contributes one record rather than two (2af57e8)Bug Fixes
max_radius_kmapplies to the download and not only to the station query — FDSN dataselect takes no geographic parameters, so a wildcard request was unbounded (2af57e8)min_radius_kmnow applies on its own, and a non-positive radius or an inverted annulus is refused (2af57e8)Documentation
[smoothing] methodbehaviour change in 0.4.0 (b460d19)This PR was generated with Release Please. See documentation.