Repository navigation
Complete the release notes for v0.4.1 - #286
Merged
llucax merged 4 commits intoSep 15, 2026
Merged
llucax merged 4 commits into
llucax merged 4 commits into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Replace the template placeholder with an overview of the release: the new Microgrid and Assets API wrappers, the move to validity-in-the-type conversion with deprecations scheduled for v0.5.0, and a pointer to the intentional hard breaks listed in the Upgrading section. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Two changes to symbols released in v0.4.0 were missing from the Upgrading section: * `Bounds` now raises `ValueError` on a `NaN` endpoint (frequenz-floss#254). * `MetricConnection.name` is a plain `str` defaulting to `""` instead of `str | None` defaulting to `None` (frequenz-floss#257). Add a bullet for each, with the migration hints. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
* Mention that `metric_config_bounds` keys also store the raw `0` for unspecified metrics (frequenz-floss#224). * Merge the two `Microgrid` bullets, which described the same addition. * Describe the `ElectricalComponent` boolean accessors (frequenz-floss#237), the `CategorySpecificInfo` field (frequenz-floss#257, frequenz-floss#273) and the aggregated `metric_config_bounds` (frequenz-floss#268). * Add a compact list of the smaller supporting types from frequenz-floss#248 and frequenz-floss#249 (`Invalid{Latitude,Longitude,CountryCode}`, `InvalidLifetime` and their errors). Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Exceptions reporting an invalid value now render it with `str()` instead of `repr()` (frequenz-floss#258); this was missing from Bug Fixes. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
llucax
requested review from
daniel-zullo-frequenz and
tiyash-basu-frequenz
September 15, 2026 10:13
llucax
enabled auto-merge
September 15, 2026 10:15
daniel-zullo-frequenz
approved these changes
Sep 15, 2026
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
Reviewers
Assignees
2 participants
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.
Fill the gaps found in a pre-release sanity check of RELEASE_NOTES.md:
The PaginationInfo breaking change from #217 is documented separately in #285, which adds InvalidPaginationInfo and pagination_info_from_proto2.