Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 19, 2025

This PR contains the following updates:

Package Type Update Change
time (source) dependencies patch 0.3.360.3.46

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

time-rs/time (time)

v0.3.46

Compare Source

Added
  • All possible panics are now documented for the relevant methods.

  • The need to use #[serde(default)] when using custom serde formats is documented. This applies
    only when deserializing an Option<T>.

  • Duration::nanoseconds_i128 has been made public, mirroring
    std::time::Duration::from_nanos_u128.

  • Various methods for truncating components have been added, avoiding the need to call the fallible
    replace methods multiple times.

    For PrimitiveDateTime, UtcDateTime, and OffsetDateTime:

    • truncate_to_day

    For Time, PrimitiveDateTime, UtcDateTime, and OffsetDateTime:

    • truncate_to_hour
    • truncate_to_minute
    • truncate_to_second
    • truncate_to_millisecond
    • truncate_to_microsecond
Changed
  • The minimum supported Rust version is now 1.88.0.
  • Significant performance gains in numerous locations. No public APIs were changed or removed as
    part of this.
  • The size of error::ComponentRange, along with types that contain it, has been significantly
    reduced.
Fixed
  • The PartialOrd and Ord implementations of UtcOffset now return the expected result.

v0.3.45

Compare Source

Added
  • time::format_description::StaticFormatDescription type alias for &'static [BorrowedFormatItem<'static>]. This is the type returned by the
    time::macros::format_description! macro.
Changed
  • The minimum supported Rust version is now 1.83.0.
  • All floating point methods on Duration are now const fn.
  • All setters on Parsed are now const fn.
  • The serde dependency has been replaced with serde_core, This reduces compile times by not
    including unused parts of serde.
  • Date::from_julian_day uses a new algorithm, resulting in an approximately 16% performance
    improvement. This method is used internally by numerous other methods.
  • util::is_leap_year uses a new algorithm, resulting in an approximately 8% performance
    improvement.

v0.3.44

Compare Source

Fixed
  • Comparisons of PrimitiveDateTime, UtcDateTime, and OffsetDateTime with differing signs (i.e.
    one negative and one positive year) would return the inverse result of what was expected. This was
    introduced in v0.3.42 and has been fixed.
  • Type inference would fail due to feature unification when wasm-bindgen enabled serde_json.
    This has been fixed by explicitly specifying the type in the relevant locations.

v0.3.43

Compare Source

Added
  • Support for rand 0.9
Fixed
  • In the convert module, any use of per with types that were not the same (such as
    Nanosecond::per(Second)) would not compile due to a bug. This has been fixed.

v0.3.42

Compare Source

Added
  • Time::duration_until
  • Time::duration_since
  • per_t method for all types in time::convert. This is similar to the existing per method, but
    can return any of the primitive numeric types that can represent the result. This will cut down on
    as casts while ensuring correctness. Type inference isn't perfect, so you may need to provide a
    type annotation in some situations.
  • impl PartialOrd for Month and impl Ord for Month; this assumes the months are in the same year
  • SystemTimeExt trait, adding methods for checked arithmetic with time::Duration and obtaining
    the difference between two SystemTimes as a time::Duration
  • Permit using UtcDateTime with rand (this was inadvertently omitted previously)
  • impl core::error::Error for all error types (now available when the std feature is disabled)
  • MacOS can now obtain the local UTC offset in multi-threaded programs as the system APIs are
    thread-safe.
  • #[track_caller] has been added to all relevant methods.
Changed
  • The minimum supported Rust version is now 1.81.0.
  • The dependency on itoa has been removed, as the standard library now has similar functionality
    by default.
  • Formatting a component that involves a floating point number is now guaranteed to be
    deterministic, avoiding any subtle differences between platforms or compiler versions.
Fixed
  • Serializing timestamps with nanosecond precision should always emit the correct value.
    Previously, it could be off by one nanosecond due to floating point imprecision.
  • A previously unknown bug in OffsetDateTime::to_offset and UtcDateTime::to_offset has been
    fixed. The bug could result in a value that was invalid. It was unlikely to ever occur in
    real-world code, as it involved passing a UTC offset that has never been used in any location.
Miscellaneous
  • The amount of code generated by macros has been massively reduced, on the order of 65-70% for
    typical use cases of format_description!.
  • Significant performance gains for comparisons of Time, PrimitiveDateTime, UtcDateTime, and
    OffsetDateTime. The first three have gains of approximately 85% (i.e. 6× faster).
  • Nearly all methods are #[inline].

v0.3.41

Compare Source

Fixed
  • Compatibility with the latest release of deranged. This fix is permanent and covers future
    similar changes upstream.

v0.3.40

Compare Source

Added
  • Visibility modifiers may now be added to the mod generated by time::sere::format_description!.

v0.3.39

Compare Source

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

Compare Source

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

v0.3.37

Compare Source

Added
  • Time::MAX, equivalent to time!(23:59:59.999999999)
  • [year repr:century] is now supported in format descriptions. When used in conjunction with
    [year repr:last_two], there is sufficient information to parse a date. Note that with the
    large-date feature enabled, there is an ambiguity when parsing the two back-to-back.
  • Parsing of strftime-style format descriptions, located at
    time::format_description::parse_strftime_borrowed and
    time::format_description::parse_strftime_owned
  • time::util::refresh_tz and time::util::refresh_tz_unchecked, which updates information
    obtained via the TZ environment variable. This is equivalent to the tzset syscall on Unix-like
    systems, with and without built-in soundness checks, respectively.
  • Month::length and util::days_in_month, replacing util::days_in_year_month.
  • Expressions are permitted in time::serde::format_description! rather than only paths. This also
    drastically improves diagnostics when an invalid value is provided.
Changed
  • Obtaining the system UTC offset on Unix-like systems should now succeed when multi-threaded.
    However, if the TZ environment variable is altered, the program will not be aware of this until
    time::util::refresh_tz or time::util::refresh_tz_unchecked is called. refresh_tz has the
    same soundness requirements as obtaining the system UTC offset previously did, with the
    requirements still being automatically enforced. refresh_tz_unchecked does not enforce these
    requirements at the expense of being unsafe. Most programs should not need to call either
    function.

    Due to this change, the time::util::local_offset module has been deprecated in its entirety. The
    get_soundness and set_soundness functions are now no-ops.

    Note that while calls should succeed, success is not guaranteed in any situation. Downstream
    users should always be prepared to handle the error case.

Fixed
  • Floating point values are truncated, not rounded, when formatting.
  • RFC3339 allows arbitrary separators between the date and time components.
  • Serialization of negative Durations less than one second is now correct. It previously omitted
    the negative sign.
  • From<js_sys::Date> for OffsetDateTime now ensures sub-millisecond values are not erroneously
    returned.

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 was generated by Mend Renovate. View the repository job log.

@netlify
Copy link

netlify bot commented Jan 19, 2025

Deploy Preview for hoard-docs ready!

Name Link
🔨 Latest commit 3c19287
🔍 Latest deploy log https://app.netlify.com/projects/hoard-docs/deploys/697462e3fb0ade000874ad56
😎 Deploy Preview https://deploy-preview-218--hoard-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from bee490b to 46f61de Compare March 5, 2025 06:36
@renovate renovate bot changed the title fix(deps): update rust crate time to v0.3.37 fix(deps): update rust crate time to v0.3.38 Mar 5, 2025
@renovate renovate bot changed the title fix(deps): update rust crate time to v0.3.38 fix(deps): update rust crate time to v0.3.39 Mar 6, 2025
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from 46f61de to 7e9d0c2 Compare March 6, 2025 10:21
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from 7e9d0c2 to b51ae55 Compare March 18, 2025 12:05
@renovate renovate bot changed the title fix(deps): update rust crate time to v0.3.39 fix(deps): update rust crate time to v0.3.40 Mar 18, 2025
@renovate renovate bot changed the title fix(deps): update rust crate time to v0.3.40 fix(deps): update rust crate time to v0.3.41 Mar 24, 2025
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from b51ae55 to fa9505d Compare March 24, 2025 01:47
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from fa9505d to 27c85bf Compare August 10, 2025 12:55
@renovate renovate bot changed the title fix(deps): update rust crate time to v0.3.41 fix(deps): update rust crate time to v0.3.42 Sep 2, 2025
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from 27c85bf to 530c61c Compare September 2, 2025 00:00
@renovate renovate bot changed the title fix(deps): update rust crate time to v0.3.42 fix(deps): update rust crate time to v0.3.43 Sep 2, 2025
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from 530c61c to c954ec0 Compare September 2, 2025 20:43
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from c954ec0 to 34ef049 Compare September 19, 2025 08:56
@renovate renovate bot changed the title fix(deps): update rust crate time to v0.3.43 fix(deps): update rust crate time to v0.3.44 Sep 19, 2025
@renovate renovate bot changed the title fix(deps): update rust crate time to v0.3.44 chore(deps): update rust crate time to v0.3.44 Sep 25, 2025
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from 34ef049 to 9613a61 Compare December 10, 2025 10:37
@renovate renovate bot changed the title chore(deps): update rust crate time to v0.3.44 chore(deps): update rust crate time to v0.3.45 Jan 13, 2026
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from 9613a61 to dc4e482 Compare January 13, 2026 11:11
@renovate renovate bot changed the title chore(deps): update rust crate time to v0.3.45 chore(deps): update rust crate time to v0.3.46 Jan 24, 2026
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from dc4e482 to 3c19287 Compare January 24, 2026 06:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant