ci: add cargo deny #7651
Draft
ci: add cargo deny #7651
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
parquet
timsaucer
force-pushed
the
feat/add-cargo-deny
branch
from
f15651b to
068c60d
Compare
|
Moving to draft until I can resolve maintainer suggestion in the original issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which issue does this PR close?
We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax.
Closes #7648.
Rationale for this change
This change helps to ensure code quality by reducing duplicate dependencies and to check for vulnerabilities.
What changes are included in this PR?
Update dependency for
tonicwhich removes some of the duplicate dependencies we have right now. It also adds a cargo deny configuration with details about the remaining duplicates in the repository with links to the issues or PRs to resolve them.Are there any user-facing changes?
None