Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 5, 2025

This PR contains the following updates:

Package Type Update Change
time (source) dependencies patch 0.3.37 -> 0.3.44

Release Notes

time-rs/time (time)

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

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.

@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 4b9fdf4 to 09ecf8f Compare March 6, 2025 11:58
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from 09ecf8f to 269f0db Compare March 18, 2025 10:31
@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 23, 2025
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from 269f0db to afd51c1 Compare March 23, 2025 22:02
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from afd51c1 to ad96dcd Compare August 10, 2025 13:53
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from ad96dcd to 81dc3fe Compare September 6, 2025 15:52
@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.43 Sep 6, 2025
@renovate renovate bot force-pushed the renovate/time-0.x-lockfile branch from 81dc3fe to 327e3ea Compare September 19, 2025 10:29
@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
Copy link
Contributor Author

renovate bot commented Sep 25, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package time@0.3.37 --precise 0.3.44
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)

@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.44 - autoclosed Oct 19, 2025
@renovate renovate bot closed this Oct 19, 2025
@renovate renovate bot deleted the renovate/time-0.x-lockfile branch October 19, 2025 14:59
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