Skip to content

Bump the cargo group across 1 directory with 5 updates#1

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/cargo-b2132e516c
Closed

Bump the cargo group across 1 directory with 5 updates#1
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/cargo-b2132e516c

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot bot commented on behalf of github Feb 12, 2026

Bumps the cargo group with 5 updates in the / directory:

Package From To
h2 0.3.9 0.3.12
mio 0.8.2 0.8.11
tokio 1.17.0 1.26.0
time 0.3.9 0.3.26
axum-core 0.2.3 0.2.4

Updates h2 from 0.3.9 to 0.3.12

Release notes

Sourced from h2's releases.

v0.3.12

  • Avoid time operations that can panic (#599)
  • Bump MSRV to Rust 1.49 (#606)
  • Fix header decoding error when a header name is contained at a continuation header boundary (#589)
  • Remove I/O type names from handshake tracing spans (#608)

New Contributors

v0.3.11

  • Fix SendStream::poll_capacity to never return Ok(Some(0)) (#596)
  • Fix panic when receiving already reset push promise (#597)

v0.3.10

  • Add Error::is_go_away() and Error::is_remote() methods.
  • Fix panic if receiving malformed PUSH_PROMISE with stream ID of 0.
Changelog

Sourced from h2's changelog.

0.3.12 (March 9, 2022)

  • Avoid time operations that can panic (#599)
  • Bump MSRV to Rust 1.49 (#606)
  • Fix header decoding error when a header name is contained at a continuation header boundary (#589)
  • Remove I/O type names from handshake tracing spans (#608)

0.3.11 (January 26, 2022)

  • Make SendStream::poll_capacity never return Ok(Some(0)) (#596)
  • Fix panic when receiving already reset push promise (#597)

0.3.10 (January 6, 2022)

  • Add Error::is_go_away() and Error::is_remote() methods.
  • Fix panic if receiving malformed PUSH_PROMISE with stream ID of 0.
Commits
  • 3383ef7 v0.3.12
  • b8eab38 tracing: remove I/O type names from handshake spans (#608)
  • 85549fc fix header parsing: consume buf only if header name and value are both decoded
  • 7bb1462 Bump MSRV to 1.49, since Tokio uses it
  • 4c31a32 Upgrade dev-dependencies
  • 47e9f62 There's no such thing as HTTP/2.0
  • 4dc2b4a Avoid time operations that can panic
  • b0d01bb v0.3.11
  • 556447c Make use of NLL to clean up handshaking logic (#576)
  • 7de2ccc fix panic when receiving already reset push promise (#597)
  • Additional commits viewable in compare view

Updates mio from 0.8.2 to 0.8.11

Changelog

Sourced from mio's changelog.

0.8.11

0.8.10

Added

0.8.9

Added

Fixed

0.8.8

Fixed

0.8.7

Added

  • Add/fix support for tvOS and watchOS, Mio should now build for tvOS and

... (truncated)

Commits

Updates tokio from 1.17.0 to 1.26.0

Release notes

Sourced from tokio's releases.

Tokio v1.26.0

Fixed

Added

Changed

Internal Changes

Unstable

Documented

... (truncated)

Commits

Updates time from 0.3.9 to 0.3.26

Release notes

Sourced from time's releases.

v0.3.26

See the changelog for details.

v0.3.25

See the changelog for details.

v0.3.24

See the changelog for details.

v0.3.23

See the changelog for details.

v0.3.22

See the changelog for details.

v0.3.21

See the changelog for details.

v0.3.20

See the changelog for details.

v0.3.19

See the changelog for details.

v0.3.18

See the changelog for details.

v0.3.17

See the changelog for details.

v0.3.16

See the changelog for details.

v0.3.15

See the changelog for details.

v0.3.14

See the changelog for details.

v0.3.13

See the changelog for details.

v0.3.12

See the changelog for details.

v0.3.11

See the changelog for details.

v0.3.10

See the changelog for details.

Changelog

Sourced from time's changelog.

0.3.26 [2023-08-18]

This release contains only a single change. serde is required to be a version prior to 1.0.171. This is due to the decision by the maintainer of serde to include pre-built binaries that are executed without the end user's knowledge. As of the time of publishing, the included binary has not even been reproduced. This is a security risk, and the time project strongly opposes this decision. While this may break some users' builds due to conflicting versions, it is a necessary step to ensure the security.

0.3.25 [2023-08-02]

Fixed

  • Methods such as Time::replace_milliseconds would panic on some out-of-range values. This has been fixed.

0.3.24 [2023-07-30]

Added

  • The subsecond component is taken into account when parsing the unix_timestamp component. If data is conflicting, the subsecond value takes precedence.
  • Parsing a Time with only the hour component is now supported. The minute and second, and subsecond components are assumed to be zero.

Changed

  • The minimum supported Rust version is now 1.67.0.
  • The debug output for Parsed has been improved.
  • When parsing, invalid values are now rejected sooner. Previously, the entire input would be parsed before being rejected in the final step. Now, invalid values are rejected as soon as they are encountered. This affects the error variant returned, which may cause minor breakage for any code (incorrectly) relying on the exact error variant.
  • When parsing a Time, an error is returned if components are present but not consecutive. For example, if hours and seconds are present, minutes will not be assumed to be zero.

Fixed

  • The implementation of Duration::checked_div could return a slightly incorrect result in some cases. This has been fixed.

0.3.23 [2023-07-08]

Added

  • Date::next_occurrence
  • Date::prev_occurrence
  • Date::nth_next_occurrence
  • Date::nth_prev_occurrence
  • Weekday::nth_prev

... (truncated)

Commits
  • 500f8e4 Remove support for serde with pre-built binaries
  • a98fe2d v0.3.25 release
  • b74ebe8 Use new feature of deranged
  • d671910 Avoid panicking on out-of-range value
  • cdc85da v0.3.24 release
  • 227b6f8 Gate methods as necessary
  • 8060100 Fix implementation of Duration::checked_div
  • a9fea9f Use ranged integers internally for Duration
  • 04936ee Use ensure_ranged! for UtcOffset
  • 7e95cb2 Use ranged integers internally for Time
  • Additional commits viewable in compare view

Updates axum-core from 0.2.3 to 0.2.4

Commits
  • 5be73c1 axum-core: Version 0.2.4 (#984)
  • 8dd6070 Implement `IntoResponse for (Parts | Request<()>, $(impl IntoResponseParts)+,...
  • 1fe4558 Move examples to separate workspace (#978)
  • 6e18350 Implement IntoResponse for Response\<()> and response::Parts (#950)
  • 5bb924b Implement IntoResponse and IntoResponseParts for http::Extensions (#975)
  • d606728 ecosystem: Add CLOMonitor to project showcase (#976)
  • a3b6cbc axum-extra: Version 0.3.0 (#974)
  • 7006179 Move private and signed cookies behind feature flags (#949)
  • a723ed1 axum: Version 0.5.4 (#973)
  • See full diff in compare view

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
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Note

Medium Risk
Dependency-only change, but it upgrades core runtime/networking crates (tokio, mio, h2, time) which can subtly affect scheduling, IO behavior, and platform-specific builds.

Overview
Bumps the async/runtime stack by upgrading tokio to 1.26 (from 1.17) and refreshing the resolved dependency tree in Cargo.lock (lockfile format v4).

Pulls in newer versions of key transitive crates like h2, mio, time (including new time-core/deranged deps), and Windows support crates (windows-sys/windows-targets), and removes some previously-resolved packages (e.g., miow, ntapi, num_threads, and a kaspaxilinx lock entry).

Written by Cursor Bugbot for commit 6d90865. This will update automatically on new commits. Configure here.

Bumps the cargo group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [h2](https://github.com/hyperium/h2) | `0.3.9` | `0.3.12` |
| [mio](https://github.com/tokio-rs/mio) | `0.8.2` | `0.8.11` |
| [tokio](https://github.com/tokio-rs/tokio) | `1.17.0` | `1.26.0` |
| [time](https://github.com/time-rs/time) | `0.3.9` | `0.3.26` |
| [axum-core](https://github.com/tokio-rs/axum) | `0.2.3` | `0.2.4` |



Updates `h2` from 0.3.9 to 0.3.12
- [Release notes](https://github.com/hyperium/h2/releases)
- [Changelog](https://github.com/hyperium/h2/blob/master/CHANGELOG.md)
- [Commits](hyperium/h2@v0.3.9...v0.3.12)

Updates `mio` from 0.8.2 to 0.8.11
- [Release notes](https://github.com/tokio-rs/mio/releases)
- [Changelog](https://github.com/tokio-rs/mio/blob/master/CHANGELOG.md)
- [Commits](tokio-rs/mio@v0.8.2...v0.8.11)

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

Updates `time` from 0.3.9 to 0.3.26
- [Release notes](https://github.com/time-rs/time/releases)
- [Changelog](https://github.com/time-rs/time/blob/main/CHANGELOG.md)
- [Commits](time-rs/time@v0.3.9...v0.3.26)

Updates `axum-core` from 0.2.3 to 0.2.4
- [Release notes](https://github.com/tokio-rs/axum/releases)
- [Changelog](https://github.com/tokio-rs/axum/blob/main/CHANGELOG.md)
- [Commits](tokio-rs/axum@axum-core-v0.2.3...axum-core-v0.2.4)

---
updated-dependencies:
- dependency-name: h2
  dependency-version: 0.3.12
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: mio
  dependency-version: 0.8.11
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: tokio
  dependency-version: 1.26.0
  dependency-type: direct:production
  dependency-group: cargo
- dependency-name: time
  dependency-version: 0.3.26
  dependency-type: direct:production
  dependency-group: cargo
- dependency-name: axum-core
  dependency-version: 0.2.4
  dependency-type: indirect
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Feb 12, 2026
Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

"libc",
"num_threads",
"serde",
"time-core",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

time 0.3.26 adds controversial serde version ceiling

Medium Severity

The time crate is pinned to version 0.3.26, which is the notorious release that added serde as a non-optional dependency with a hard upper bound of < 1.0.171. This was a controversial protest against serde's pre-built binaries and was reverted in later time versions (0.3.28+). Despite the project only requesting formatting and macros features, serde now appears unconditionally in time's dependency list, introducing a workspace-wide version ceiling that blocks any future serde upgrade past 1.0.170 and could cause dependency resolution failures with other crates needing newer serde.

Fix in Cursor Fix in Web

@dependabot @github
Copy link
Copy Markdown
Author

dependabot bot commented on behalf of github Feb 20, 2026

Superseded by #2.

@dependabot dependabot bot closed this Feb 20, 2026
@dependabot dependabot bot deleted the dependabot/cargo/cargo-b2132e516c branch February 20, 2026 11:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants