Use new BaseClient version #109
Conversation
Signed-off-by: Mathias L. Baumann <[email protected]>
github-actions
bot
added
part:docs
Marenz
added
the
status:blocked
Marenz
requested review from
ela-kotulska-frequenz and
hannah-stevenson-frequenz
| "frequenz-api-dispatch == 1.0.0-rc1", | ||
| "frequenz-client-base >= 0.7.0, < 0.8.0", | ||
| "frequenz-client-base >= 0.8.0, < 0.9.0", | ||
| "frequenz-client-common >= 0.1.0, < 0.3.0", |
There was a problem hiding this comment.
Why don't you update RELEASE_NOTES?
There was a problem hiding this comment.
Hmm I usually update them if it's something the user can see, but nothing changed from their perspective in this case, just an indirect dependency
There was a problem hiding this comment.
Yeah, the only issue with bumping dependencies with breaking changes is users are forced to upgrade the dependency too (the thing that is triggering all these release trains), which will force them to update the code because the changes are breaking. This is why we usually document disruptive dependency bumps, because it has a high potential of actually affecting the user at the end. But in development mode (v0.x.x) I think is not that bad if it is missing in the release notes, people are supposed to expect breakage anyway.
Signed-off-by: Mathias L. Baumann <[email protected]>
- **Update to latest channels & dispatch client** Blocked by: * frequenz-floss/frequenz-sdk-python#1109 * frequenz-floss/frequenz-client-dispatch-python#109 * frequenz-floss/frequenz-client-microgrid-python#100
- **Update to latest channels & dispatch client** Blocked by: * frequenz-floss/frequenz-sdk-python#1109 * frequenz-floss/frequenz-client-dispatch-python#109 * frequenz-floss/frequenz-client-microgrid-python#100
3 participants
Uh oh!
There was an error while loading. Please reload this page.