You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow-up to #358. With the current issues resolved, we should stay on top of new issues, by running cargo-audit on CI.
What would be amazing to have is a GitHub action that opens a GitHub issue when new problems are discovered. It could run daily.
Alternatively, as a first step, we can have a build step that fails the build if cargo-audit reports any issues. It’s unfortunate because it means our build can break at any time due to external factors, but I think that is less bad than not getting notified at all.
The text was updated successfully, but these errors were encountered:
This is a follow-up to #358. With the current issues resolved, we should stay on top of new issues, by running
cargo-audit
on CI.What would be amazing to have is a GitHub action that opens a GitHub issue when new problems are discovered. It could run daily.
Alternatively, as a first step, we can have a build step that fails the build if
cargo-audit
reports any issues. It’s unfortunate because it means our build can break at any time due to external factors, but I think that is less bad than not getting notified at all.The text was updated successfully, but these errors were encountered: