search

crazyscot / brot3

Yet Another Fractal Plotter
Other
0 stars 0 forks source link

chore(deps): bump the cargo group with 5 updates #146

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps the cargo group with 5 updates:

Package From To
clap 4.5.13 4.5.16
serde 1.0.204 1.0.209
quick_cache 0.6.2 0.6.6
iai-callgrind 0.12.3 0.13.1
tokio 1.38.1 1.40.0

Updates clap from 4.5.13 to 4.5.16

Release notes

Sourced from clap's releases.

v4.5.16

[4.5.16] - 2024-08-15

Fixes

  • (derive) Improve error messages when derive feature is missing

v4.5.15

[4.5.15] - 2024-08-10

Compatiblity

  • (unstable-ext) Arg::remove changed return types

Fixes

  • (unstable-ext) Make Arg::remove return the removed item

v4.5.14

[4.5.14] - 2024-08-08

Features

  • (unstable-ext) Added Arg::add for attaching arbitrary state, like completion hints, to Arg without Arg knowing about it
Changelog

Sourced from clap's changelog.

[4.5.16] - 2024-08-15

Fixes

  • (derive) Improve error messages when derive feature is missing

[4.5.15] - 2024-08-10

Compatiblity

  • (unstable-ext) Arg::remove changed return types

Fixes

  • (unstable-ext) Make Arg::remove return the removed item

[4.5.14] - 2024-08-08

Features

  • (unstable-ext) Added Arg::add for attaching arbitrary state, like completion hints, to Arg without Arg knowing about it
Commits


Updates serde from 1.0.204 to 1.0.209

Release notes

Sourced from serde's releases.

v1.0.209

  • Fix deserialization of empty structs and empty tuples inside of untagged enums (#2805, thanks @​Mingun)

v1.0.208

  • Support serializing and deserializing unit structs in a flatten field (#2802, thanks @​jonhoo)

v1.0.207

  • Improve interactions between flatten attribute and skip_serializing/skip_deserializing (#2795, thanks @​Mingun)

v1.0.206

  • Improve support for flatten attribute inside of enums (#2567, thanks @​Mingun)

v1.0.205

  • Use serialize_entry instead of serialize_key + serialize_value when serialize flattened newtype enum variants (#2785, thanks @​Mingun)
  • Avoid triggering a collection_is_never_read lint in the deserialization of enums containing flattened fields (#2791)
Commits
  • 30752ac Release 1.0.209
  • b84e6ca Improve wording of PR 2805 comments
  • 87a2fb0 Wrap comments from PR 2805 to 80 columns
  • 9eaf7b9 Merge pull request #2805 from Mingun/untagged-tests
  • 7bde100 Replace MapRefDeserializer with value::MapDeserializer
  • da7fc79 Fix deserialization of empty struct variant in untagged enums
  • 4c5fec1 Test special cases that reaches SeqRefDeserializer::deserialize_any len==0 co...
  • 6588b0a Cover Content::Seq case in VariantRefDeserializer::struct_variant
  • 0093f74 Split test newtype_enum into four tests for each variant
  • 171c6da Complete coverage of ContentRefDeserializer::deserialize_newtype_struct
  • Additional commits viewable in compare view


Updates quick_cache from 0.6.2 to 0.6.6

Release notes

Sourced from quick_cache's releases.

v0.6.5

What's Changed

Full Changelog: https://github.com/arthurprs/quick-cache/compare/v0.6.2...v0.6.5

Commits


Updates iai-callgrind from 0.12.3 to 0.13.1

Release notes

Sourced from iai-callgrind's releases.

v0.13.1

[0.13.1] - 2024-08-28

Changed

  • Updated locked non-development dependencies:
    • cc: 1.1.13 -> 1.1.15
    • quote: 1.0.36 -> 1.0.37
    • serde: 1.0.208 -> 1.0.209
    • serde_json: 1.0.126 -> 1.0.127
    • syn: 2.0.75 -> 2.0.76

Fixed

  • (#248): If the Command's path was a simple command name like echo, cat, the path was interpreted as relative path instead of searched in the $PATH. Relative paths like ./echo are now interpreted as relative to the current directory. If running the Command in a Sandbox, this is the root directory of the Sandbox. Otherwise, it is the directory which is set by cargo bench.

Full Changelog: https://github.com/iai-callgrind/iai-callgrind/compare/v0.13.0...v0.13.1

v0.13.0

[0.13.0] - 2024-08-19

!!! IMPORTANT The default to run binary benchmarks in a sandbox has been changed from true to false. The setup and teardown of the binary_benchmark_group! are not executed in the sandbox anymore !!!

The way to set up binary benchmarks has completely changed and has been rewritten from scratch! The api for binary and library benchmarks is now consistent and most features from library benchmarks which were missing for binary benchmarks are now available in binary benchmarks, too. For example comparison of benchmarks by id. If you are using library benchmarks but not binary benchmarks, this release doesn't change much. There are no breaking changes for library benchmarks and you can jump right to the changes section of this release. Otherwise, here's a small introduction to the new api and the changes for binary benchmarks.

There are a lot of advantages for you and honestly for us, too, because we don't have to maintain two completely different apis. Binary benchmarks and library benchmarks can now be written in a similar fashion what makes writing benchmarks for a crate's binaries just easier and faster. No need to learn a completely different api if you already used library benchmarks and vice versa! Also, the feature set between library benchmarks and binary benchmarks diverged over time. For example comparison by id of benchmarks within the same group was available in library benchmarks via the library_benchmark_group! macro but not in binary benchmarks. Such differences are gone, now. Also, if you find out the new #[binary_attribute] does not provide you with the same power as the old builder api, you can still use a low level api and can even intermix the two styles. The new low level api is more intuitive than the old builder api, just more powerful and mirrors the binary_benchmark attribute as much as possible.

For example if the crate's binary is named my-binary:

use iai_callgrind::{binary_benchmark, binary_benchmark_group};

#[binary_benchmark]
#[bench::some_id("foo")]
fn bench_binary(arg: &str) -> iai_callgrind::Command {
iai_callgrind::Command::new(env!("CARGO_BIN_EXE_my-binary"))
.arg(arg)
.build()
}
</tr></table>

... (truncated)

Changelog

Sourced from iai-callgrind's changelog.

[0.13.1] - 2024-08-28

Changed

  • Updated locked non-development dependencies:
    • cc: 1.1.13 -> 1.1.15
    • quote: 1.0.36 -> 1.0.37
    • serde: 1.0.208 -> 1.0.209
    • serde_json: 1.0.126 -> 1.0.127
    • syn: 2.0.75 -> 2.0.76

Fixed

  • (#221): If the Command's path was a simple command name like echo, cat, the path was interpreted as relative path instead of searched in the $PATH. Relative paths like ./echo are now interpreted as relative to the current directory. If running the Command in a Sandbox, this is the root directory of the Sandbox. Otherwise, it is the directory which is set by cargo bench.

[0.13.0] - 2024-08-19

!!! IMPORTANT The default to run binary benchmarks in a sandbox has been changed from true to false. The setup and teardown of the binary_benchmark_group! are not executed in the sandbox anymore !!!

The way to set up binary benchmarks has completely changed and has been rewritten from scratch! The api for binary and library benchmarks is now consistent and most features from library benchmarks which were missing for binary benchmarks are now available in binary benchmarks, too. For example comparison of benchmarks by id. If you are using library benchmarks but not binary benchmarks, this release doesn't change much. There are no breaking changes for library benchmarks and you can jump right to the changes section of this release. Otherwise, here's a small introduction to the new api and the changes for binary benchmarks.

There are a lot of advantages for you and honestly for us, too, because we don't have to maintain two completely different apis. Binary benchmarks and library benchmarks can now be written in a similar fashion what makes writing benchmarks for a crate's binaries just easier and faster. No need to learn a completely different api if you already used library benchmarks and vice versa! Also, the feature set between library benchmarks and binary benchmarks diverged over time. For example comparison by id of benchmarks within the same group was available in library benchmarks via the library_benchmark_group! macro but not in binary benchmarks. Such differences are gone, now. Also, if you find out the new #[binary_attribute] does not provide you with the same power as the old builder api, you can still use a low level api and can even intermix the two styles. The new low level api is more intuitive than the old builder api, just more powerful and mirrors the binary_benchmark attribute as much as possible.

... (truncated)

Commits
  • 492e1a1 Merge branch 'release'
  • e79e7f9 tests(helper): Try another impl of echo helper to fix ci issues
  • 61fd5d5 Bump version v0.13.0 -> v0.13.1
  • 8b1ffaa chore: Remove README from version bump configuration
  • e64ec6b Update CHANGELOG
  • 59e91fb Merge pull request #251 from iai-callgrind/renovate/cc-1.x-lockfile
  • 960df73 Merge pull request #253 from gamma0987/groups-in-justfile
  • 983cc63 chore(just): Group recipes in Justfile. Fix output of command not found
  • e10ee57 chore(deps): update rust crate cc to v1.1.15
  • 96bcfdc Merge pull request #248 from gamma0987/fix-path
  • Additional commits viewable in compare view


Updates tokio from 1.38.1 to 1.40.0

Release notes

Sourced from tokio's releases.

Tokio v1.40.0

1.40.0 (August 30th, 2024)

Added

  • io: add util::SimplexStream (#6589)
  • process: stabilize Command::process_group (#6731)
  • sync: add {TrySendError,SendTimeoutError}::into_inner (#6755)
  • task: add JoinSet::join_all (#6784)

Added (unstable)

  • runtime: add Builder::{on_task_spawn, on_task_terminate} (#6742)

Changed

  • io: use vectored io for write_all_buf when possible (#6724)
  • runtime: prevent niche-optimization to avoid triggering miri (#6744)
  • sync: mark mpsc types as UnwindSafe (#6783)
  • sync,time: make Sleep and BatchSemaphore instrumentation explicit roots (#6727)
  • task: use NonZeroU64 for task::Id (#6733)
  • task: include panic message when printing JoinError (#6753)
  • task: add #[must_use] to JoinHandle::abort_handle (#6762)
  • time: eliminate timer wheel allocations (#6779)

Documented

  • docs: clarify that [build] section doesn't go in Cargo.toml (#6728)
  • io: clarify zero remaining capacity case (#6790)
  • macros: improve documentation for select! (#6774)
  • sync: document mpsc channel allocation behavior (#6773)

#6589: tokio-rs/tokio#6589 #6724: tokio-rs/tokio#6724 #6727: tokio-rs/tokio#6727 #6728: tokio-rs/tokio#6728 #6731: tokio-rs/tokio#6731 #6733: tokio-rs/tokio#6733 #6742: tokio-rs/tokio#6742 #6744: tokio-rs/tokio#6744 #6753: tokio-rs/tokio#6753 #6755: tokio-rs/tokio#6755 #6762: tokio-rs/tokio#6762 #6773: tokio-rs/tokio#6773 #6774: tokio-rs/tokio#6774 #6779: tokio-rs/tokio#6779 #6783: tokio-rs/tokio#6783 #6784: tokio-rs/tokio#6784 #6790: tokio-rs/tokio#6790

... (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