Skip to content

deps(deps): bump the rust-runtime group across 1 directory with 9 updates#66

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/rustytime/main/rust-runtime-ce7b865507
Open

deps(deps): bump the rust-runtime group across 1 directory with 9 updates#66
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/rustytime/main/rust-runtime-ce7b865507

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Apr 13, 2026

Bumps the rust-runtime group with 9 updates in the /rustytime directory:

Package From To
tokio 1.50.0 1.51.1
uuid 1.22.0 1.23.0
rand 0.10.0 0.10.1
indexmap 2.13.0 2.14.0
apalis-postgres 1.0.0-rc.6 1.0.0-rc.7
apalis 1.0.0-rc.6 1.0.0-rc.7
apalis-cron 1.0.0-rc.6 1.0.0-rc.7
moka 0.12.14 0.12.15
serde_qs 1.0.0 1.1.1

Updates tokio from 1.50.0 to 1.51.1

Release notes

Sourced from tokio's releases.

Tokio v1.51.1

1.51.1 (April 8th, 2026)

Fixed

  • sync: fix semaphore reopens after forget (#8021)
  • net: surface errors from SO_ERROR on recv for UDP sockets on Linux (#8001)

Fixed (unstable)

  • metrics: fix worker_local_schedule_count test (#8008)
  • rt: do not leak fd when cancelling io_uring open operation (#7983)

#7983: tokio-rs/tokio#7983 #8001: tokio-rs/tokio#8001 #8008: tokio-rs/tokio#8008 #8021: tokio-rs/tokio#8021

Tokio v1.51.0

1.51.0 (April 3rd, 2026)

Added

  • net: implement get_peer_cred on Hurd (#7989)
  • runtime: add tokio::runtime::worker_index() (#7921)
  • runtime: add runtime name (#7924)
  • runtime: stabilize LocalRuntime (#7557)
  • wasm: add wasm32-wasip2 networking support (#7933)

Changed

  • runtime: steal tasks from the LIFO slot (#7431)

Fixed

  • docs: do not show "Available on non-loom only." doc label (#7977)
  • macros: improve overall macro hygiene (#7997)
  • sync: fix notify_waiters priority in Notify (#7996)
  • sync: fix panic in Chan::recv_many when called with non-empty vector on closed channel (#7991)

#7431: tokio-rs/tokio#7431 #7557: tokio-rs/tokio#7557 #7921: tokio-rs/tokio#7921 #7924: tokio-rs/tokio#7924 #7933: tokio-rs/tokio#7933 #7977: tokio-rs/tokio#7977 #7989: tokio-rs/tokio#7989 #7991: tokio-rs/tokio#7991 #7996: tokio-rs/tokio#7996 #7997: tokio-rs/tokio#7997

Commits
  • 98df02d chore: prepare Tokio v1.51.1 (#8023)
  • 3ea11e2 sync: fix semaphore reopens after forget (#8021)
  • c791213 rt: do not leak fd when cancelling io_uring open operation (#7983)
  • ad8c59a net: surface errors from SO_ERROR on recv for UDP sockets on Linux (#8001)
  • 654d38b metrics: fix worker_local_schedule_count test (#8008)
  • 857ba80 docs: improve contributing docs on how to specify crates dependency versions ...
  • 95b9342 chore: remove path deps for tokio-macros 2.7.0 (#8007)
  • 0af06b7 chore: prepare Tokio v1.51.0 (#8005)
  • 01a7f1d chore: prepare tokio-macros v2.7.0 (#8004)
  • eeb55c7 runtime: steal tasks from the LIFO slot (#7431)
  • Additional commits viewable in compare view

Updates uuid from 1.22.0 to 1.23.0

Release notes

Sourced from uuid's releases.

v1.23.0

What's Changed

New Contributors

Special thanks

@​meng-xu-cs raised a series of bugs against the timestamp logic in uuid using automated tooling. The issues themselves were reasonably and responsibly presented and the end result is a better uuid library for everyone. Thanks!

Deprecations

This release includes the following deprecations:

  • Context: Renamed to ContextV1
  • Timestamp::from_gregorian: Renamed to Timestamp::from_gregorian_time

Change to Version::Max

Version::Max's u8 representation has changed from 0xff to 0x0f to match the value returned by Uuid::get_version_num.

Change to Uuid::get_version for the max UUID

Uuid::get_version will only return Some(Version::Max) if the UUID is actually the max UUID (all bytes are 0xff). Previously it would return Some if only the version field was 0x0f. This change matches the behaviour of the nil UUID, which only returns Some(Version::Nil) if the UUID is the nil UUID (all bytes are 0x00).

Full Changelog: uuid-rs/uuid@v1.22.0...v1.23.0

Commits
  • 00ab922 Merge pull request #876 from uuid-rs/cargo/v1.23.0
  • 726ba45 prepare for 1.23.0 release
  • 996dade Merge pull request #875 from uuid-rs/fix/context-ordering
  • e140479 simplify a use stmt
  • 8ed9142 reorganize and document more v7 context internals
  • e09a322 use LazyLock to synchronize v1/v6 context initialization
  • 0f260cc Merge pull request #874 from uuid-rs/chore/impl-cleanups
  • 1419e91 clean up and refactor main lib tests
  • ceeaf4b ensure we don't overflow on counters less than 12
  • 63bc8f5 Merge pull request #873 from uuid-rs/fix/error-msg
  • Additional commits viewable in compare view

Updates rand from 0.10.0 to 0.10.1

Changelog

Sourced from rand's changelog.

[0.10.1] — 2026-02-11

This release includes a fix for a soundness bug; see #1763.

Changes

  • Document panic behavior of make_rng and add #[track_caller] (#1761)
  • Deprecate feature log (#1763)

#1761: rust-random/rand#1761 #1763: rust-random/rand#1763

Commits

Updates indexmap from 2.13.0 to 2.14.0

Changelog

Sourced from indexmap's changelog.

2.14.0 (2026-04-09)

  • MSRV: Rust 1.85.0 or later is now required.
  • Updated the hashbrown dependency to 0.17.
  • Made more map::Slice methods const: new_mut, first_mut, last_mut, split_at_mut, split_at_mut_checked, split_first_mut, split_last_mut

2.13.1 (2026-04-02)

  • Made some Slice methods const:
    • map::Slice::{first,last,split_at,split_at_checked,split_first,split_last}
    • set::Slice::{first,last,split_at,split_at_checked,split_first,split_last}
Commits
  • bcd165b Merge pull request #439 from cuviper/release-2.14.0
  • 4ef06a7 Release 2.14.0
  • d21826c Merge pull request #438 from cuviper/hashbrown-0.17
  • 2566bec Upgrade to hashbrown v0.17
  • 4b62776 Merge pull request #437 from cuviper/disjoint-panic
  • 478fba2 Normalize the panic doc of get_disjoint_mut
  • fb6dafd Merge pull request #436 from cuviper/const-slice-mut
  • 5c237a2 Make Slice::{first,last,split_*}_mut methods const
  • 48ff9ce Merge pull request #435 from cuviper/edition-2024
  • 648be98 cargo fmt with edition 2024
  • Additional commits viewable in compare view

Updates apalis-postgres from 1.0.0-rc.6 to 1.0.0-rc.7

Release notes

Sourced from apalis-postgres's releases.

v1.0.0-rc.7

What's Changed

Full Changelog: apalis-dev/apalis-postgres@v1.0.0-rc.6...v1.0.0-rc.7

Changelog

Sourced from apalis-postgres's changelog.

[1.0.0-rc.7] - 2026-04-09

  • bump: introducing rc.7
Commits

Updates apalis from 1.0.0-rc.6 to 1.0.0-rc.7

Release notes

Sourced from apalis's releases.

v1.0.0-rc.7

What's Changed

Full Changelog: apalis-dev/apalis@v1.0.0-rc.6...v1.0.0-rc.7

Commits

Updates apalis-cron from 1.0.0-rc.6 to 1.0.0-rc.7

Release notes

Sourced from apalis-cron's releases.

v1.0.0-rc.7

What's Changed

Full Changelog: apalis-dev/apalis-cron@v1.0.0-rc.6...v1.0.0-rc.7

Changelog

Sourced from apalis-cron's changelog.

[1.0.0-rc.7] - 2026-04-08

  • deps(deps): bump cron from 0.15.0 to 0.16.0 (#46)
Commits

Updates moka from 0.12.14 to 0.12.15

Release notes

Sourced from moka's releases.

Moka 0.12.15

Version 0.12.15

Fixed

  • Fixed a bug where re-inserting an expired entry could cause it to lose its expiration time and remain in the cache indefinitely when using a custom Expiry policy with per-entry expiration. (#582gh-pull-0582 by @​jiangzhe, #581gh-pull-0581 by @​atrocities, reported in #575gh-issue-0575):
    • This occurred when an entry that had expired but not yet been evicted was re-inserted, and expire_after_update returned None. This primarily affected users who only override expire_after_create, since the default expire_after_update returns duration_until_expiry, which is None for expired entries.
    • This bug was introduced by the changes in v0.12.13 (#549gh-pull-0549 and #564gh-pull-0564).
    • Subtle behavior change:
      • Before this fix, re-inserting an expired entry was treated as an update, so Expiry::expire_after_update was called.
      • After this fix, re-inserting an expired entry is treated as a creation, so Expiry::expire_after_create is called instead.
      • This may change the expiration time of re-inserted entries, depending on your Expiry trait implementation.
  • Fixed flaky tests cht::segment::tests::drop_many_values and drop_many_values_concurrent that were failing on high-core-count machines (#586gh-pull-0586):
    • These tests were using a CPU-dependent segment count, causing inconsistent bucket array shrinking behavior of the internal segmented hash map across different machines.
    • Changed these tests to use a fixed segment count (4) for consistent results.

Changed

  • Disabled flaky GC-dependent tests by default using run_flaky_tests cfg (#584gh-pull-0584):
    • These tests rely on epoch-based garbage collection (crossbeam-epoch) timing that is not guaranteed, causing intermittent failures.
    • Fixed #539gh-issue-0539 and #580gh-issue-0580.
    • To run these tests, set RUSTFLAGS='--cfg run_flaky_tests'.
Changelog

Sourced from moka's changelog.

Version 0.12.15

Fixed

  • Fixed a bug where re-inserting an expired entry could cause it to lose its expiration time and remain in the cache indefinitely when using a custom Expiry policy with per-entry expiration. (#582[gh-pull-0582] by [@​jiangzhe][gh-jiangzhe], #581[gh-pull-0581] by [@​atrocities][gh-atrocities], reported in #575[gh-issue-0575]):
    • This occurred when an entry that had expired but not yet been evicted was re-inserted, and expire_after_update returned None. This primarily affected users who only override expire_after_create, since the default expire_after_update returns duration_until_expiry, which is None for expired entries.
    • This bug was introduced by the changes in v0.12.13 (#549[gh-pull-0549] and #564[gh-pull-0564]).
    • Subtle behavior change:
      • Before this fix, re-inserting an expired entry was treated as an update, so Expiry::expire_after_update was called.
      • After this fix, re-inserting an expired entry is treated as a creation, so Expiry::expire_after_create is called instead.
      • This may change the expiration time of re-inserted entries, depending on your Expiry trait implementation.
  • Fixed flaky tests cht::segment::tests::drop_many_values and drop_many_values_concurrent that were failing on high-core-count machines (#586[gh-pull-0586]):
    • These tests were using a CPU-dependent segment count, causing inconsistent bucket array shrinking behavior of the internal segmented hash map across different machines.
    • Changed these tests to use a fixed segment count (4) for consistent results.

Changed

  • Disabled flaky GC-dependent tests by default using run_flaky_tests cfg (#584[gh-pull-0584]):
    • These tests rely on epoch-based garbage collection (crossbeam-epoch) timing that is not guaranteed, causing intermittent failures.
    • Fixed #539[gh-issue-0539] and #580[gh-issue-0580].
    • To run these tests, set RUSTFLAGS='--cfg run_flaky_tests'.
Commits
  • 616473e Merge pull request #586 from moka-rs/fix-flaky-cht-test-on-many-core-machines
  • caf8c82 Apply cargo fmt
  • 65ff433 Fix flaky test cht::segment::tests::drop_many_values on many-core machines
  • fd103ad Update the change log for PR #586
  • 5baf38c Fix flaky test cht::segment::tests::drop_many_values_concurrent
  • 4b709c8 Merge pull request #585 from moka-rs/chore/prepare-v0.12.15
  • 9e7c73b Remove an unused link from the change log
  • fa14f78 Bump the version to v0.12.15
  • 98968b3 Update the change log for v0.12.15
  • 4c37fd4 Merge pull request #584 from moka-rs/chore/disable-flaky-tests-by-default
  • Additional commits viewable in compare view

Updates serde_qs from 1.0.0 to 1.1.1

Release notes

Sourced from serde_qs's releases.

v1.1.1

Other

  • Cargo feature / dependency cleanup (#165)

v1.1.0

Added

  • add DuplicateKeyBehavior config option (#162)
Changelog

Sourced from serde_qs's changelog.

1.1.1 - 2026-04-05

Other

  • Cargo feature / dependency cleanup (#165)

1.1.0 - 2026-03-21

Added

  • add DuplicateKeyBehavior config option (#162)
Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
deps(deps): bump the rust-runtime group across 1 directory with 9 upd…
5a7ca2f 
…ates

Bumps the rust-runtime group with 9 updates in the /rustytime directory:

| Package | From | To |
| --- | --- | --- |
| [tokio](https://github.com/tokio-rs/tokio) | `1.50.0` | `1.51.1` |
| [uuid](https://github.com/uuid-rs/uuid) | `1.22.0` | `1.23.0` |
| [rand](https://github.com/rust-random/rand) | `0.10.0` | `0.10.1` |
| [indexmap](https://github.com/indexmap-rs/indexmap) | `2.13.0` | `2.14.0` |
| [apalis-postgres](https://github.com/apalis-dev/apalis-postgres) | `1.0.0-rc.6` | `1.0.0-rc.7` |
| [apalis](https://github.com/apalis-dev/apalis) | `1.0.0-rc.6` | `1.0.0-rc.7` |
| [apalis-cron](https://github.com/apalis-dev/apalis-cron) | `1.0.0-rc.6` | `1.0.0-rc.7` |
| [moka](https://github.com/moka-rs/moka) | `0.12.14` | `0.12.15` |
| [serde_qs](https://github.com/samscott89/serde_qs) | `1.0.0` | `1.1.1` |



Updates `tokio` from 1.50.0 to 1.51.1
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](tokio-rs/tokio@tokio-1.50.0...tokio-1.51.1)

Updates `uuid` from 1.22.0 to 1.23.0
- [Release notes](https://github.com/uuid-rs/uuid/releases)
- [Commits](uuid-rs/uuid@v1.22.0...v1.23.0)

Updates `rand` from 0.10.0 to 0.10.1
- [Release notes](https://github.com/rust-random/rand/releases)
- [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md)
- [Commits](rust-random/rand@0.10.0...0.10.1)

Updates `indexmap` from 2.13.0 to 2.14.0
- [Changelog](https://github.com/indexmap-rs/indexmap/blob/main/RELEASES.md)
- [Commits](indexmap-rs/indexmap@2.13.0...2.14.0)

Updates `apalis-postgres` from 1.0.0-rc.6 to 1.0.0-rc.7
- [Release notes](https://github.com/apalis-dev/apalis-postgres/releases)
- [Changelog](https://github.com/apalis-dev/apalis-postgres/blob/main/CHANGELOG.md)
- [Commits](apalis-dev/apalis-postgres@v1.0.0-rc.6...v1.0.0-rc.7)

Updates `apalis` from 1.0.0-rc.6 to 1.0.0-rc.7
- [Release notes](https://github.com/apalis-dev/apalis/releases)
- [Changelog](https://github.com/apalis-dev/apalis/blob/main/CHANGELOG.md)
- [Commits](apalis-dev/apalis@v1.0.0-rc.6...v1.0.0-rc.7)

Updates `apalis-cron` from 1.0.0-rc.6 to 1.0.0-rc.7
- [Release notes](https://github.com/apalis-dev/apalis-cron/releases)
- [Changelog](https://github.com/apalis-dev/apalis-cron/blob/main/CHANGELOG.md)
- [Commits](apalis-dev/apalis-cron@v1.0.0-rc.6...v1.0.0-rc.7)

Updates `moka` from 0.12.14 to 0.12.15
- [Release notes](https://github.com/moka-rs/moka/releases)
- [Changelog](https://github.com/moka-rs/moka/blob/main/CHANGELOG.md)
- [Commits](moka-rs/moka@v0.12.14...v0.12.15)

Updates `serde_qs` from 1.0.0 to 1.1.1
- [Release notes](https://github.com/samscott89/serde_qs/releases)
- [Changelog](https://github.com/samscott89/serde_qs/blob/main/CHANGELOG.md)
- [Commits](samscott89/serde_qs@v1.0.0...v1.1.1)

---
updated-dependencies:
- dependency-name: tokio
  dependency-version: 1.51.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-runtime
- dependency-name: uuid
  dependency-version: 1.23.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-runtime
- dependency-name: rand
  dependency-version: 0.10.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-runtime
- dependency-name: indexmap
  dependency-version: 2.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-runtime
- dependency-name: apalis-postgres
  dependency-version: 1.0.0-rc.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-runtime
- dependency-name: apalis
  dependency-version: 1.0.0-rc.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-runtime
- dependency-name: apalis-cron
  dependency-version: 1.0.0-rc.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-runtime
- dependency-name: moka
  dependency-version: 0.12.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-runtime
- dependency-name: serde_qs
  dependency-version: 1.1.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-runtime
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies rust Pull requests that update rust code labels Apr 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies rust Pull requests that update rust code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants