chore(deps): update rust crate time to v0.3.55 (master)

renovate-bot bot commented

2026-02-16 15:03:47 +01:00

Collaborator

This PR contains the following updates:

Package	Type	Update	Change
time (source)	dependencies	patch	`0.3.44` → `0.3.55`
time (source)	workspace.dependencies	patch	`0.3.44` → `0.3.55`

⚠️ Warning

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

Release Notes

time-rs/time (time)

`v0.3.55`

Compare Source

Fixed

Avoid underflow in DateIter::nth, ensuring correct behavior.
Avoid overflow when deserializing timestamps.
Handle out-of-bounds data when deserializing.
Don't assume that the format being deserialized was generated by the serializer; this previously
led to some valid values being parsed incorrectly and others being rejected.
No longer silence errors when deserializing UtcOffset.
OffsetDateTime::from_unix_timestamp_nanos and UtcDateTime::from_unix_timestamp_nanos correctly
return None for all out-of-range values, rather than unexpectedly panicking in some situations.
OffsetDateTime::checked_to_offset and UtcDateTime::checked_to_offset correctly return None
for all out-of-range values, rather than unexpectedly panicking in some situations.

`v0.3.54`

Compare Source

Added

PrimitiveDateTime has been renamed to PlainDateTime.
Duration has been renamed to SignedDuration.
Iteration is now possible over Date, Month, and Weekday. Relevant iterator methods have been
overridden to ensure maximum performance.

For both PlainDateTime and SignedDuration, a non-deprecated type alias has been added for
backwards compatibility. The new names should be preferred.

Changed

The associated metadata type (for powerfmt implementations) for various types has been changed
to () and made public. This guarantees that no additional metadata will be present.

Performance

More gains when parsing RFC 2822.

There are no publicly-facing changes in this release. It solely works around the cookie crate
relying on an implementation detail of time that was never part of the public API (and thus
subject to semver guarantees). The internal API has been reverted to the extent necessary for
cookie to compile. This measure is temporary; the internal change will be re-applied in an
yet-to-be-determined future release.

`v0.3.52`

Compare Source

Fixed

Subsecond values in the time! macro are parsed using the textual representation, ensuring
accuracy. Previously, they were parsed using the floating point representation, which could result
in a loss of precision and even invalid values.
The date! macro could previously create an invalid value that would then panic at compile time.
The macro now emits a proper error instead.
When parsing an invalid format description, an edge case would inadvertently panic. This now
returns an error as intended.

Added

Support default values when parsing

`v0.3.51`

Compare Source

Fixed

time compiles with macros enabled. This version is otherwise identical to v0.3.50.

`v0.3.50`

Compare Source

Fixed

time compiles with macros enabled. This version is otherwise identical to v0.3.50.

`v0.3.49`

Compare Source

Fixed

Due to a long-standing bug in the Rust compiler, v0.3.48 caused a number of crates to stop
compiling. A patch has been added that avoids triggering the bug.

`v0.3.48`

Compare Source

This version was yanked due to a bug in the Rust compiler.

Security

The number of digits parsed by [subsecond digits:1+] is capped at 32 to avoid parsing unbounded
user input. Digits after the 9^th have no semantic meaning.
Explicitly specify #[repr] for Weekday. The value of the variants is relied upon in multiple
locations for soundness. The practical effect of this change is nothing, as Rust has always mapped
C-like enums to 0..N in memory.

Compatibility

Non-UTF-8 formatting and parsing is deprecated without replacement. It is recommended to only
format and parse valid UTF-8.
format_description::parse is deprecated. It is recommended to use
format_description::parse_borrowed::<3> or format_description::parse_owned::<3>.

Added

All types in the unit module have a generic parameter, though this is currently not used for
much. Usage will be expanded in the future.
Comparisons between types in the unit module and the generic Unit type are permitted.
Support for rand 0.10
Version 3 format descriptions
- Only UTF-8 is supported. As a side effect of this, [ignore] requires that the remaining input
  not begin mid-codepoint.
- Representation is deliberately opaque to allow for arbitrary changes going forward.
- format:false is supported on [optional] components. This is not possible in version 1 and
  version 2 format descriptions due to API compatibility.
- The time::serde::format_description! macro uses a new, clearer syntax for version 3.
  - time::serde::format_description!(mod foo [Date] = "[year]-[month]-[day]");
  - Unlike version 1 and version 2 format descriptions, the type is not automatically brought into
    scope. You must import it yourself.
- Nonsensical combinations of modifiers are rejected. For example, you cannot specify
  case-sensitivity when parsing a numerical month.
- [year] defaults to range:standard
- Components and modifiers are case sensitive (and always lowercase).

Changed

The convert module has been renamed to unit.

Fixed

Macro hygiene has been improved by specifying re-exports.
Fix handling of T in ISO 8601
Support parsing the full range of UTC offset hours
Version 1 nested format descriptions may now start with a component. Previously, a lexer bug
unintentionally prohibited this.
Error when ISO week date overflows the max year. This would previously panic.
Error when padding is specified in strftime format descriptions but the component is not. This
would previously panic.

Performance

Huge performance gains across multiple areas, including:

optimizing equality checks for Duration
optimizing Display impls for all major types
optimizing the formatting of components and well-known formats
precomputing metadata when formatting, reducing allocations
adding fast path for typical RFC 2822 usage
optimizing strftime parsing
refactoring format description parsing

Depending on the area, gains range from 3× to even 11×.

`v0.3.47`

Compare Source

Security

The possibility of a stack exhaustion denial of service attack when parsing RFC 2822 has been
eliminated. Previously, it was possible to craft input that would cause unbounded recursion. Now,
the depth of the recursion is tracked, causing an error to be returned if it exceeds a reasonable
limit.

This attack vector requires parsing user-provided input, with any type, using the RFC 2822 format.

Compatibility

Attempting to format a value with a well-known format (i.e. RFC 3339, RFC 2822, or ISO 8601) will
error at compile time if the type being formatted does not provide sufficient information. This
would previously fail at runtime. Similarly, attempting to format a value with ISO 8601 that is
only configured for parsing (i.e. Iso8601::PARSING) will error at compile time.

Added

Builder methods for format description modifiers, eliminating the need for verbose initialization
when done manually.
date!(2026-W01-2) is now supported. Previously, a space was required between W and 01.
[end] now has a trailing_input modifier which can either be prohibit (the default) or
discard. When it is discard, all remaining input is ignored. Note that if there are components
after [end], they will still attempt to be parsed, likely resulting in an error.

Changed

More performance gains when parsing.

Fixed

If manually formatting a value, the number of bytes written was one short for some components.
This has been fixed such that the number of bytes written is always correct.
The possibility of integer overflow when parsing an owned format description has been effectively
eliminated. This would previously wrap when overflow checks were disabled. Instead of storing the
depth as u8, it is stored as u32. This would require multiple gigabytes of nested input to
overflow, at which point we've got other problems and trivial mitigations are available by
downstream users.

`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.

Configuration

📅 Schedule: (in timezone Europe/Berlin)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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

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

This PR has been generated by Mend Renovate.

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.44` → `0.3.55` | | [time](https://time-rs.github.io) ([source](https://github.com/time-rs/time)) | workspace.dependencies | patch | `0.3.44` → `0.3.55` | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the [Dependency Dashboard](issues/190) for more information. --- ### Release Notes <details> <summary>time-rs/time (time)</summary> ### [`v0.3.55`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0355-2026-08-01) [Compare Source](https://github.com/time-rs/time/compare/v0.3.54...v0.3.55) ##### Fixed - Avoid underflow in `DateIter::nth`, ensuring correct behavior. - Avoid overflow when deserializing timestamps. - Handle out-of-bounds data when deserializing. - Don't assume that the format being deserialized was generated by the serializer; this previously led to some valid values being parsed incorrectly and others being rejected. - No longer silence errors when deserializing `UtcOffset`. - `OffsetDateTime::from_unix_timestamp_nanos` and `UtcDateTime::from_unix_timestamp_nanos` correctly return `None` for all out-of-range values, rather than unexpectedly panicking in some situations. - `OffsetDateTime::checked_to_offset` and `UtcDateTime::checked_to_offset` correctly return `None` for all out-of-range values, rather than unexpectedly panicking in some situations. ### [`v0.3.54`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0354-2026-07-20) [Compare Source](https://github.com/time-rs/time/compare/v0.3.53...v0.3.54) ##### Added - `PrimitiveDateTime` has been renamed to `PlainDateTime`. - `Duration` has been renamed to `SignedDuration`. - Iteration is now possible over `Date`, `Month`, and `Weekday`. Relevant iterator methods have been overridden to ensure maximum performance. For both `PlainDateTime` and `SignedDuration`, a non-deprecated type alias has been added for backwards compatibility. The new names should be preferred. ##### Changed - The associated metadata type (for `powerfmt` implementations) for various types has been changed to `()` and made public. This guarantees that no additional metadata will be present. ##### Performance - More gains when parsing RFC 2822. ### [`v0.3.53`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0353-2026-07-01) [Compare Source](https://github.com/time-rs/time/compare/v0.3.52...v0.3.53) There are no publicly-facing changes in this release. It solely works around the `cookie` crate relying on an implementation detail of `time` that was never part of the public API (and thus subject to semver guarantees). The internal API has been reverted to the extent necessary for `cookie` to compile. This measure is temporary; the internal change will be re-applied in an yet-to-be-determined future release. ### [`v0.3.52`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0352-2026-06-30) [Compare Source](https://github.com/time-rs/time/compare/v0.3.51...v0.3.52) ##### Fixed - Subsecond values in the `time!` macro are parsed using the textual representation, ensuring accuracy. Previously, they were parsed using the floating point representation, which could result in a loss of precision and even invalid values. - The `date!` macro could previously create an invalid value that would then panic at compile time. The macro now emits a proper error instead. - When parsing an invalid format description, an edge case would inadvertently panic. This now returns an error as intended. ##### Added - Support default values when parsing ### [`v0.3.51`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0351-2026-06-22) [Compare Source](https://github.com/time-rs/time/compare/v0.3.50...v0.3.51) ##### Fixed - `time` compiles with `macros` enabled. This version is otherwise identical to v0.3.50. ### [`v0.3.50`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0351-2026-06-22) [Compare Source](https://github.com/time-rs/time/compare/v0.3.49...v0.3.50) ##### Fixed - `time` compiles with `macros` enabled. This version is otherwise identical to v0.3.50. ### [`v0.3.49`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0349-2026-06-13) [Compare Source](https://github.com/time-rs/time/compare/v0.3.48...v0.3.49) ##### Fixed - Due to a long-standing bug in the Rust compiler, v0.3.48 caused a number of crates to stop compiling. A patch has been added that avoids triggering the bug. ### [`v0.3.48`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0348-2026-06-12-YANKED) [Compare Source](https://github.com/time-rs/time/compare/v0.3.47...v0.3.48) *This version was yanked due to a bug in the Rust compiler.* ##### Security - The number of digits parsed by `[subsecond digits:1+]` is capped at 32 to avoid parsing unbounded user input. Digits after the 9<sup>th</sup> have no semantic meaning. - Explicitly specify `#[repr]` for `Weekday`. The value of the variants is relied upon in multiple locations for soundness. The practical effect of this change is nothing, as Rust has always mapped C-like `enum`s to 0..N in memory. ##### Compatibility - Non-UTF-8 formatting and parsing is deprecated without replacement. It is recommended to only format and parse valid UTF-8. - `format_description::parse` is deprecated. It is recommended to use `format_description::parse_borrowed::<3>` or `format_description::parse_owned::<3>`. ##### Added - All types in the `unit` module have a generic parameter, though this is currently not used for much. Usage will be expanded in the future. - Comparisons between types in the `unit` module and the generic `Unit` type are permitted. - Support for `rand` 0.10 - Version 3 format descriptions - Only UTF-8 is supported. As a side effect of this, `[ignore]` requires that the remaining input not begin mid-codepoint. - Representation is deliberately opaque to allow for arbitrary changes going forward. - `format:false` is supported on `[optional]` components. This is not possible in version 1 and version 2 format descriptions due to API compatibility. - The `time::serde::format_description!` macro uses a new, clearer syntax for version 3. - `time::serde::format_description!(mod foo [Date] = "[year]-[month]-[day]");` - Unlike version 1 and version 2 format descriptions, the type is not automatically brought into scope. You must import it yourself. - Nonsensical combinations of modifiers are rejected. For example, you cannot specify case-sensitivity when parsing a numerical month. - `[year]` defaults to `range:standard` - Components and modifiers are case sensitive (and always lowercase). ##### Changed - The `convert` module has been renamed to `unit`. ##### Fixed - Macro hygiene has been improved by specifying re-exports. - Fix handling of `T` in ISO 8601 - Support parsing the full range of UTC offset hours - Version 1 nested format descriptions may now start with a component. Previously, a lexer bug unintentionally prohibited this. - Error when ISO week date overflows the max year. This would previously panic. - Error when padding is specified in `strftime` format descriptions but the component is not. This would previously panic. ##### Performance Huge performance gains across multiple areas, including: - optimizing equality checks for `Duration` - optimizing `Display` impls for all major types - optimizing the formatting of components and well-known formats - precomputing metadata when formatting, reducing allocations - adding fast path for typical RFC 2822 usage - optimizing `strftime` parsing - refactoring format description parsing Depending on the area, gains range from 3× to even 11×. ### [`v0.3.47`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0347-2026-02-05) [Compare Source](https://github.com/time-rs/time/compare/v0.3.46...v0.3.47) ##### Security - The possibility of a stack exhaustion denial of service attack when parsing RFC 2822 has been eliminated. Previously, it was possible to craft input that would cause unbounded recursion. Now, the depth of the recursion is tracked, causing an error to be returned if it exceeds a reasonable limit. This attack vector requires parsing user-provided input, with any type, using the RFC 2822 format. ##### Compatibility - Attempting to format a value with a well-known format (i.e. RFC 3339, RFC 2822, or ISO 8601) will error at compile time if the type being formatted does not provide sufficient information. This would previously fail at runtime. Similarly, attempting to format a value with ISO 8601 that is only configured for parsing (i.e. `Iso8601::PARSING`) will error at compile time. ##### Added - Builder methods for format description modifiers, eliminating the need for verbose initialization when done manually. - `date!(2026-W01-2)` is now supported. Previously, a space was required between `W` and `01`. - `[end]` now has a `trailing_input` modifier which can either be `prohibit` (the default) or `discard`. When it is `discard`, all remaining input is ignored. Note that if there are components after `[end]`, they will still attempt to be parsed, likely resulting in an error. ##### Changed - More performance gains when parsing. ##### Fixed - If manually formatting a value, the number of bytes written was one short for some components. This has been fixed such that the number of bytes written is always correct. - The possibility of integer overflow when parsing an owned format description has been effectively eliminated. This would previously wrap when overflow checks were disabled. Instead of storing the depth as `u8`, it is stored as `u32`. This would require multiple gigabytes of nested input to overflow, at which point we've got other problems and trivial mitigations are available by downstream users. ### [`v0.3.46`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0346-2026-01-23) [Compare Source](https://github.com/time-rs/time/compare/v0.3.45...v0.3.46) ##### 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`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0345-2026-01-13) [Compare Source](https://github.com/time-rs/time/compare/v0.3.44...v0.3.45) ##### 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. </details> --- ### Configuration 📅 **Schedule**: (in timezone Europe/Berlin) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).

renovate-bot bot force-pushed renovate/master-time-0.x-lockfile from 77e368e13a

/ clippy (pull_request) Successful in 3m43s

Details

to 79a522ac9e

/ clippy (pull_request) Failing after 3m45s

Details

2026-03-28 20:02:14 +01:00

Compare

renovate-bot bot force-pushed renovate/master-time-0.x-lockfile from 79a522ac9e

/ clippy (pull_request) Failing after 3m45s

Details

to ba7954ce36

/ clippy (pull_request) Failing after 3m1s

Details

2026-03-31 19:03:07 +02:00

Compare

renovate-bot bot force-pushed renovate/master-time-0.x-lockfile from ba7954ce36

/ clippy (pull_request) Failing after 3m1s

Details

to eba30fd55a

/ clippy (pull_request) Failing after 2m9s

Details

2026-05-23 12:04:17 +02:00

Compare

renovate-bot bot force-pushed renovate/master-time-0.x-lockfile from eba30fd55a

/ clippy (pull_request) Failing after 2m9s

Details

to fdb095887d

/ clippy (pull_request) Failing after 2m6s

Details

2026-06-12 11:00:47 +02:00

Compare

renovate-bot bot changed title from ~~chore(deps): update rust crate time to v0.3.47 (master)~~ to chore(deps): update rust crate time to v0.3.48 (master)

2026-06-12 11:00:49 +02:00

renovate-bot bot changed title from ~~chore(deps): update rust crate time to v0.3.48 (master)~~ to chore(deps): update rust crate time to v0.3.47 (master)

2026-06-13 02:00:59 +02:00

renovate-bot bot force-pushed renovate/master-time-0.x-lockfile from fdb095887d

/ clippy (pull_request) Failing after 2m6s

Details

to ffd242b7b0

/ clippy (pull_request) Failing after 1m51s

Details

2026-06-13 02:00:59 +02:00

Compare

renovate-bot bot force-pushed renovate/master-time-0.x-lockfile from ffd242b7b0

/ clippy (pull_request) Failing after 1m51s

Details

to b1eeef464a

/ clippy (pull_request) Failing after 4m2s

Details

2026-06-14 00:01:06 +02:00

Compare

renovate-bot bot changed title from ~~chore(deps): update rust crate time to v0.3.47 (master)~~ to chore(deps): update rust crate time to v0.3.49 (master)

2026-06-14 00:01:06 +02:00

renovate-bot bot force-pushed renovate/master-time-0.x-lockfile from b1eeef464a

/ clippy (pull_request) Failing after 4m2s

Details

to 1dc8f03dfe

/ clippy (pull_request) Failing after 1m55s

Details

2026-06-22 08:00:52 +02:00

Compare

renovate-bot bot changed title from ~~chore(deps): update rust crate time to v0.3.49 (master)~~ to chore(deps): update rust crate time to v0.3.50 (master)

2026-06-22 08:00:54 +02:00

renovate-bot bot force-pushed renovate/master-time-0.x-lockfile from 1dc8f03dfe

/ clippy (pull_request) Failing after 1m55s

Details

to 815b1a2968

/ clippy (pull_request) Failing after 1m47s

Details

2026-06-22 09:00:55 +02:00

Compare

renovate-bot bot changed title from ~~chore(deps): update rust crate time to v0.3.50 (master)~~ to chore(deps): update rust crate time to v0.3.51 (master)

2026-06-22 09:00:55 +02:00

renovate-bot bot force-pushed renovate/master-time-0.x-lockfile from 815b1a2968

/ clippy (pull_request) Failing after 1m47s

Details

to aae9e686d9

/ clippy (pull_request) Failing after 1m59s

Details

2026-06-30 11:00:56 +02:00

Compare

renovate-bot bot changed title from ~~chore(deps): update rust crate time to v0.3.51 (master)~~ to chore(deps): update rust crate time to v0.3.52 (master)

2026-06-30 11:00:57 +02:00

renovate-bot bot changed title from ~~chore(deps): update rust crate time to v0.3.52 (master)~~ to chore(deps): update rust crate time to v0.3.53 (master)

2026-07-01 14:01:24 +02:00

renovate-bot bot force-pushed renovate/master-time-0.x-lockfile from aae9e686d9

/ clippy (pull_request) Failing after 1m59s

Details

to 5840135d3e

/ clippy (pull_request) Failing after 2m59s

Details

2026-07-01 14:01:29 +02:00

Compare

renovate-bot bot force-pushed renovate/master-time-0.x-lockfile from 5840135d3e

/ clippy (pull_request) Failing after 2m59s

Details

to 60607ba64b

/ clippy (pull_request) Failing after 2m1s

Details

2026-07-20 11:00:56 +02:00

Compare

renovate-bot bot changed title from ~~chore(deps): update rust crate time to v0.3.53 (master)~~ to chore(deps): update rust crate time to v0.3.54 (master)

2026-07-20 11:00:57 +02:00

renovate-bot bot force-pushed renovate/master-time-0.x-lockfile from 60607ba64b

/ clippy (pull_request) Failing after 2m1s

Details

to a8ab964117

/ clippy (pull_request) Failing after 2m1s

Details

2026-08-01 11:00:53 +02:00

Compare

renovate-bot bot changed title from ~~chore(deps): update rust crate time to v0.3.54 (master)~~ to chore(deps): update rust crate time to v0.3.55 (master)

2026-08-01 11:00:55 +02:00

/ clippy (pull_request) Failing after 2m1s

Required

Details

Some required checks were not successful.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin renovate/master-time-0.x-lockfile:renovate/master-time-0.x-lockfile

git switch renovate/master-time-0.x-lockfile

Rows
Columns

chore(deps): update rust crate time to v0.3.55 (master) #337

Release Notes

Fixed

Added

Changed

Performance

Fixed

Added

Fixed

Fixed

Fixed

Security

Compatibility

Added

Changed

Fixed

Performance

Security

Compatibility

Added

Changed

Fixed

Added

Changed

Fixed

Added

Changed

Configuration

Checkout