Update typed-builder requirement from 0.6.0 to 0.9.0

[dependabot-preview]

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

Changelog

Sourced from typed-builder's changelog.

0.9.0 - 2021-01-31

Added

• Builder type implements Clone when all set fields support clone.

Fixed

• Fix code generation for raw identifiers.

0.8.0 - 2020-12-06

Changed

• Upgraded the Rust edition to 2018.

Added

• #[field_defaults(...)] attribute for settings default attributes for all the fields.

0.7.1 - 2020-11-20

Fixed

• Fix lifetime bounds erroneously preserved in phantom generics.

0.7.0 - 2020-07-23

Added

• Brought back default_code, because it needed to resolve conflict with other custom derive proc-macro crates that try to parse [#builder(default = ...)] attribute in order to decide if they are relevant to them - and fail because the expect them to be simple literals.

0.6.0 - 2020-05-18

Added

• Ability to use into and strip_option simultaneously for a field.

Changed

• [BREAKING] Specifying skip twice in the same builder(setter(...)) is no longer supported. Then again, if you were doing that you probably deserve having your code broken.

0.5.1 - 2020-01-26

Fixed

• Prevent Clippy from warning about the panic!() in the faux build method.

0.5.0 - 2020-01-25

Changed

• [BREAKING] Move doc and skip into a subsetting named setter(...). This means that #[builder(doc = "...")], for example, should now be written as #[builder(setter(doc = "..."))].
• [BREAKING] Setter arguments by default are no longer automatically converted to the target type with into(). If you want to automatically convert them, use #[builder(setter(into))]. This new default enables rustc inference for generic types and proper integer literal type detection.
• Improve build errors for incomplete .build() and repeated setters, by creating faux methods with deprecation warnings.

... (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 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)