Bump frequenz-channels from 1.0.0b2 to 1.0.0rc1

[dependabot[bot]]

Bumps frequenz-channels from 1.0.0b2 to 1.0.0rc1.

Release notes

Sourced from frequenz-channels's releases.

v1.0.0-rc.1

Frequenz channels Release Notes

Summary

This is the first release candidate for version 1.0. It includes few new features and a lot of cleanups and API improvements and polishing. Because of this, there are a lot of breaking changes too, but they should be easy to fix, as they ae mostly renames and reorganizations.

We hope this is the final pre-release before the final 1.0 release, and we don't expect to introduce any further breaking changes. Because of this we encourage you to test it and report any issues you find. You can also use a version constraint like >= 1.0.0-rc.1, < 2.0.0 as the final version should be compatible.

Upgrading

• Anycast

  • __init__: The maxsize argument was renamed to limit and made keyword-only and a new keyword-only name argument was added.

    You should instantiate using Anycast(name=..., limit=...) (or Anycast(name=...) if the default limit is enough) instead of Anycast(...) or Anycast(maxsize=...).

  • new_sender and new_receiver: They now return a base Sender and Receiver class (respectively) instead of a channel-specific Sender or Receiver subclass.

    This means users now don't have access to the internals to the channel-specific Sender and Receiver subclasses.

• Broadcast

  • __init__: The name argument was made optional and keyword-only; resend_latest was also made keyword-only. If a name is not specified, it will be generated from the id() of the instance.

    You should instantiate using Broadcast(name=name, resend_latest=resend_latest) (or Broadcast() if the defaults are enough) instead of Broadcast(name) or Broadcast(name, resend_latest).

  • new_receiver: The maxsize argument was renamed to limit and made keyword-only; the name argument was also made keyword-only. If a name is not specified, it will be generated from the id() of the instance instead of a random UUID.

    You should use .new_receiver(name=name, limit=limit) (or .new_receiver() if the defaults are enough) instead of .new_receiver(name) or .new_receiver(name, maxsize).

  • new_sender and new_receiver now return a base Sender and Receiver class (respectively) instead of a channel-specific Sender or Receiver subclass.

    This means users now don't have access to the internals to the channel-specific Sender and Receiver subclasses.

• Event

  • __init__: The name argument was made keyword-only. The default was changed to a more readable version of id(self).

    You should instantiate using Event(name=...) instead of Event(...).

  • Moved from frequenz.channels.util to frequenz.channels.event.

• FileWatcher

  • Moved from frequenz.channels.util to frequenz.channels.file_watcher.

  • Support classes are no longer nested inside FileWatcher. They are now top-level classes within the new frequenz.channels.file_watcher module (e.g., frequenz.channels.util.FileWatcher.EventType -> frequenz.channels.file_watcher.EventType, frequenz.channels.util.FileWatcher.Event -> frequenz.channels.file_watcher.Event).

• Receiver

... (truncated)

Commits

• c6c92ac Prepare release notes for 1.0.0-rc.1 (#284)
• 7ad6391 Prepare release notes for 1.0.0-rc.1
• e522772 Improve generics usage (#282)
• 13391c8 Update release notes
• 8eed457 Make all select-related classes and functions covariant
• e2c3873 Make merge and Merger covariant
• 7a7fb37 Make ChannelError generic
• 1564a00 Make sender errors type variable covariant
• 0550126 Use the new public type variables
• 808440d Add public generic type vars
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #21.