Skip to content

deps(cargo): bump the cargo-patch group across 2 directories with 4 updates - #35

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/crates/cargo-patch-6776afae03
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/crates/cargo-patch-6776afae03

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 9, 2026 •

Copy link
Copy Markdown

Bumps the cargo-patch group with 4 updates in the /crates directory: hyper-util, serde_json, sha2 and thiserror.
Bumps the cargo-patch group with 4 updates in the /crates/desktop directory: hyper-util, serde_json, sha2 and thiserror.

Updates hyper-util from 0.1.20 to 0.1.21

Release notes

Sourced from hyper-util's releases.

v0.1.21

Additions

  • Add crate-level documentation. (#327)
  • Add client::legacy::Builder::http2_header_table_size() method. (#274)
  • Add client::legacy::Builder::http2_max_concurrent_streams() method. (#274)
  • Add client::legacy::Builder::http2_max_local_error_reset_streams() method. (#277)
  • Add client::legacy::connect::HttpConnector::set_mark() method. (#303)
  • Add rt::tracing::WithSpanExecutor<E>, hyper_util::rt::tracing::CurrentSpanExecutor<E>, and hyper_util::rt::tracing::MkSpanExecutor<E, F> executors. (#323)

Fixes

  • Fix client::legacy::Client so that it properly validates CONNECT responses. (#315)
  • Fix client::legacy::Client to cancel the idle interval once its pool empties. (#292)
  • Fix client::legacy::Client to properly handle IPv6 addresses when using a SOCKS proxy. (#302)
  • Fix client::pool::cache to preserve readiness with clones. (#297)
  • Fix client::pool::cache to wake its waiters in FIFO order. (#298)
  • Fix client::pool::singleton::Singleton to properly handle cancellation. (#299)
  • Fix client::pool::singleton::Singleton to share errors with all waiters. (#296)
  • Fix client::proxy::matcher handling for IP wildcards. (#309)
  • The tokio/net feature is narrowed to the client-legacy feature flag, from the client feature flag. (#276)
  • Various fixes to the client::legacy::Client's SOCKS proxying. (#302) (#307) (#308) (#310)

Changes

This release contains a minor behavioral change for users of the tracing feature flag to be aware of.

This feature flag was introduced in v0.1.11. When enabled, rt::TokioExecutor<E> began propagating the currently active tracing::Span to spawned tasks when hyper::rt::Executor::execute() is called. This caused issues for some users, due to background tasks keeping a span open for the duration of a long-lived connection.

This behavior has now been removed from rt::TokioExecutor<E> (#322) by default. A collection of executor wrappers have been added to a new rt::tracing submodule, to provide facilities for instrumenting a client or server's spawned tasks. See the module-level documentation of rt::tracing for more information.

To temporarily preserve the previous rt::TokioExecutor<E> span propagation behavior, enable the rt-tracing-exec-force feature. Note that this feature flag will be removed in a future release.

This release bumps the minimal supported Rust version (MSRV) from 1.64 to 1.85.

This release bumps the rust edition from 2021 to 2024.

... (truncated)

Changelog

Sourced from hyper-util's changelog.

0.1.21 (2026-09-24)

This release bumps the minimal supported Rust version (MSRV) from 1.64 to 1.85.

This release bumps the rust edition from 2021 to 2024.

Additions

  • Add crate-level documentation. (#327)
  • Add client::legacy::Builder::http2_header_table_size() method. (#274)
  • Add client::legacy::Builder::http2_max_concurrent_streams() method. (#274)
  • Add client::legacy::Builder::http2_max_local_error_reset_streams() method. (#277)
  • Add client::legacy::connect::HttpConnector::set_mark() method. (#303)
  • Add rt::tracing::WithSpanExecutor<E>, hyper_util::rt::tracing::CurrentSpanExecutor<E>, and hyper_util::rt::tracing::MkSpanExecutor<E, F> executors. (#323)

Fixes

  • Fix client::legacy::Client so that it properly validates CONNECT responses. (#315)
  • Fix client::legacy::Client to cancel the idle interval once its pool empties. (#292)
  • Fix client::legacy::Client to properly handle IPv6 addresses when using a SOCKS proxy. (#302)
  • Fix client::pool::cache to preserve readiness with clones. (#297)
  • Fix client::pool::cache to wake its waiters in FIFO order. (#298)
  • Fix client::pool::singleton::Singleton to properly handle cancellation. (#299)
  • Fix client::pool::singleton::Singleton to share errors with all waiters. (#296)
  • Fix client::proxy::matcher handling for IP wildcards. (#309)
  • The tokio/net feature is narrowed to the client-legacy feature flag, from the client feature flag. (#276)
  • Various fixes to the client::legacy::Client's SOCKS proxying. (#302) (#307) (#308) (#310)

Changes

This release contains a minor behavioral change for users of the tracing feature flag to be aware of.

This feature flag was introduced in v0.1.11. When enabled, rt::TokioExecutor<E> began propagating the currently active tracing::Span to spawned tasks when hyper::rt::Executor::execute() is called. This caused issues for some users, due to background tasks keeping a span open for the duration of a long-lived connection.

This behavior has now been removed from rt::TokioExecutor<E> (#322) by default. A collection of executor wrappers have been added to a new rt::tracing submodule, to provide facilities for instrumenting a client or server's spawned tasks. See the module-level documentation of rt::tracing for more information.

To temporarily preserve the previous rt::TokioExecutor<E> span propagation behavior, enable the rt-tracing-exec-force feature. Note that this feature flag will be removed in a future release.

Commits
  • 23a8689 v0.1.21
  • cdb2346 doc(client/pool): add broken_intra_doc_links allowance (#326)
  • 13b6110 chore(error): remove disabled hyper_util::error submodule (#325)
  • b9ee451 docs(lib): add crate-level documentation (#327)
  • d6b7d7e feat(rt/tracing): introduce tracing executors (#323)
  • f2da915 feat(client): add HttpConnector::set_mark for SO_MARK (#303)
  • 4dbd494 feat(rt): change TokioExecutor to not trace, add rt-tracing-exec-force feat...
  • d480d9f fix(client): parse proxy CONNECT response with httparse (#315)
  • 7e0958b chore(ci): simplify msrv check (#317)
  • 0734568 chore(ci): update to actions/checkout@v7 (#316)
  • Additional commits viewable in compare view

Updates serde_json from 1.0.151 to 1.0.154

Release notes

Sourced from serde_json's releases.

v1.0.154

v1.0.153

v1.0.152

Commits
  • 20572a6 Release 1.0.154
  • a91bfaf Fix RandomState links in map documentation
  • 3c932c0 Merge pull request #1333 from razmser/no-std-preserve-order
  • 4b2d726 Release 1.0.153
  • 83335ee Touch up PR 1345
  • 4b4810a Resolve range_plus_one pedantic clippy lint
  • 8af71cc Merge pull request #1345 from 00200200/fix-invalid-utf8-error-column
  • 452afa2 Correct multiline raw UTF-8 error positions and simplify indexing
  • c9f1e3b Release 1.0.152
  • 854fc70 Touch up PR 1347
  • Additional commits viewable in compare view

Updates sha2 from 0.11.0 to 0.11.1

Commits

Updates thiserror from 2.0.20 to 2.0.21

Release notes

Sourced from thiserror's releases.

2.0.21

  • Fix parsing of generic unit variants in display expressions (#459)
Commits
  • b1827ee Release 2.0.21
  • 58037b5 Merge pull request #459 from dtolnay/turbofish
  • f82a0cf Keep track of nested turbofish depth
  • 72ea492 Raise required compiler to Rust 1.77
  • 72eea0d Resolve io_other_error clippy lint in tests
  • 07f09a2 Raise required compiler to Rust 1.74
  • 2715388 Update ui test suite to nightly-2026-09-22
  • 5a306c7 Update ui test suite to nightly-2026-09-05
  • ef9383b Update ui test suite to nightly-2026-08-22
  • 8336b84 Update ui tests for version 2.0.20
  • See full diff in compare view

Updates serde_json from 1.0.151 to 1.0.154

Release notes

Sourced from serde_json's releases.

v1.0.154

v1.0.153

v1.0.152

Commits
  • 20572a6 Release 1.0.154
  • a91bfaf Fix RandomState links in map documentation
  • 3c932c0 Merge pull request #1333 from razmser/no-std-preserve-order
  • 4b2d726 Release 1.0.153
  • 83335ee Touch up PR 1345
  • 4b4810a Resolve range_plus_one pedantic clippy lint
  • 8af71cc Merge pull request #1345 from 00200200/fix-invalid-utf8-error-column
  • 452afa2 Correct multiline raw UTF-8 error positions and simplify indexing
  • c9f1e3b Release 1.0.152
  • 854fc70 Touch up PR 1347
  • Additional commits viewable in compare view

Updates hyper-util from 0.1.20 to 0.1.21

Release notes

Sourced from hyper-util's releases.

v0.1.21

Additions

  • Add crate-level documentation. (#327)
  • Add client::legacy::Builder::http2_header_table_size() method. (#274)
  • Add client::legacy::Builder::http2_max_concurrent_streams() method. (#274)
  • Add client::legacy::Builder::http2_max_local_error_reset_streams() method. (#277)
  • Add client::legacy::connect::HttpConnector::set_mark() method. (#303)
  • Add rt::tracing::WithSpanExecutor<E>, hyper_util::rt::tracing::CurrentSpanExecutor<E>, and hyper_util::rt::tracing::MkSpanExecutor<E, F> executors. (#323)

Fixes

  • Fix client::legacy::Client so that it properly validates CONNECT responses. (#315)
  • Fix client::legacy::Client to cancel the idle interval once its pool empties. (#292)
  • Fix client::legacy::Client to properly handle IPv6 addresses when using a SOCKS proxy. (#302)
  • Fix client::pool::cache to preserve readiness with clones. (#297)
  • Fix client::pool::cache to wake its waiters in FIFO order. (#298)
  • Fix client::pool::singleton::Singleton to properly handle cancellation. (#299)
  • Fix client::pool::singleton::Singleton to share errors with all waiters. (#296)
  • Fix client::proxy::matcher handling for IP wildcards. (#309)
  • The tokio/net feature is narrowed to the client-legacy feature flag, from the client feature flag. (#276)
  • Various fixes to the client::legacy::Client's SOCKS proxying. (#302) (#307) (#308) (#310)

Changes

This release contains a minor behavioral change for users of the tracing feature flag to be aware of.

This feature flag was introduced in v0.1.11. When enabled, rt::TokioExecutor<E> began propagating the currently active tracing::Span to spawned tasks when hyper::rt::Executor::execute() is called. This caused issues for some users, due to background tasks keeping a span open for the duration of a long-lived connection.

This behavior has now been removed from rt::TokioExecutor<E> (#322) by default. A collection of executor wrappers have been added to a new rt::tracing submodule, to provide facilities for instrumenting a client or server's spawned tasks. See the module-level documentation of rt::tracing for more information.

To temporarily preserve the previous rt::TokioExecutor<E> span propagation behavior, enable the rt-tracing-exec-force feature. Note that this feature flag will be removed in a future release.

This release bumps the minimal supported Rust version (MSRV) from 1.64 to 1.85.

This release bumps the rust edition from 2021 to 2024.

... (truncated)

Changelog

Sourced from hyper-util's changelog.

0.1.21 (2026-09-24)

This release bumps the minimal supported Rust version (MSRV) from 1.64 to 1.85.

This release bumps the rust edition from 2021 to 2024.

Additions

  • Add crate-level documentation. (#327)
  • Add client::legacy::Builder::http2_header_table_size() method. (#274)
  • Add client::legacy::Builder::http2_max_concurrent_streams() method. (#274)
  • Add client::legacy::Builder::http2_max_local_error_reset_streams() method. (#277)
  • Add client::legacy::connect::HttpConnector::set_mark() method. (#303)
  • Add rt::tracing::WithSpanExecutor<E>, hyper_util::rt::tracing::CurrentSpanExecutor<E>, and hyper_util::rt::tracing::MkSpanExecutor<E, F> executors. (#323)

Fixes

  • Fix client::legacy::Client so that it properly validates CONNECT responses. (#315)
  • Fix client::legacy::Client to cancel the idle interval once its pool empties. (#292)
  • Fix client::legacy::Client to properly handle IPv6 addresses when using a SOCKS proxy. (#302)
  • Fix client::pool::cache to preserve readiness with clones. (#297)
  • Fix client::pool::cache to wake its waiters in FIFO order. (#298)
  • Fix client::pool::singleton::Singleton to properly handle cancellation. (#299)
  • Fix client::pool::singleton::Singleton to share errors with all waiters. (#296)
  • Fix client::proxy::matcher handling for IP wildcards. (#309)
  • The tokio/net feature is narrowed to the client-legacy feature flag, from the client feature flag. (#276)
  • Various fixes to the client::legacy::Client's SOCKS proxying. (#302) (#307) (#308) (#310)

Changes

This release contains a minor behavioral change for users of the tracing feature flag to be aware of.

This feature flag was introduced in v0.1.11. When enabled, rt::TokioExecutor<E> began propagating the currently active tracing::Span to spawned tasks when hyper::rt::Executor::execute() is called. This caused issues for some users, due to background tasks keeping a span open for the duration of a long-lived connection.

This behavior has now been removed from rt::TokioExecutor<E> (#322) by default. A collection of executor wrappers have been added to a new rt::tracing submodule, to provide facilities for instrumenting a client or server's spawned tasks. See the module-level documentation of rt::tracing for more information.

To temporarily preserve the previous rt::TokioExecutor<E> span propagation behavior, enable the rt-tracing-exec-force feature. Note that this feature flag will be removed in a future release.

Commits
  • 23a8689 v0.1.21
  • cdb2346 doc(client/pool): add broken_intra_doc_links allowance (#326)
  • 13b6110 chore(error): remove disabled hyper_util::error submodule (#325)
  • b9ee451 docs(lib): add crate-level documentation (#327)
  • d6b7d7e feat(rt/tracing): introduce tracing executors (#323)
  • f2da915 feat(client): add HttpConnector::set_mark for SO_MARK (#303)
  • 4dbd494 feat(rt): change TokioExecutor to not trace, add rt-tracing-exec-force feat...
  • d480d9f fix(client): parse proxy CONNECT response with httparse (#315)
  • 7e0958b chore(ci): simplify msrv check (#317)
  • 0734568 chore(ci): update to actions/checkout@v7 (#316)
  • Additional commits viewable in compare view

Updates sha2 from 0.11.0 to 0.11.1

Commits

Updates thiserror from 2.0.20 to 2.0.21

Release notes

Sourced from thiserror's releases.

2.0.21

  • Fix parsing of generic unit variants in display expressions (#459)
Commits
  • b1827ee Release 2.0.21
  • 58037b5 Merge pull request #459 from dtolnay/turbofish
  • f82a0cf Keep track of nested turbofish depth
  • 72ea492 Raise required compiler to Rust 1.77
  • 72eea0d Resolve io_other_error clippy lint in tests
  • 07f09a2 Raise required compiler to Rust 1.74
  • 2715388 Update ui test suite to nightly-2026-09-22
  • 5a306c7 Update ui test suite to nightly-2026-09-05
  • ef9383b Update ui test suite to nightly-2026-08-22
  • 8336b84 Update ui tests for version 2.0.20
  • See full diff in compare view

Updates hyper-util from 0.1.20 to 0.1.21

Release notes

Sourced from hyper-util's releases.

v0.1.21

Additions

  • Add crate-level documentation. (#327)
  • Add client::legacy::Builder::http2_header_table_size() method. (#274)
  • Add client::legacy::Builder::http2_max_concurrent_streams() method. (#274)
  • Add client::legacy::Builder::http2_max_local_error_reset_streams() method. (#277)
  • Add client::legacy::connect::HttpConnector::set_mark() method. (#303)
  • Add rt::tracing::WithSpanExecutor<E>, hyper_util::rt::tracing::CurrentSpanExecutor<E>, and hyper_util::rt::tracing::MkSpanExecutor<E, F> executors. (#323)

Fixes

  • Fix client::legacy::Client so that it properly validates CONNECT responses. (#315)
  • Fix client::legacy::Client to cancel the idle interval once its pool empties. (#292)
  • Fix client::legacy::Client to properly handle IPv6 addresses when using a SOCKS proxy. (#302)
  • Fix client::pool::cache to preserve readiness with clones. (#297)
  • Fix client::pool::cache to wake its waiters in FIFO order. (#298)
  • Fix client::pool::singleton::Singleton to properly handle cancellation. (#299)
  • Fix client::pool::singleton::Singleton to share errors with all waiters. (#296)
  • Fix client::proxy::matcher handling for IP wildcards. (#309)
  • The tokio/net feature is narrowed to the client-legacy feature flag, from the client feature flag. (#276)
  • Various fixes to the client::legacy::Client's SOCKS proxying. (#302) (#307) (#308) (#310)

Changes

This release contains a minor behavioral change for users of the tracing feature flag to be aware of.

This feature flag was introduced in v0.1.11. When enabled, rt::TokioExecutor<E> began propagating the currently active tracing::Span to spawned tasks when hyper::rt::Executor::execute() is called. This caused issues for some users, due to background tasks keeping a span open for the duration of a long-lived connection.

This behavior has now been removed from rt::TokioExecutor<E> (#322) by default. A collection of executor wrappers have been added to a new rt::tracing submodule, to provide facilities for instrumenting a client or server's spawned tasks. See the module-level documentation of rt::tracing for more information.

To temporarily preserve the previous rt::TokioExecutor<E> span propagation behavior, enable the rt-tracing-exec-force feature. Note that this feature flag will be removed in a future release.

This release bumps the minimal supported Rust version (MSRV) from 1.64 to 1.85.

This release bumps the rust edition from 2021 to 2024.

... (truncated)

Changelog

Sourced from hyper-util's changelog.

0.1.21 (2026-09-24)

This release bumps the minimal supported Rust version (MSRV) from 1.64 to 1.85.

This release bumps the rust edition from 2021 to 2024.

Additions

  • Add crate-level documentation. (#327)
  • Add client::legacy::Builder::http2_header_table_size() method. (#274)
  • Add client::legacy::Builder::http2_max_concurrent_streams() method. (#274)
  • Add client::legacy::Builder::http2_max_local_error_reset_streams() method. (#277)
  • Add client::legacy::connect::HttpConnector::set_mark() method. (#303)
  • Add rt::tracing::WithSpanExecutor<E>, hyper_util::rt::tracing::CurrentSpanExecutor<E>, and hyper_util::rt::tracing::MkSpanExecutor<E, F> executors. (#323)

Fixes

  • Fix client::legacy::Client so that it properly validates CONNECT responses. (#315)
  • Fix client::legacy::Client to cancel the idle interval once its pool empties. (#292)
  • Fix client::legacy::Client to properly handle IPv6 addresses when using a SOCKS proxy. (#302)
  • Fix client::pool::cache to preserve readiness with clones. (#297)
  • Fix client::pool::cache to wake its waiters in FIFO order. (#298)
  • Fix client::pool::singleton::Singleton to properly handle cancellation. (#299)
  • Fix client::pool::singleton::Singleton to share errors with all waiters. (#296)
  • Fix client::proxy::matcher handling for IP wildcards. (#309)
  • The tokio/net feature is narrowed to the client-legacy feature flag, from the client feature flag. (#276)
  • Various fixes to the client::legacy::Client's SOCKS proxying. (#302) (#307) (#308) (#310)

Changes

This release contains a minor behavioral change for users of the tracing feature flag to be aware of.

This feature flag was introduced in v0.1.11. When enabled, rt::TokioExecutor<E> began propagating the currently active tracing::Span to spawned tasks when hyper::rt::Executor::execute() is called. This caused issues for some users, due to background tasks keeping a span open for the duration of a long-lived connection.

This behavior has now been removed from rt::TokioExecutor<E> (#322) by default. A collection of executor wrappers have been added to a new rt::tracing submodule, to provide facilities for instrumenting a client or server's spawned tasks. See the module-level documentation of rt::tracing for more information.

To temporarily preserve the previous rt::TokioExecutor<E> span propagation behavior, enable the rt-tracing-exec-force feature. Note that this feature flag will be removed in a future release.

Commits
  • 23a8689 v0.1.21
  • cdb2346 doc(client/pool): add broken_intra_doc_links allowance (#326)
  • 13b6110 chore(error): remove disabled hyper_util::error submodule (#325)
  • b9ee451 docs(lib): add crate-level documentation (#327)
  • d6b7d7e feat(rt/tracing): introduce tracing executors (#323)
  • f2da915 feat(client): add HttpConnector::set_mark for SO_MARK (#303)
  • 4dbd494 feat(rt): change TokioExecutor to not trace, add rt-tracing-exec-force feat...
  • d480d9f fix(client): parse proxy CONNECT response with httparse (#315)
  • 7e0958b chore(ci): simplify msrv check (#317)
  • 0734568 chore(ci): update to actions/checkout@v7 (#316)
  • Additional commits viewable in compare view

Updates serde_json from 1.0.151 to 1.0.154

Release notes

Sourced from serde_json's releases.

v1.0.154

v1.0.153

v1.0.152

Commits
  • 20572a6 Release 1.0.154
  • a91bfaf Fix RandomState links in map documentation
  • 3c932c0 Merge pull request #1333 from razmser/no-std-preserve-order
  • 4b2d726 Release 1.0.153
  • 83335ee Touch up PR 1345
  • 4b4810a Resolve range_plus_one pedantic clippy lint
  • 8af71cc Merge pull request #1345 from 00200200/fix-invalid-utf8-error-column
  • 452afa2 Correct multiline raw UTF-8 error positions and simplify indexing
  • c9f1e3b Release 1.0.152
  • 854fc70 Touch up PR 1347
  • Additional commits viewable in compare view

Updates sha2 from 0.11.0 to 0.11.1

Commits

Updates thiserror from 2.0.20 to 2.0.21

Release notes

Sourced from thiserror's releases.

2.0.21

  • Fix parsing of generic unit variants in display expressions (#459)
Commits
  • b1827ee Release 2.0.21
  • 58037b5 Merge pull request #459 from dtolnay/turbofish
  • f82a0cf Keep track of nested turbofish depth
  • 72ea492 Raise required compiler to Rust 1.77
  • 72eea0d Resolve io_other_error clippy lint in tests
  • 07f09a2 Raise required compiler to Rust 1.74
  • 2715388 Update ui test suite to nightly-2026-09-22
  • 5a306c7 Update ui test suite to nightly-2026-09-05
  • ef9383b Update ui test suite to nightly-2026-08-22
  • 8336b84 Update ui tests for version 2.0.20
  • See full diff in compare view

Updates serde_json from 1.0.151 to 1.0.154

Release notes

Sourced from serde_json's releases.

v1.0.154

v1.0.153

v1.0.152

Commits
  • 20572a6 Release 1.0.154
  • a91bfaf Fix RandomState links in map documentation
  • 3c932c0 Merge pull request #1333 from razmser/no-std-preserve-order
  • 4b2d726 Release 1.0.153
  • 83335ee Touch up PR 1345
  • 4b4810a Resolve range_plus_one pedantic clippy lint
  • 8af71cc Merge pull request #1345 from 00200200/fix-invalid-utf8-error-column
  • 452afa2 Correct multiline raw UTF-8 error positions and simplify indexing
  • c9f1e3b Release 1.0.152
  • 854fc70 Touch up PR 1347
  • Additional commits viewable in compare view

Updates hyper-util from 0.1.20 to 0.1.21

Release notes

Sourced from hyper-util's releases.

v0.1.21

Additions

  • Add crate-level documentation. (#327)
  • Add client::legacy::Builder::http2_header_table_size() method. (#274)
  • Add client::legacy::Builder::http2_max_concurrent_streams() method. (#274)
  • Add client::legacy::Builder::http2_max_local_error_reset_streams() method. (#277)
  • Add client::legacy::connect::HttpConnector::set_mark() method. (#303)
  • Add rt::tracing::...

    Description has been truncated

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Nov 9, 2026
@dependabot
dependabot Bot force-pushed the dependabot/cargo/crates/cargo-patch-6776afae03 branch 2 times, most recently from ccf7042 to 6e3d4a1 Compare November 10, 2026 07:41
@sovtechpro

sovtechpro Bot commented Nov 10, 2026

Copy link
Copy Markdown

CI run 42777055497 fails deterministically in two places:

  • lock (job 129697912880), step lock.
  • check (job 129697912738), step check, at locked paths: unchanged, and nfx-pay built only from pinned files and dependencies; the preceding compilation and tests passed.

Root cause: this PR updates crates/Cargo.lock, but the separate money-dependency snapshot/pins were not regenerated. The guarded source files still match; the resolved dependency graph no longer does. This is not a flaky or infrastructure failure.

The lock job reports:

locked paths: 43 guarded files and sections match their pins
locked paths: what the money crates are built from differs from its pins:
- money-dep serde_json 1.0.151 ...
+ money-dep serde_json 1.0.154 ...
- money-dep sha2 0.11.0 ...
+ money-dep sha2 0.11.1 ...
- money-dep thiserror 2.0.20 ...
+ money-dep thiserror 2.0.21 ...
- money-dep thiserror-impl 2.0.20 ...
+ money-dep thiserror-impl 2.0.21 ...

Those are the updates in crates/Cargo.lock:4535, crates/Cargo.lock:4606, crates/Cargo.lock:4967, and crates/Cargo.lock:4987. The resolved graph also adds windows-sys 0.52.0 and windows-targets 0.52.6 with its platform crates, and changes the windows-sys 0.61.2 feature set.

Smallest fix: keep the two Cargo lockfile updates and regenerate crates/ci/locked-compiled.txt for the complete new resolved graph, refreshing the corresponding pin(s) in crates/ci/locked.sha256 as required by the lock procedure. Commit those generated lock-data changes together, then verify with crates/ci/check-locked.sh; do not bypass the money-dependency guard.

@sovtechpro sovtechpro Bot added size/XS Lines changed by this pull request: XS (sovtechpro[bot]) deps-risk/low Dependency bump risk: low (sovtechpro[bot] facts table) labels Nov 16, 2026
@sovtechpro

sovtechpro Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Dependency bump facts (automated; nothing was installed or run)

Package Ecosystem From → To Published Publisher Provenance Install scripts Known vulns (old → new)
hyper-util crates.io 0.1.20 → 0.1.21 52 d ago same none none new 0 → 0
serde_json crates.io 1.0.151 → 1.0.154 35 d ago same none none new 0 → 0
sha2 crates.io 0.11.0 → 0.11.1 34 d ago unknown kept none new 0 → 0
thiserror crates.io 2.0.20 → 2.0.21 53 d ago same none none new 0 → 0
  • Files changed: 2, all manifests or lockfiles.
  • Commits: 1, all by Dependabot and verified.
  • Supply-chain risk: low.

Release notes, summarised by a model from untrusted text (it can be wrong): hyper-util adds HTTP/2 builder options, tracing executor wrappers, and a batch of client/pool/proxy fixes, while serde json and thiserror ship small correctness fixes (no notes were provided for sha2). The risky part is hyper-util raising its minimum Rust version from 1.64 to 1.85 and moving to the 2024 edition, which will break builds on older toolchains. Also note hyper-util no longer propagates the active…

Facts from the package registries and OSV. This comment is updated in place.

@dependabot
dependabot Bot force-pushed the dependabot/cargo/crates/cargo-patch-6776afae03 branch from 6e3d4a1 to c79f5de Compare November 16, 2026 05:57
@coderabbitai

coderabbitai Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters: 2

  • crates/Cargo.lock is excluded by !**/*.lock
  • crates/desktop/Cargo.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 0f69c117-4da2-4a77-955c-89f1f2daf957

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

@sovtechpro

sovtechpro Bot commented Nov 16, 2026

Copy link
Copy Markdown

CI run 43813554176 fails deterministically in lock (step lock) and check (step check). In check, the visible nfx-proto, nfx-pay-wire, and nfx-wasm WASM tests pass before the final lock guard fails; this is not a flaky test or runner failure.

Root cause: the PR updates crates/Cargo.lock, including crates in the money crates’ resolved dependency closure, but leaves the separate dependency-pin snapshot unchanged. The source pins still match; the resolved dependency graph does not.

Both jobs report:

locked paths: 44 guarded files and sections match their pins
locked paths: what the money crates are built from differs from its pins:

The reported diff includes serde_json 1.0.151 → 1.0.154, sha2 0.11.0 → 0.11.1, and thiserror/thiserror-impl 2.0.20 → 2.0.21, plus new Windows dependency entries and changed windows-sys 0.61.2 features. The stale snapshot is visible at crates/ci/locked-compiled.txt:21-27, which still pins those old versions, while the new selections are at crates/Cargo.lock:4535, crates/Cargo.lock:4606, crates/Cargo.lock:4967, and crates/Cargo.lock:4987.

Smallest fix: after reviewing the resolved dependency diff, regenerate both pin files together from outside CI with LOCKED_DIRS_UNLOCKED=1 crates/ci/check-locked.sh --pin, then commit the regenerated crates/ci/locked-compiled.txt and crates/ci/locked.sha256 alongside the lockfile updates and run the normal checks. Do not bypass the dependency guard; no test or workflow change is indicated.

@sovtechpro

sovtechpro Bot commented Nov 16, 2026

Copy link
Copy Markdown

CI diagnosis — run 43813559461

  • Failing jobs/steps: lock (job 133120374123, step lock) and check (job 133120374420, step check).
  • Root cause: This PR changes the resolved dependency closure used to build nfx-pay and nfx-pay-wire, but does not update the money-dependency pins in crates/ci/locked-compiled.txt. The money-code lock is therefore rejecting the new graph as designed; this is not a compilation/test failure and does not look flaky or infrastructural. The visible compilation, advisory, and WASM checks in check passed before its final lock verification.

Evidence

Both failing logs report:

locked paths: 44 guarded files and sections match their pins
locked paths: what the money crates are built from differs from its pins

The existing pins still record serde_json 1.0.151, sha2 0.11.0, and thiserror/thiserror-impl 2.0.20 (crates/ci/locked-compiled.txt:80, :82, and :90-91). This PR instead resolves them to 1.0.154, 0.11.1, and 2.0.21 respectively (crates/Cargo.lock:4535, :4606, :4967, and :4987). The logs also show Windows graph drift, including windows-sys 0.52.0 plus windows-targets/platform crates at 0.52.6, while the money pin records windows-sys 0.61.2 (crates/ci/locked-compiled.txt:108).

Smallest fix

If the money-closure updates are not intended, revert those lockfile changes so the resolved graph matches the existing pins. If they are intended, first have sovtech review the dependency diff, then regenerate the pins outside CI with:

LOCKED_DIRS_UNLOCKED=1 crates/ci/check-locked.sh --pin

Commit the resulting crates/ci/locked-compiled.txt and crates/ci/locked.sha256 updates together with the lockfile changes. Re-running the unchanged workflow will not fix this deterministic pin mismatch.

…pdates

Bumps the cargo-patch group with 4 updates in the /crates directory: [hyper-util](https://github.com/hyperium/hyper-util), [serde_json](https://github.com/serde-rs/json), [sha2](https://github.com/RustCrypto/hashes) and [thiserror](https://github.com/dtolnay/thiserror).
Bumps the cargo-patch group with 4 updates in the /crates/desktop directory: [hyper-util](https://github.com/hyperium/hyper-util), [serde_json](https://github.com/serde-rs/json), [sha2](https://github.com/RustCrypto/hashes) and [thiserror](https://github.com/dtolnay/thiserror).


Updates `hyper-util` from 0.1.20 to 0.1.21
- [Release notes](https://github.com/hyperium/hyper-util/releases)
- [Changelog](https://github.com/hyperium/hyper-util/blob/master/CHANGELOG.md)
- [Commits](hyperium/hyper-util@v0.1.20...v0.1.21)

Updates `serde_json` from 1.0.151 to 1.0.154
- [Release notes](https://github.com/serde-rs/json/releases)
- [Commits](serde-rs/json@v1.0.151...v1.0.154)

Updates `sha2` from 0.11.0 to 0.11.1
- [Commits](RustCrypto/hashes@sha2-v0.11.0...sha2-v0.11.1)

Updates `thiserror` from 2.0.20 to 2.0.21
- [Release notes](https://github.com/dtolnay/thiserror/releases)
- [Commits](dtolnay/thiserror@2.0.20...2.0.21)

Updates `serde_json` from 1.0.151 to 1.0.154
- [Release notes](https://github.com/serde-rs/json/releases)
- [Commits](serde-rs/json@v1.0.151...v1.0.154)

Updates `hyper-util` from 0.1.20 to 0.1.21
- [Release notes](https://github.com/hyperium/hyper-util/releases)
- [Changelog](https://github.com/hyperium/hyper-util/blob/master/CHANGELOG.md)
- [Commits](hyperium/hyper-util@v0.1.20...v0.1.21)

Updates `sha2` from 0.11.0 to 0.11.1
- [Commits](RustCrypto/hashes@sha2-v0.11.0...sha2-v0.11.1)

Updates `thiserror` from 2.0.20 to 2.0.21
- [Release notes](https://github.com/dtolnay/thiserror/releases)
- [Commits](dtolnay/thiserror@2.0.20...2.0.21)

Updates `hyper-util` from 0.1.20 to 0.1.21
- [Release notes](https://github.com/hyperium/hyper-util/releases)
- [Changelog](https://github.com/hyperium/hyper-util/blob/master/CHANGELOG.md)
- [Commits](hyperium/hyper-util@v0.1.20...v0.1.21)

Updates `serde_json` from 1.0.151 to 1.0.154
- [Release notes](https://github.com/serde-rs/json/releases)
- [Commits](serde-rs/json@v1.0.151...v1.0.154)

Updates `sha2` from 0.11.0 to 0.11.1
- [Commits](RustCrypto/hashes@sha2-v0.11.0...sha2-v0.11.1)

Updates `thiserror` from 2.0.20 to 2.0.21
- [Release notes](https://github.com/dtolnay/thiserror/releases)
- [Commits](dtolnay/thiserror@2.0.20...2.0.21)

Updates `serde_json` from 1.0.151 to 1.0.154
- [Release notes](https://github.com/serde-rs/json/releases)
- [Commits](serde-rs/json@v1.0.151...v1.0.154)

Updates `hyper-util` from 0.1.20 to 0.1.21
- [Release notes](https://github.com/hyperium/hyper-util/releases)
- [Changelog](https://github.com/hyperium/hyper-util/blob/master/CHANGELOG.md)
- [Commits](hyperium/hyper-util@v0.1.20...v0.1.21)

Updates `sha2` from 0.11.0 to 0.11.1
- [Commits](RustCrypto/hashes@sha2-v0.11.0...sha2-v0.11.1)

Updates `thiserror` from 2.0.20 to 2.0.21
- [Release notes](https://github.com/dtolnay/thiserror/releases)
- [Commits](dtolnay/thiserror@2.0.20...2.0.21)

---
updated-dependencies:
- dependency-name: hyper-util
  dependency-version: 0.1.21
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo-patch
- dependency-name: hyper-util
  dependency-version: 0.1.21
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo-patch
- dependency-name: serde_json
  dependency-version: 1.0.154
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo-patch
- dependency-name: serde_json
  dependency-version: 1.0.154
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo-patch
- dependency-name: sha2
  dependency-version: 0.11.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo-patch
- dependency-name: sha2
  dependency-version: 0.11.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo-patch
- dependency-name: thiserror
  dependency-version: 2.0.21
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo-patch
- dependency-name: thiserror
  dependency-version: 2.0.21
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@sovtechpro

sovtechpro Bot commented Nov 16, 2026

Copy link
Copy Markdown

CI diagnosis — run 43887143003

  • Failing jobs/steps: lock (job 133368256772, step lock) and check (job 133368256351, step check).
  • Root cause: this PR changes the dependency closure used to build nfx-pay and nfx-pay-wire in crates/Cargo.lock, but the separate snapshot in crates/ci/locked-compiled.txt still pins the old graph. The money-code guard is rejecting that drift as designed; this is deterministic, not a flaky test or infrastructure failure. In check, the final Wasm tests passed before locked-path verification exited with code 1.

Evidence

Both failing logs report:

locked paths: what the money crates are built from differs from its pins

The 44 guarded files and sections still match their pins, so this is dependency-graph drift rather than a guarded-source mismatch. The existing pins record serde_json 1.0.151, sha2 0.11.0, and thiserror/thiserror-impl 2.0.20 (crates/ci/locked-compiled.txt:80, :82, and :90-91), while this PR resolves them to 1.0.154, 0.11.1, and 2.0.21 (crates/Cargo.lock:4535, :4606, :4967, and :4987). The reported diff also adds windows-sys 0.52.0, windows-targets 0.52.6, and the associated Windows architecture packages.

Smallest fix

After sovtech reviews the resolved dependency diff, regenerate the pins outside CI with:

LOCKED_DIRS_UNLOCKED=1 crates/ci/check-locked.sh --pin

Commit the resulting crates/ci/locked-compiled.txt and crates/ci/locked.sha256 changes together with the lockfile updates, then run the normal checks. If the money-closure changes are unintended, revert those lockfile changes instead. Re-running the unchanged workflow will not clear this pin mismatch.

@sovtechpro

sovtechpro Bot commented Nov 16, 2026

Copy link
Copy Markdown

CI diagnosis — run 43887155096

Failing jobs/steps: lock / lock and check / check, both exiting 1 in the locked-paths money-dependency verification.

Root cause: this PR updates the resolved dependency graph in crates/Cargo.lock, but the recorded money-crate dependency facts in crates/ci/locked-compiled.txt still describe the old graph. This is a deterministic pin/lockfile mismatch, not a test or infrastructure failure: the guarded-file hashes pass before dependency verification fails.

Evidence: both logs report:

locked paths: 44 guarded files and sections match their pins

locked paths: what the money crates are built from differs from its pins

The reported pinned → resolved versions are serde_json 1.0.151 → 1.0.154, sha2 0.11.0 → 0.11.1, and thiserror / thiserror-impl 2.0.20 → 2.0.21. The lockfile confirms the first two at crates/Cargo.lock:4535 and crates/Cargo.lock:4606. The resolved Windows graph also adds the windows-sys 0.52.0 / windows-targets 0.52.6 family and changes the windows-sys 0.61.2 feature set.

Smallest fix: review that complete dependency/feature-graph diff first. If all of it is intended, refresh both pin files from a non-CI security-stage checkout, as documented at crates/ci/check-locked.sh:33-38:

LOCKED_DIRS_UNLOCKED=1 crates/ci/check-locked.sh --pin

Commit the resulting crates/ci/locked-compiled.txt and crates/ci/locked.sha256. If the extra dependency-graph changes are not intended, regenerate the lockfile without them rather than re-pinning them.

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 deps-risk/low Dependency bump risk: low (sovtechpro[bot] facts table) rust Pull requests that update rust code size/XS Lines changed by this pull request: XS (sovtechpro[bot])

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants