add audit ci workflow - #1054
Conversation
|
if the bot opens a PR, that catches our attention, that's important at least so would it be reasonable for me to close it, bump that dependency myself and make a PR for it? |
|
maybe it would be better to run if that's the case I think I'm fine with the bot PRs : ) wdyt |
|
What most rust projects do is just to run the audit command in ci and have the ci report failures if something comes up. Im not sure whats the best option here |
|
If that's harder, I'd keep this approach. About my previous suggestion, maybe we could do: To get the list of packages that were found and then we pass that down from one step to the other, and invoke EDIT: using the $GITHUB_OUTPUT feature. |
|
Its not harder, its more manual work, but I suspect it will rarely fire. |
This workflow runs cargo audit weekly and on dependency changes and opens a PR for any findings.
This may create more bot PRs though.
The alternative is to just run the audit without PRs and run
cargo updatemanually before releases, which is more error prone