Fix vulnerable crossbeam dependency, audit strategy#73
Merged
Conversation
Signed-off-by: Simon Gellis <simongellis@gmail.com>
Signed-off-by: Simon Gellis <simongellis@gmail.com>
Signed-off-by: Simon Gellis <simongellis@gmail.com>
Signed-off-by: Simon Gellis <simongellis@gmail.com>
EnriqueL8
reviewed
Jul 8, 2026
EnriqueL8
left a comment
EnriqueL8
left a comment
Contributor
There was a problem hiding this comment.
Thanks @SupernaviX , agree on the cron job cadence!
EnriqueL8
approved these changes
Jul 8, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Context
After merging a "speed up the build" PR, the main branch's "test" job was failing. Cargo audit was flagging a new vuln reported yesterday.
Important Changes Introduced
First of all, update dependencies past the vulnerability. (Not sure why Dependabot didn't do this, maybe because it was a transitive version bump).
Secondly, invoke cargo audit on a cronjob (daily at midnight UTC) instead of on changes. It will open an issue reporting any vulnerabilities, and will not block builds. This means that vulnerabilities reported outside of active development windows will be caught and addressed quickly.