Fix cargo deny warnings and errors #2332
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The CI has been failing since 20 August 2024. Since it's been failing, I suspect commits following that PR have added things that have broken the
cargo deny check
command even more. This PR should make the CI green again.This PR fixes the errors. Things this PR addresses:
targets
property under[graph]
fieldvulnerability
andunmaintained
properties since they've been removed fromcargo-deny
and now emit errors.deny.toml
properties likeskip-tree
. Maybe this was needed at some point, but it's not anymore.num-derive
fromskip
list since it doesn't emit errors anymore.miniz_oxide
toskip
list since some deps depend on0.7.4
while others on0.8.0
. I've created a ex-rs PR on to bump the dep to0.8.0
Update Cargo.toml dependencies and release 1.73.0 johannesvollmer/exrs#240Current error/warning logs
The PR solves these erorr/warnings: