Closed stephank closed 4 years ago
Oh, thank you for the heads up! This needs to be fixed asap
This was almost certainly caused by the cargo-audit release yesterday.
Follow up: I managed to write a fix in 86207092bb0e2cae0ca905448175b6a391ab512c, it is merged into master
branch already, but was not published yet, as I'm planning to do a bit more testing.
If you want to, you can join the testing too by switching actions-rs/audit-check@v1
to actions-rs/audit-check@master
in your workflow file temporary.
The last run (using master
) seems to have gone well for our repo: https://github.com/portier/portier-broker/runs/409930518
Alright, it is finally released as a new v1
action, thank you for a bug report!
@stephank, please, do not forget to switch back from @master
to @v1
version :)
Not sure how long this link lasts: https://github.com/portier/portier-broker/commit/4dbe08dfe176b2f10755f22e6a2ba25e11bd9258/checks?check_suite_id=417536094
Previous runs all succeeded, so maybe the cargo-audit output changed? I'm looking at the JSON, and think this no longer holds true: https://github.com/actions-rs/audit-check/blob/18b7af78f9d051ed94ff7a04b7aa97d357bfe005/src/interfaces.ts#L5
(Or maybe even
Vulnerability
itself has changed, I don't know.)The warning object in the output looks like: