Repository navigation
release: v0.12.0 - #19
Merged
Merged
Conversation
Version bump and changelog. MeteoAlarm now falls back to matching the feed's own area names when no EMMA_ID filter applies; no wire-shape change since 0.11.0.
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
1 participant
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.
Version bump and changelog for the area-name matcher that landed in #18.
MeteoAlarm filtering now falls back to the feed's own
cap:areaDescvalues when no EMMA_ID filter applies, which narrows the feed for Portugal and Croatia and for the nine feeds the 0.11.0 census found carrying no EMMA_ID geocodes. The EMMA_ID stage is unchanged and still decides quiet days.No wire-shape change since 0.11.0, so this is additive: 0.11.0 -> 0.12.0.
Merging this then tagging
v0.12.0runs the release workflow: validate, publish to crates.io over OIDC, GitHub release.