build(deps): bump time from 0.3.16 to 0.3.17

[dependabot]

Bumps time from 0.3.16 to 0.3.17.

Release notes

Sourced from time's releases.

v0.3.17

See the changelog for details.

Changelog

Sourced from time's changelog.

0.3.17 [2022-11-06]

Changed

• The amount of code generated by time::serde::format_description! is reduced if not all feature flags are active.
• cargo test --tests works with any configuration of feature flags. This occurs by spawning a subprocess that passes --all-features. cargo test --doc works with most combinations of feature flags, including the default. The combination of these changes means that crater will now run on time.
• libc and num_threads are only included as dependencies when needed. They were previously unconditionally included.

Added

• time::format_description::parse_owned, which returns an OwnedFormatItem. This avoids "lifetime hell", where all your structs now need a lifetime because a single field has one. Note that when possible, the borrowed format item (just called FormatItem) is still preferred, as it has significantly fewer allocations. The new OwnedFormatItem is usable for both formatting and parsing, as you would expect.

Compatibility

• The parser for runtime format descriptions has been rewritten. A side effect of this is that some errors have slightly changed. No existing API has been altered, so this is not a breaking change. However, you may notice different errors, which are hopefully better! The parser for compile-time format descriptions has not yet been swapped out. If you notice any bugs, please file an issue.

Commits

• d97594b 0.3.17 release
• 88f5c13 Fix concurrency for GitHub actions
• e5e2a60 Update lints
• 27ea0d4 Use parse_owned in tests
• 4887aa7 Add format_description::parse_owned
• 2ba92f6 Configure codecov
• 2cba2ef Add tests for OwnedFormatItem
• 4d18c08 Implement owned format descriptions
• 139aba1 Move FormatItem definition to its own module
• e4b40ad Remove extraneous debug call
• 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 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]

Superseded by #119.