Update Rust crate time to 0.3.30 - autoclosed

This MR contains the following updates:

Package	Type	Update	Change
time (source)	dependencies	patch	0.3.21 -> 0.3.30

---

Release Notes

time-rs/time (time)

v0.3.30

Compare Source

Added

• powerfmt::smart_display::SmartDisplay has been added for the main types in the library. These implementations ensure that values follow the requested fill, width, and alignment when using format! or similar macros. Display is implemented in terms of SmartDisplay.

Fixed

• Large values no longer wrap around in release mode when using NumericalDuration or NumericalStdDuration.

v0.3.29

Compare Source

Added

• Niche value optimization for Date has been added. Both Date and Option<Date> are four bytes.
• Unit conversions have been added. It is now possible to write Second::per(Day), which returns the number of seconds in one day. See the types in the [time::convert module][time::convert module] for more information.

Changed

• The diagnostic for --cfg unsound_local_offset has been removed.
• #![feature(no_coverage)] was previously used internally for code coverage. It is no longer used, so it has been removed.
• The default value for modifier::OffsetHour has been changed. This was unintentionally changed in v0.3.17 and went unnoticed until now. The sign is now only present if needed by default, as was the case previously. This does not affect any situation where format_description! or format_description::parse is used.

Fixed

• Adding or subtracting a std::time::Duration to/from an OffsetDateTime will not result in integer overflow internally. It will still panic if the result is out of range.

v0.3.28

Compare Source

Added

• More additional constants for the well-known Iso8601 format description have been added. This avoids the need to manually configure the format.
• An [end] component has been added. This is ignored during formatting, but is used to indicate the end of input when parsing. If any input remains after this component, an error is returned. This is useful when using the [first] component, as it avoids the need to reorder variants.

Changed

• The exemption for MacOS introduced in 0.3.20 has been removed. This is because some supported versions of MacOS do not meet the requirements for the exemption.
• The UnexpectedTrailingCharacters error variant has been moved to ParseFromDescription. All previously-existing locations of this variant have been deprecated and will no longer be returned.

v0.3.27

Compare Source

This sets the serde dependency requirement to >= 1.0.184 where the binaries have been removed.

v0.3.26

Compare Source

This release contains only a single change. serde is required to be a version prior to 1.0.171. This is due to the decision by the maintainer of serde to include pre-built binaries that are executed without the end user's knowledge. As of the time of publishing, the included binary has not even been reproduced. This is a security risk, and the time project strongly opposes this decision. While this may break some users' builds due to conflicting versions, it is a necessary step to ensure the security.

v0.3.25

Compare Source

Fixed

• Methods such as Time::replace_milliseconds would panic on some out-of-range values. This has been fixed.

v0.3.24

Compare Source

Added

• The subsecond component is taken into account when parsing the unix_timestamp component. If data is conflicting, the subsecond value takes precedence.
• Parsing a Time with only the hour component is now supported. The minute and second, and subsecond components are assumed to be zero.

Changed

• The minimum supported Rust version is now 1.67.0.
• The debug output for Parsed has been improved.
• When parsing, invalid values are now rejected sooner. Previously, the entire input would be parsed before being rejected in the final step. Now, invalid values are rejected as soon as they are encountered. This affects the error variant returned, which may cause minor breakage for any code (incorrectly) relying on the exact error variant.
• When parsing a Time, an error is returned if components are present but not consecutive. For example, if hours and seconds are present, minutes will not be assumed to be zero.

Fixed

• The implementation of Duration::checked_div could return a slightly incorrect result in some cases. This has been fixed.

v0.3.23

Compare Source

Added

• Date::next_occurrence
• Date::prev_occurrence
• Date::nth_next_occurrence
• Date::nth_prev_occurrence
• Weekday::nth_prev
• Month::nth_next
• Month::nth_prev

Changed

The minimum supported Rust version policy has been updated. See the README for details.

Fixed

• Duration::abs correctly returns Duration::MAX when near the minimum value. The nanoseconds value was previously incorrect.
• Compliance with ISO 8601 has been improved. Previously, a UTC offset would be incorrectly rejected in some cases.

v0.3.22

Compare Source

Added

• OffsetDateTime::checked_to_offset

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot.