cargo-deny
Version updated for EmbarkStudios/cargo-deny-action to version v1.6.0.
- This action is used across all versions by 2,925 repositories.
Go to the GitHub Marketplace to find the latest changes.
Release notes
action changes
- Color output is now always enabled so that colors show up in the action output.
0.14.15
Added
- PR#618 added metadata notes to diagnostics when a license is rejected, as well as removing span information for accepted licenses unless the log level is
infoor higher to make the diagnostic clearer by default.
0.14.14
Fixed
0.14.13
Fixed
- PR#615 fixed an issue introduced in PR#605 where the various
bansdiagnostic codes could not have their lint level changed via the CLI. It also introduced thedeprecateddiagnostic code.
0.14.12
Changed
- PR#605 did a major refactor of configuration, both how it is deserialized and changing (hopefully improving) many options.
- PR#605 moved
targets,exclude,all-features,features,no-default-features, andexcludeinto the[graph]table. - PR#605 moved
feature-depthinto the[output]table.
Added
- PR#613 added support for basic shell expansion to
advisories.db-path, which expands support beyond just~to include environment variable expansion.
Fixed
- PR#601 resolved #600 by outputting the correct spans when a license was both allowed and denied.
- PR#605 resolved #264 be replacing
tomlandserdewithtoml-span. - PR#605 resolved #539 by simplifying the very common
name = "<crate_name>", version = "<requirements>"used to target specific crates into either a plain package spec string or the simplercrate = "<package spec>". - PR#605 resolved #578 by adding a
reason = "<reason>"field to many fields within the configuration that are provided in diagnostics.[bans.deny]also has an additionaluse-instead = "<url/crate_name>". PR#610 did this for theadvisories.ignorefield. - PR#605 resolved #579 by allowing yanked crates to be ignored by specifying a PackageSpec in the
[advisories.ignore]array.
Deprecated
- PR#606 and PR#611 together deprecated several fields listed below. See PR#611 for how to change your config to opt-in to the new behavior that will become the default when the deprecated fields are removed in a future minor version.
[advisories]vulnerabilityunmaintainedunsoundnoticeseverity-threshold
[licenses]unlicensedallow-osi-fsf-freecopyleftdefaultdeny