Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 1, 2025

This PR contains the following updates:

Package Type Update Change
divan dev-dependencies patch 0.1.15 -> 0.1.21
jiff dev-dependencies patch 0.2.6 -> 0.2.11

Release Notes

nvzqz/divan (divan)

v0.1.21

Compare Source

Fixed
  • Divan::skip_exact behaved incorrectly in v0.1.19.
Changed
  • Improved handling of internal code around filters and those responsible for
    sacking the people who have just been sacked have been sacked.

v0.1.20

Compare Source

Fixed
  • Divan::skip_regex accidentally dropped
    regex_lite::Regex
    and behaved incorrectly in v0.1.19.

v0.1.19

Compare Source

Fixed
  • [cargo-nextest] no longer skips benchmarks with argument parameters ([#​75]).
Changed
  • Organized positive and negative filters into a split buffer.

v0.1.18

Compare Source

Added
  • Support for [cargo-nextest] running benchmarks as tests.

  • [prelude] module for simplifying imports of [#[bench]][bench_attr],
    [#[bench_group]][bench_group_attr], [black_box], [black_box_drop],
    [AllocProfiler], [Bencher], and [Divan].

  • Support wasi and emscripten targets.

v0.1.17

Compare Source

Changed
  • Set [MSRV] to 1.80 for [LazyLock] and new size_of prelude import.

  • Reduced thread pool memory usage by many kilobytes by using rendezvous
    channels instead of array-based channels.

v0.1.16

Compare Source

Added
  • Thread pool for reusing threads across multi-threaded benchmarks. The result
    is that when running Divan benchmarks under a sampling profiler, the
    profiler's output will be cleaner and easier to understand. ([#​37])

  • Track the maximum number of allocations during a benchmark.

Changed
  • Make private Arg::get trait method not take self, so that text editors
    don't recommend using it. ([#​59])

  • Cache BenchOptions using LazyLock instead of OnceLock, saving space and
    simplifying the implementation.

BurntSushi/jiff (jiff)

v0.2.11

Compare Source

===================
This release includes new APIs for customizing Jiff's strtime behavior along
with a few minor bug fixes. Jiff's strtime formatting API has also been
optimized. It's about twice as fast as it was.

This release also coincides with the publication of jiff-icu 0.2.0-beta.2,
which has support for icu 2.0.0-beta.2.

Enhancements:

  • #​338:
    Add support for the %c, %r, %X and %x conversion specifiers.
  • #​341:
    Add support for %q in jiff::fmt::strtime (prints quarter of year).
  • #​342:
    Add support for %::z and %:::z in jiff::fmt::strtime.
  • #​344:
    Add support for %N in jiff::fmt::strtime (alias for %9f).
  • #​350:
    Add a "lenient" mode for strtime formatting APIs that ignores most errors.

Bug fixes:

  • #​328:
    Document default precision behavior of Display impls for datetime types.
  • #​340:
    Allow whitespace in more places in RFC 2822 parser (improves spec compliance).
  • #​346:
    TimeZone::get("UTC") should now always return TimeZone::UTC.

Performance:

  • #​338:
    Jiff's strftime APIs are now approximately twice as fast as they were.
    Performance should be comparable to chrono and time's prebuilt APIs.

v0.2.10

Compare Source

===================
This release includes a bug fix for parsing Tuesday when using %A via
Jiff's strptime APIs. Specifically, it would recognize Tueday instead of
Tuesday.

Bug fixes:

  • #​333:
    Fix typo in strptime parsing from Tueday to Tuesday.

v0.2.9

Compare Source

==================
This release includes a bug fix that, in debug mode, could result in datetime
types having different hashes for the same value. This could cause problems,
for example, if you are using datetimes as keys in a hash map. This problem
didn't exist when Jiff was compiled in release mode.

This release also improves the panic message shown when the js feature isn't
enabled and the current time is requested on wasm32-unknown-unknown targets.

Enhancements:

  • #​296:
    Provide a better panic message when Zoned::now() fails on WASM.

Bug fixes:

  • #​330:
    Fix bug where Hash on datetime types could yield different hash values for
    the same underlying date/time.

v0.2.8

Compare Source

==================
This release fixes a bug where the constructors on SignedDuration
for floating point durations could panic (in debug mode) or produce
incorrect results (in release mode). This bug only impacts users of
the try_from_secs_{f32,f64} and from_secs_{f32,f64} methods on
SignedDuration.

Enhancements:

  • #​326:
    Add an alternate Debug impl for SignedDuration that only shows its second
    and nanosecond components (while using only one component when the other is
    zero).

Bug fixes:

  • #​324:
    Fix a bug that could produce a panic or incorrect results in
    SignedDuration::(try_)?from_secs_{f32,f64}.

v0.2.7

Compare Source

==================
This release includes a bug fix that changes how an empty but set TZ
environment variable is interpreted (as indistinguishable from TZ=UTC).
This also includes a new enabled by default create feature, perf-inline,
which allows toggling Jiff's use of inline(always). This may help improve
compile times or decrease binary size.

Enhancements:

  • #​320:
    Remove some internal uses of generics to mildly improve compile times.
  • #​321:
    Add perf-inline crate feature for controlling inline(always) annotations.

Bug fixes:

  • #​311:
    Make TZ= indistinguishable from TZ=UTC.

Configuration

📅 Schedule: Branch creation - "before 5am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 enabled auto-merge (squash) May 1, 2025 02:51
@renovate renovate bot force-pushed the renovate/compatible-(dev) branch from 71ac9f7 to 03b948f Compare May 1, 2025 22:19
@renovate renovate bot merged commit 74072ba into master May 1, 2025
26 of 27 checks passed
@renovate renovate bot deleted the renovate/compatible-(dev) branch May 1, 2025 22:28
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