Skip to content

Commit

Permalink
update dependencies to avoid depending on the chrono crate
Browse files Browse the repository at this point in the history
The `chrono` crate has a security vulnerability, and the ecosystem is
moving away from it, so should we (also it annoys me that `cargo-check`
doesn't pass anymore because of this).

See https://rustsec.org/advisories/RUSTSEC-2020-0159 for details.

Cargo-check can't be configured to tolerate vulnerabilities in dev
dependencies right now. It's a feature request, so maybe it'll come one
day:
EmbarkStudios/cargo-deny#322
  • Loading branch information
HippoBaro committed Nov 26, 2021
1 parent bbeaecb commit 07f55d0
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion glommio/Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ hdrhistogram = "7.3.0"
pretty_env_logger = "~0.4"
rand = "~0.8"
tokio = { version = "1.12", default-features = false, features = ["rt", "macros", "rt-multi-thread", "net", "io-util", "time", "sync"] }
tracing-subscriber = "~0.2"
tracing-subscriber = { version = "~0.3", features = ["env-filter"] }

[build-dependencies]
cc = "1.0"
Expand Down

0 comments on commit 07f55d0

Please sign in to comment.