CI: Disallow all warnings in cargo deny and prune unmatched skips
#8283
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.
Connections
Split out from #6876
Description
The warnings right now all entail
unmatched-skip/unmatched-skip-rootthat have (likely) gotten stale since various automated Renovate bumps whereCargo.lockchanges don't require the corresponding unmatched duplicate to be removed from.deny.tomlagain.An exception has been made for
unmatched-organizationsince we don't always have agitdependency on a fork ingfx-rs, resulting in a warning about that orga being insources.allow-org.github.Testing
Locally:
$ cargo deny --all-features --workspace check -Dwarnings -Aunmatched-organizationSquash or Rebase?
Rebase
Checklist
cargo fmt.taplo format.cargo clippy --tests. If applicable, add:--target wasm32-unknown-unknowncargo xtask testto run tests.CHANGELOG.mdentry.