-
Notifications
You must be signed in to change notification settings - Fork 213
ignore audit advisories we want to ignore, or cannot do anything right now #1550
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.
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
Conversation
b389d60
to
1f23ef7
Compare
don't merge just yet, I want to test the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM whenever you want to merge :)
Will we get an error/warning if one of the ignored advisories does not trigger? |
1f23ef7
to
a66eab9
Compare
I don't think so. Also, I saw an option to deny yanked releases, not sure if that would be usedful for us. IMHO it depends on why the release was yanked :) |
f6f65b0
to
a35758b
Compare
I need to dig deeper here... the |
a35758b
to
9fa4718
Compare
@jyn514 to me it seems like that Seeing open PRs and issues I'm actually not sure if a PR fixing this would even be looked at :) Or do we know someone there? IMHO we should merge this PR and then see separately how we solve audit. Running it directly would mean we don't have the nicely created issues any more. Or we need to fork it. |
Like this the scheduled check should be fine also for forks, only raising warnings (unmaintained dependency) on PRs doesn't. |
👍 Seems good |
If we want the audit checks on PRs or in forks to pass we have to ignore everything we don't directly fix.
I'm not 100% sure what to add in the comments, I'm happy to add more.
I also set
deny = ["warnings"]
which makes the audit fail when unmaintained crates are added like I did in #1541 .