Update typed-builder requirement from 0.15.0 to 0.16.0 in /crates/mux-client

[dependabot]

Updates the requirements on typed-builder to permit the latest version.

Changelog

Sourced from typed-builder's changelog.

0.16.0 - 2023-08-26

Added

• #[builder(crate_module_path = ...)] for overcoming cases where the derive macro is used in another crate's macro (see issue #109)

0.15.2 - 2023-08-03

Fixed

• Fix const generics generating "empty" entries in some lists, resulting in consecutive commas (see issue #106)

0.15.1 - 2023-07-10

Fixed

• no-std build.

0.15.0 - 2023-07-06

Changed

• [BREAKING] Split the derive macro out to a separate procmacro crate. This is considered a breaking change because reexporting and/or renmaing the crate can now prevent the generated code from finding the types it needs (see issue #101)

Fixed

• Marking a field as #[deprecated] now behaves properly - TypedBuilder generated code itself does trigger the deprecation warning, and instead the setter for that field now does.
• The "fake" build method when required fields are not provided now returns the never type ("!"). Refer to PR #97 for more thorough explanation.

Added

• Support for setter method prefixes and suffixes #[builder(field_defaults(setter(prefix = "...", suffix = "...")))]. This either prepends or appends the provided string to the setter method. This allows method names like: set_x(), with_y(), or set_z_value().

0.14.0 - 2023-03-08

Added

• build_method(into) and build_method(into = ...).

0.13.0 - 2023-03-05

Changed

y

• [BREAKING] Builder state parameter moved to the end of the generated builder type's parameters list.
• Generated builder type's builder state parameter now defaults to tuple of empty tuples. This means the empty builder, where no parameter is yet set.

Fixed

• #[builder(build_method(...))] now affects the fake build method that's generated to add information to the compiler error.

0.12.0 - 2023-01-29

Removed

... (truncated)

Commits

• See full diff 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 <dependency name> 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)