fix: do not fail when Cargo.lock is not found #39
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.