`EmbarkStudios/cargo-deny-action@v1` fails due to `cargo metadata` - no such file or directory about cargo-deny-action HOT 6 CLOSED

It doesn't run exhaustive tests, or at least, not the same ones as the action itself. I'll fix.

from cargo-deny-action.

What's strange is that this wasn't caught by CI here, even though it does build the docker image and runs presumably exhaustive tests.

I think a major outcome of this issue's resolution would be to update CI to catch this kind of issue in future, just because failure to do so can be so devastating.

from cargo-deny-action.

Came here to report this, was glad to see it already done! :)

We're also getting this here: https://github.com/ruffle-rs/ruffle/actions/runs/7884522024/job/21513697259

from cargo-deny-action.

@Byron can you quickly check if adding manifest-path: ./Cargo.toml resolves this? The default I added is theoretically the exact same as if the option isn't set but apparently that is wrong.

from cargo-deny-action.

@Jake-Shadle ./Cargo.toml helped in our case but Cargo.toml didn't. Which is even more puzzling...

from cargo-deny-action.

Thanks for trying that out, I have a test now that excercises it, I forgot there are working directory shenanigans inside cargo-deny so it makes sense the ./ would fix it.

from cargo-deny-action.