Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make sure we use Sparse protocol for cargo audit. #94

Open
CosminPerRam opened this issue Sep 10, 2023 · 1 comment
Open

Make sure we use Sparse protocol for cargo audit. #94

CosminPerRam opened this issue Sep 10, 2023 · 1 comment
Labels
ci Continous integration enhancement New feature or request
Milestone
Backlog

Comments

@CosminPerRam
Copy link
Member

CosminPerRam commented Sep 10, 2023 •
edited
Loading

What is this feature about?
Add cargo audit to CI.

Additional context/references
Audits the Cargo.lock file for crates containing security vulnerabilities.
Also make sure the version used is above 0.18, as in that version they made the Sparse protocol the default one, which is much faster, check a blog post about that here.
@CosminPerRam CosminPerRam added enhancement New feature or request ci Continous integration labels Sep 10, 2023
@CosminPerRam
Copy link
Member Author

We already have cargo audit in CI by rustsec/audit-check. I'll change this issue to be a tracker to make sure we use the new sparse protocol (to make CI faster).

@CosminPerRam CosminPerRam changed the title [CI] Add cargo audit. [CI] Make sure we use Sparse protocol for cargo audit. Sep 16, 2023
@CosminPerRam CosminPerRam changed the title [CI] Make sure we use Sparse protocol for cargo audit. Make sure we use Sparse protocol for cargo audit. Sep 19, 2023
@cainthebest cainthebest added this to the Backlog milestone Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ci Continous integration enhancement New feature or request
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
2 participants
@CosminPerRam @cainthebest