crazyscot / brot3

Yet Another Fractal Plotter
Other
0 stars 0 forks source link

chore(deps): bump the cargo group with 10 updates #138

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps the cargo group with 10 updates:

Package From To
clap 4.5.8 4.5.11
serde 1.0.203 1.0.204
anstyle 1.0.7 1.0.8
quick_cache 0.5.1 0.6.2
iai-callgrind 0.11.0 0.12.0
built 0.7.3 0.7.4
bytes 1.6.0 1.6.1
tokio 1.38.0 1.39.1
tokio-macros 2.3.0 2.4.0
tauri-build 1.5.2 1.5.3

Updates clap from 4.5.8 to 4.5.11

Release notes

Sourced from clap's releases.

v4.5.10

[4.5.10] - 2024-07-23

v4.5.9

[4.5.9] - 2024-07-09

Fixes

  • (error) When defining a custom help flag, be sure to suggest it like we do the built-in one
Changelog

Sourced from clap's changelog.

[4.5.11] - 2024-07-25

[4.5.10] - 2024-07-23

[4.5.9] - 2024-07-09

Fixes

  • (error) When defining a custom help flag, be sure to suggest it like we do the built-in one
Commits
  • 349ed30 chore: Release
  • 68ed9ff docs: Update changelog
  • afecaa4 Merge pull request #5576 from shannmu/option_value_new
  • 4a00677 chore: Release
  • 36c849b refactor(clap_complete): Reuse code about shortflag parsing
  • fc479ba feat(clap_complete): Add support for -fbar and -f=bar completion
  • 48a23f5 test(clap_complete): Add test cases for -fbar and -f=bar completion
  • 6b18d77 docs(derive): Acknowledge Vec<Vec>
  • 5efa52a chore: Release
  • 1857e47 docs: Update changelog
  • Additional commits viewable in compare view


Updates serde from 1.0.203 to 1.0.204

Release notes

Sourced from serde's releases.

v1.0.204

  • Apply #[diagnostic::on_unimplemented] attribute on Rust 1.78+ to suggest adding serde derive or enabling a "serde" feature flag in dependencies (#2767, thanks @​weiznich)
Commits
  • 18dcae0 Release 1.0.204
  • 58c307f Alphabetize list of rustc-check-cfg
  • 8cc4809 Merge pull request #2769 from dtolnay/onunimpl
  • 1179158 Update ui test with diagnostic::on_unimplemented from PR 2767
  • 91aa40e Add ui test of unsatisfied serde trait bound
  • 595019e Cut test_suite from workspace members in old toolchain CI jobs
  • b0d7917 Pull in trybuild 'following types implement trait' fix
  • 8e6637a Merge pull request #2767 from weiznich/feature/diagnostic_on_unimplemented
  • 694fe05 Use the #[diagnostic::on_unimplemented] attribute when possible
  • f3dfd2a Suppress dead code warning in test of unit struct remote derive
  • Additional commits viewable in compare view


Updates anstyle from 1.0.7 to 1.0.8

Commits


Updates quick_cache from 0.5.1 to 0.6.2

Release notes

Sourced from quick_cache's releases.

v0.6.2

What's Changed

New Contributors

v0.5.2

What's Changed

New Contributors

Commits


Updates iai-callgrind from 0.11.0 to 0.12.0

Release notes

Sourced from iai-callgrind's releases.

v0.12.0

Changelog

All notable changes to this project will be documented in this file.

This is the combined CHANGELOG for all packages: iai-callgrind, iai-callgrind-runner and iai-callgrind-macros. iai-callgrind and iai-callgrind-runner use the same version which is the version used here. iai-callgrind-macros uses a different version number but is not a standalone package, so its changes are also listed here.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

[Unreleased]

[0.12.0] - 2024-07-24

Added

  • (#160): Add --separate-targets (env: IAI_CALLGRIND_SEPARATE_TARGETS). Using this option causes the compilation target to be included in the iai-callgrind output directory tree to mitigate issues when running benchmarks on multiple targets. For example, instead of having all output files under target/iai, using this option puts all files under the directory target/iai/x86_64-unknown-linux-gnu if running the benchmarks on the x86_64-unknown-linux-gnu target.
  • (#188): Add the option --home (env: IAI_CALLGRIND_HOME) to be able to change the default home directory target/iai.
  • (#192): The #[bench] attribute now accepts a setup parameter similarly to the #[benches] attribute. The #[bench] and #[benches] attribute accept a new teardown parameter. The teardown function is called with the return value of the benchmark function. The #[library_benchmark] attribute now accepts a global setup and teardown parameter which are applied to all following #[bench] and #[benches] attributes if they don't specify one of these parameters themselves.
  • (#194): Add --nocapture (env: IAI_CALLGRIND_NOCAPTURE) option to tell iai-callgrind to not capture callgrind terminal output of benchmark functions. For all possible values see the README.
  • (#201): Add support for generic benchmark functions fixing #198 (Generic bench arguments cause compilation failure).

Changed

  • Update locked dependencies: syn -> 2.0.72, cc -> 1.1.5, serde -> 1.0.204
  • Update minimal version of syn -> 2.0.32
  • (#201): The BinaryBenchmarkConfig::entry_point and Run::entry_point functions now use glob patterns as argument with * as placeholder for any amount of characters.
  • (#203): Improve error messages during the initialization phase of the iai-callgrind-runner, get rid of a lot of unwraps and include a solution hint. These errors mainly happen if the iai-callgrind library has a different version than the iai-callgrind-runner binary.

Fixed

  • (#192): Fix a wrongly issued compiler error when the setup parameter was specified before the args parameter and the number of elements of the args parameter did not match the number of arguments of the benchmark function.
  • (#192): Fix the error span of wrong user supplied argument types or wrong number of arguments. The compiler errors now point to the exact location of any wrong arguments instead of the generic call-site of the #[library_benchmark] attribute. If there is a setup function involved, we leave it to the rust compiler to point to the location of the setup function and the wrong arguments.

Full Changelog: https://github.com/iai-callgrind/iai-callgrind/compare/v0.11.1...v0.12.0

v0.11.1

... (truncated)

Changelog

Sourced from iai-callgrind's changelog.

[0.12.0] - 2024-07-24

Added

  • (#160): Add --separate-targets (env: IAI_CALLGRIND_SEPARATE_TARGETS). Using this option causes the compilation target to be included in the iai-callgrind output directory tree to mitigate issues when running benchmarks on multiple targets. For example, instead of having all output files under target/iai, using this option puts all files under the directory target/iai/x86_64-unknown-linux-gnu if running the benchmarks on the x86_64-unknown-linux-gnu target.
  • (#188): Add the option --home (env: IAI_CALLGRIND_HOME) to be able to change the default home directory target/iai.
  • (#192): The #[bench] attribute now accepts a setup parameter similarly to the #[benches] attribute. The #[bench] and #[benches] attribute accept a new teardown parameter. The teardown function is called with the return value of the benchmark function. The #[library_benchmark] attribute now accepts a global setup and teardown parameter which are applied to all following #[bench] and #[benches] attributes if they don't specify one of these parameters themselves.
  • (#194): Add --nocapture (env: IAI_CALLGRIND_NOCAPTURE) option to tell iai-callgrind to not capture callgrind terminal output of benchmark functions. For all possible values see the README.
  • (#201): Add support for generic benchmark functions fixing #198 (Generic bench arguments cause compilation failure).

Changed

  • Update locked dependencies: syn -> 2.0.72, cc -> 1.1.5, serde -> 1.0.204
  • Update minimal version of syn -> 2.0.32
  • (#201): The BinaryBenchmarkConfig::entry_point and Run::entry_point functions now use glob patterns as argument with * as placeholder for any amount of characters.
  • (#203): Improve error messages during the initialization phase of the iai-callgrind-runner, get rid of a lot of unwraps and include a solution hint. These errors mainly happen if the iai-callgrind library has a different version than the iai-callgrind-runner binary.

Fixed

  • (#192): Fix a wrongly issued compiler error when the setup parameter was specified before the args parameter and the number of elements of the args parameter did not

... (truncated)

Commits
  • 315a9a1 Merge branch 'release'
  • 4414593 Update CHANGELOG
  • 1303df0 Update README
  • 5e0bf6f Bump version v0.11.1 -> v0.12.0
  • f656e92 Bump iai-callgrind-macros version v0.2.0 -> v0.3.0
  • d798b8d Update CHANGELOG
  • e168fda Merge pull request #203 from gamma0987/better-version-mismatch-error-message
  • bfbd8c0 tests(runner): Add tests for the library and runner version comparison
  • d67d90b iai-callgrind-runner: Compare the library and runner version as soon as possible
  • d1428eb iai-callgrind-runner: Provide better error message if the argument parsing fails
  • Additional commits viewable in compare view


Updates built from 0.7.3 to 0.7.4

Changelog

Sourced from built's changelog.

[0.7.4] - 2024-07-07

Added

  • Honor SOURCE_DATE_EPOCH in BUILT_TIME_UTC
  • Bump git2 to 0.19
Commits


Updates bytes from 1.6.0 to 1.6.1

Release notes

Sourced from bytes's releases.

Bytes 1.6.1

This release fixes a bug where Bytes::is_unique returns incorrect values when the Bytes originates from a shared BytesMut. (#718)

Changelog

Sourced from bytes's changelog.

1.6.1 (July 13, 2024)

This release fixes a bug where Bytes::is_unique returns incorrect values when the Bytes originates from a shared BytesMut. (#718)

Commits


Updates tokio from 1.38.0 to 1.39.1

Release notes

Sourced from tokio's releases.

Tokio v1.39.1

1.39.1 (July 23rd, 2024)

This release reverts "time: avoid traversing entries in the time wheel twice" because it contains a bug. (#6715)

#6715: tokio-rs/tokio#6715

Tokio v1.39.0

1.39.0 (July 23rd, 2024)

  • This release bumps the MSRV to 1.70. (#6645)
  • This release upgrades to mio v1. (#6635)
  • This release upgrades to windows-sys v0.52 (#6154)

Added

  • io: implement AsyncSeek for Empty (#6663)
  • metrics: stabilize num_alive_tasks (#6619, #6667)
  • process: add Command::as_std_mut (#6608)
  • sync: add watch::Sender::same_channel (#6637)
  • sync: add {Receiver,UnboundedReceiver}::{sender_strong_count,sender_weak_count} (#6661)
  • sync: implement Default for watch::Sender (#6626)
  • task: implement Clone for AbortHandle (#6621)
  • task: stabilize consume_budget (#6622)

Changed

  • io: improve panic message of ReadBuf::put_slice() (#6629)
  • io: read during write in copy_bidirectional and copy (#6532)
  • runtime: replace num_cpus with available_parallelism (#6709)
  • task: avoid stack overflow when passing large future to block_on (#6692)
  • time: avoid traversing entries in the time wheel twice (#6584)
  • time: support IntoFuture with timeout (#6666)
  • macros: support IntoFuture with join! and select! (#6710)

Fixed

  • docs: fix docsrs builds with the fs feature enabled (#6585)
  • io: only use short-read optimization on known-to-be-compatible platforms (#6668)
  • time: fix overflow panic when using large durations with Interval (#6612)

Added (unstable)

  • macros: allow unhandled_panic behavior for #[tokio::main] and #[tokio::test] (#6593)
  • metrics: add spawned_tasks_count (#6114)
  • metrics: add worker_park_unpark_count (#6696)
  • metrics: add worker thread id (#6695)

Documented

... (truncated)

Commits


Updates tokio-macros from 2.3.0 to 2.4.0

Commits


Updates tauri-build from 1.5.2 to 1.5.3

Release notes

Sourced from tauri-build's releases.

tauri-build v1.5.3

Fetching advisory database from `https://github.com/RustSec/advisory-db.git`
      Loaded 630 security advisories (from /home/runner/.cargo/advisory-db)
    Updating crates.io index
    Scanning Cargo.lock for vulnerabilities (590 crate dependencies)
Crate:     atty
Version:   0.2.14
Warning:   unsound
Title:     Potential unaligned read
Date:      2021-07-04
ID:        RUSTSEC-2021-0145
URL:       https://rustsec.org/advisories/RUSTSEC-2021-0145
Dependency tree:
atty 0.2.14
└── clap 3.2.25
    └── tauri 1.7.0
        ├── tauri 1.7.0
        ├── restart 0.1.0
        └── app-updater 0.1.0

warning: 1 allowed warning found

[1.5.3]

Dependencies

  • Upgraded to tauri-utils@1.6.0
  • Upgraded to tauri-codegen@1.4.4
Updating crates.io index
   Packaging tauri-build v1.5.3 (/home/runner/work/tauri/tauri/core/tauri-build)
   Verifying tauri-build v1.5.3 (/home/runner/work/tauri/tauri/core/tauri-build)
    Updating crates.io index
 Downloading crates ...
  Downloaded tauri-winres v0.1.1
  Downloaded embed-resource v2.4.2
  Downloaded cargo_toml v0.15.3
   Compiling proc-macro2 v1.0.86
</tr></table> 

... (truncated)

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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 4 months ago

Looks like these dependencies are updatable in another way, so this is no longer needed.