Skip to content

Clear release notes #1100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 11, 2024
Merged

Clear release notes #1100

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 4 additions & 20 deletions RELEASE_NOTES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,32 +2,16 @@

## Summary

This release focus on improving the config management, but also introduces other minor improvements and fixes an important bug.
<!-- Here goes a general summary of what this release is about -->

## Upgrading

- The `ConfigManagingActor` now takes multiple configuration files as input, and the argument was renamed from `config_file` to `config_files`. If you are using this actor, please update your code. For example:

```python
# Old
actor = ConfigManagingActor(config_file="config.toml")
# New
actor = ConfigManagingActor(config_files=["config.toml"])
```

- The `MovingWindow` now take all arguments as keyword-only to avoid mistakes.
- The `frequenz-quantities` dependency was bumped to `1.0.0rc3`.
- The `ComponentMetricsRequest` now produces a channel name without the `start_date` if the `start_date` is `None`. If you are somehow relying on the old behavior, please update your code.
<!-- Here goes notes on how to upgrade from previous versions, including deprecations and what they should be replaced with -->

## New Features

- The `ConfigManagingActor` can now take multiple configuration files as input, allowing to override default configurations with custom configurations.
- A new `frequenz.sdk.config.load_config()` function is available to load configurations using `marshmallow_dataclass`es with correct type hints.
- Implement and standardize logging configuration with the following changes:
* Add `LoggerConfig` and `LoggingConfig` to standardize logging configuration.
* Create `LoggingConfigUpdater` to handle runtime config updates.
* Support individual log level settings for each module.
<!-- Here goes the main new features and examples or instructions on how to use them -->

## Bug Fixes

- Fixes an issue where PV and EV system bounds were not available to the Power Manager sometimes when requested after startup.
<!-- Here goes notable bug fixes that are worth a special mention or explanation -->
Loading