The [year] component (in format descriptions) now supports a range modifier, which can be
either standard or extended. The default is extended for backwards compatibility. This is
intended as a manner to opt out of the extended range when the large-dates feature is enabled.
When the large-dates feature is not enabled, the modifier has no effect.
UtcDateTime, which is semantically equivalent to an OffsetDateTime with UTC as its offset. The
advantage is that it is the same size as a PrimitiveDateTime and has improved operability with
well-known formats.

As part of this, there were some other additions:
- utc_datetime! macro, which is similar to the datetime! macro but constructs a UtcDateTime.
- PrimitiveDateTime::as_utc
- OffsetDateTime::to_utc
- OffsetDateTime::checked_to_utc
time::serde::timestamp::milliseconds_i64, which is a module to serialize/deserialize timestamps
as the Unix timestamp. The pre-existing module does this as an i128 where an i64 would
suffice. This new module should be preferred.

Changed

error::Format has had its source() implementation changed to no longer return a boxed value
from the ComponentRange variant. If you were explicitly expecting this, you will need to update
your code. The method API remains unchanged.
[year repr:century] supports single-digit values.
All format_into methods accept ?Sized references.

Miscellaneous

Some non-exhaustive enum variants that are no longer used have been modified to be statically
proven as uninhabited. The relevant fields are doc-hidden and not semver-guaranteed to remain as
such, though it is unlikely to change.
An unnecessary check when parsing RFC 2822 has been removed.
Various methods have had their implementations changed, resulting in significant performance
gains. Among the methods changed are
- util::is_leap_year
- util::weeks_in_year
- Month::length
- Date::to_calendar_date
- Date::month
- Date::day
- Date::from_julian_day
- Date::to_julian_day
- other methods that call into these methods

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 PR becomes conflicted, or you tick the rebase/retry checkbox.

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

If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [time](https://time-rs.github.io) ([source](https://github.com/time-rs/time)) | dependencies | patch | `0.3.37` -> `0.3.41` | --- ### Release Notes <details> <summary>time-rs/time (time)</summary> ### [`v0.3.41`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0341-2025-03-23) [Compare Source](https://github.com/time-rs/time/compare/v0.3.40...v0.3.41) ##### Fixed - Compatibility with the latest release of `deranged`. This fix is permanent and covers future similar changes upstream. ### [`v0.3.40`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0340-2025-03-18) [Compare Source](https://github.com/time-rs/time/compare/v0.3.39...v0.3.40) ##### Added - Visibility modifiers may now be added to the `mod` generated by `time::sere::format_description!`. ### [`v0.3.39`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0339-2025-03-06) [Compare Source](https://github.com/time-rs/time/compare/v0.3.38...v0.3.39) ##### Fixed - Doc tests run successfully with the default feature set. - wasm builds work again. Both of these were regressions in v0.3.38 and are now checked in CI. ### [`v0.3.38`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0338-2025-03-05) [Compare Source](https://github.com/time-rs/time/compare/v0.3.37...v0.3.38) ##### Added - The `[year]` component (in format descriptions) now supports a `range` modifier, which can be either `standard` or `extended`. The default is `extended` for backwards compatibility. This is intended as a manner to opt *out* of the extended range when the `large-dates` feature is enabled. When the `large-dates` feature is not enabled, the modifier has no effect. - `UtcDateTime`, which is semantically equivalent to an `OffsetDateTime` with UTC as its offset. The advantage is that it is the same size as a `PrimitiveDateTime` and has improved operability with well-known formats. As part of this, there were some other additions: - `utc_datetime!` macro, which is similar to the `datetime!` macro but constructs a `UtcDateTime`. - `PrimitiveDateTime::as_utc` - `OffsetDateTime::to_utc` - `OffsetDateTime::checked_to_utc` - `time::serde::timestamp::milliseconds_i64`, which is a module to serialize/deserialize timestamps as the Unix timestamp. The pre-existing module does this as an `i128` where an `i64` would suffice. This new module should be preferred. ##### Changed - `error::Format` has had its `source()` implementation changed to no longer return a boxed value from the `ComponentRange` variant. If you were explicitly expecting this, you will need to update your code. The method API remains unchanged. - `[year repr:century]` supports single-digit values. - All `format_into` methods accept `?Sized` references. ##### Miscellaneous - Some non-exhaustive enum variants that are no longer used have been modified to be statically proven as uninhabited. The relevant fields are doc-hidden and not semver-guaranteed to remain as such, though it is unlikely to change. - An unnecessary check when parsing RFC 2822 has been removed. - Various methods have had their implementations changed, resulting in significant performance gains. Among the methods changed are - `util::is_leap_year` - `util::weeks_in_year` - `Month::length` - `Date::to_calendar_date` - `Date::month` - `Date::day` - `Date::from_julian_day` - `Date::to_julian_day` - other methods that call into these methods </details> --- ### 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 PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).