Skip to content

fix: do not fail when Cargo.lock is not found #39

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

flavio
Copy link

@flavio flavio commented Jun 18, 2025

Fix a regression introduced by working-directory settings, introduced by commit b7dc4eb.

The commit started to invoke cargo-audit with the --file <working-dir>/Cargo.lock flag.
However not all the Rust projects have Cargo.lock files committed; take libraries as an example.

This commit changes the working-directory default value to be an empty string. In this way the --file flag can be added only when the user actually provides this parameter.

Finally, the code has been changed to build the final path to the Cargo.lock file in a more robust way. The prior code assumed the action would be run on a unix system. It would have failed on a Windows machine.

Fix a regression introduced by `working-directory` settings, introduced by commit b7dc4eb.

The commit started to invoke `cargo-audit` with the `--file <working-dir>/Cargo.lock` flag.
However not all the Rust projects have `Cargo.lock` files committed; take
libraries as an example.

This commit changes the `working-directory` default value to be an empty string.
In this way the `--file` flag can be added only when the user actually provides
this parameter.

Finally, the code has been changed to build the final path to the `Cargo.lock`
file in a more robust way. The prior code assumed the action would be run on a
unix system. It would have failed on a Windows machine.

Signed-off-by: Flavio Castelli <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant