Repository navigation
Prepare release notes for release v0.4.0 - #199
Merged
llucax merged 1 commit intoJun 11, 2026
Merged
llucax merged 1 commit into
llucax merged 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
tiyash-basu-frequenz
approved these changes
Jun 11, 2026
llucax
added a commit
to llucax/frequenz-client-common-python
that referenced
this pull request
Sep 28, 2026
The next commits use `frequenz.core.warnings`, which is not released yet: the module itself is added by frequenz-floss/frequenz-core-python#199, and the per-alias `DeprecatedAlias` messages used here come from frequenz-floss#200, stacked on frequenz-floss#199. Until both are merged and released, depend on frequenz-floss#200's head directly. The dependency goes through the upstream repository URL rather than the fork the PR comes from, because the fork has no tags: built from there, the package gets version `0.0.postN`, while from upstream it is `1.4.0.post34`, which keeps any other `frequenz-core >= 1.4` requirement in the dependency tree satisfiable. This commit must be replaced with `frequenz-core >= 1.5.0, < 2` once v1.5.0 is released, before merging. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
llucax
added a commit
to llucax/frequenz-client-common-python
that referenced
this pull request
Sep 28, 2026
The next commits use `frequenz.core.warnings`, which is not released yet: the module itself is added by frequenz-floss/frequenz-core-python#199, and the per-alias `DeprecatedAlias` messages used here come from frequenz-floss#200, stacked on frequenz-floss#199. Until both are merged and released, depend on frequenz-floss#200's head directly. The dependency goes through the upstream repository URL rather than the fork the PR comes from, because the fork has no tags: built from there, the package gets version `0.0.postN`, while from upstream it is `1.4.0.post34`, which keeps any other `frequenz-core >= 1.4` requirement in the dependency tree satisfiable. This commit must be replaced with `frequenz-core >= 1.5.0, < 2` once v1.5.0 is released, before merging. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
llucax
added a commit
to llucax/frequenz-client-common-python
that referenced
this pull request
Sep 30, 2026
The next commits use `frequenz.core.warnings`, which is not released yet: the module itself is added by frequenz-floss/frequenz-core-python#199, and the per-alias `DeprecatedAlias` messages used here come from frequenz-floss#200, stacked on frequenz-floss#199. Until both are merged and released, depend on frequenz-floss#200's head directly. The dependency goes through the upstream repository URL rather than the fork the PR comes from, because the fork has no tags: built from there, the package gets version `0.0.postN`, while from upstream it is `1.4.0.post34`, which keeps any other `frequenz-core >= 1.4` requirement in the dependency tree satisfiable. This commit must be replaced with `frequenz-core >= 1.5.0, < 2` once v1.5.0 is released, before merging. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
llucax
added a commit
to llucax/frequenz-client-common-python
that referenced
this pull request
Oct 1, 2026
The next commits use `frequenz.core.warnings`, which is not released yet: the module itself is added by frequenz-floss/frequenz-core-python#199, and the per-alias `DeprecatedAlias` messages used here come from frequenz-floss#200, stacked on frequenz-floss#199. Until both are merged and released, depend on frequenz-floss#200's head directly. The dependency goes through the upstream repository URL rather than the fork the PR comes from, because the fork has no tags: built from there, the package gets version `0.0.postN`, while from upstream it is `1.4.0.post34`, which keeps any other `frequenz-core >= 1.4` requirement in the dependency tree satisfiable. This commit must be replaced with `frequenz-core >= 1.5.0, < 2` once v1.5.0 is released, before merging. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
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.
No description provided.