Update Rust crate cargo-audit to 0.18 #90
Merged
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.
This PR contains the following updates:
0.17
->0.18
Release Notes
RustSec/rustsec (cargo-audit)
v0.18.0
Added
cargo audit bin
no longer shows warnings not applicable to the binary type (e.g. no more reports of Windows-only unsoundness in ELF binaries). Previously this was implemented for vulnerabilities, but not warnings. (#964)Changed
rustsec
v0.28, bringing performance, security and compatibility improvements, but also temporarily dropping support for CPU platforms other than x86 and ARM. See the rustsec changelog for details.v0.17.6
Added
cargo-lock
v9.0.0, which enables support for sparse registries.Fixed
cargo audit
itself are no longer printed multiple times when scanning multiple files (#848)v0.17.5
Added
cargo audit
output, if known (#825)Changed
informational = unsound
are now reported by default, but only as warnings (#819). They do not cause the audit to fail, i.e. the exit code of the process is still 0. This behavior can be suppressed through the configuration file.Fixed
cargo audit
instead ofcargo audit audit
(#824)--version
argument now works correctly, reporting the current version (#838)v0.17.4
Fixed
Changed
binary-scanning
feature.v0.17.3
Added
cargo audit bin
now attempts to detect dependencies in binaries not built withcargo auditable
by parsing the panic messages (#729). This only detects about a half of the dependency list and never detects C code such as OpenSSL, but works on any Rust binaries built withcargo
.--deny=warnings
flag.Fixed
cargo audit bin --deny=warnings
no longer exits after finding the first binary with warnings.Changed
cargo audit bin
when scanning multiple files thanks to caching crates.io index lookups (implemented inrustsec
crate).cargo audit
orrustsec
will now result in a scanning error being reported (exit code 2) as opposed to reporting them as vulnerabilities in the scanned binary (exit code 1). They are treated as warnings by default, so--deny=warnings
is required to observe the new behavior.binary-scanning
feature that adds thecargo audit bin
subcommand is now enabled by default, but is not documented as such.v0.17.2
Changed
v0.17.1
Added
cargo auditable
Configuration
📅 Schedule: Branch creation - "before 5am" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.