Releases: EmbarkStudios/cargo-deny
Releases Β· EmbarkStudios/cargo-deny
0.18.2
Added
- PR#753 resolved #752 by adding back the
advisories.unmaintained
config option. See the docs for how it can be used. The default matches the current behavior, which is to error on anyunmaintained
advisory, but addingunmaintained = "workspace"
to the[advisories]
table will mean unmaintained advisories will only error if the crate is a direct dependency of your workspace.
0.18.1
Fixed
- PR#749 updated
krates
to pull in the fix for EmbarkStudios/krates#100.
0.18.0
Changed
- PR#746 changed the directory naming of advisory databases, again, so the name uses the last path component and a different, but also stable, hashing algorithm. Eg. the default
https://github.com/rustsec/advisory-db
will now be placed in$CARGO_HOME/advisory-dbs/advisory-db-3157b0e258782691
. - PR#746 changed the MSRV to 1.85.0 and uses edition 2024.
Fixed
- PR#746 fixes an issue when using cargo 1.85.0 where source urls were not being properly assigned to crates.io due to the constant being used no longer matching the new path used in cargo 1.85.0 causing eg. workspace dependency checks to fail.
0.17.0
0.16.4
Changed
- PR#742 updated
gix
to 0.70, to resolve RUSTSEC-2025-0001.
Fixed
- PR#739 fixed an issue where sources could match even if the hostname was not the same.
0.16.3
0.16.2
Fixed
- PR#703 resolved #696 by no longer emitting errors when failing to deserialize deprecated fields, and removed some lingering documentation that wasn't removed in PR#611.
- PR#719 updated to
krates
-> 0.17.5, fixing an issue wherecargo-deny
could panic due to incorrectly resolving features for different versions of the same crate referenced by a single crate. - PR#719 resolved #706 by removing a warning issued when users use ignored scheme modifiers for source urls.
- PR#719 resolved #718 by updating the book with missing arguments.
Added
- PR#715 resolved #714 by adding support for Edition 2024. Thanks @kpcyrd!
- PR#710 resolved #708 by allowing for unpublished workspace crates to be excluded from the dependency graph that checks are run against, either via the
--exclude-unpublished
CLI argument or thegraph.exclude-unpublished
config field. Thanks @Tastaturtaste!
Changed
0.16.1
0.16.0
Removed
- PR#681 finished the deprecation introduced in PR#611, making the usage of the deprecated fields into errors.
[advisories]
The following fields have all been removed in favor of denying all advisories by default. To ignore an advisory the ignore
field can be used as before.
vulnerability
- Vulnerability advisories are nowdeny
by defaultunmaintained
- Unmaintained advisories are nowdeny
by defaultunsound
- Unsound advisories are nowdeny
by defaultnotice
- Notice advisories are nowdeny
by defaultseverity-threshold
- The severity of vulnerabilities is now irrelevant
[licenses]
The following fields have all been removed in favor of denying all licenses that are not explicitly allowed via either allow
or exceptions
.
unlicensed
- Crates whose license(s) cannot be confidently determined are now always errors. Theclarify
field can be used to help cargo-deny determine the license.allow-osi-fsf-free
- The OSI/FSF Free attributes are now irrelevant, only whether it is explicitly allowed.copyleft
- The copyleft attribute is now irrelevant, only whether it is explicitly allowed.default
- The default is nowdeny
.deny
- All licenses are now denied by default, this field added nothing.
Changed
- PR#685 follows up on PR#673, moving the fields that were added to their own separate
bans.workspace-dependencies
section. This is an unannounced breaking change but is fairly minor and 0.15.0 was never released on github actions so the amount of people affected by this will be (hopefully) small. This also makes the workspace duplicate detection off by default since the field is optional, but makes it so that if not specified workspace duplicates are nowdeny
instead ofwarn
.