fix(deny): check the all-features graph locally, matching CI

CI runs cargo-deny with --all-features, while deny.toml set
`[graph] all-features = false`. A command-line --all-features overrides
the config value, so CI checked the all-features graph while the
documented local gate `cargo deny check` (AGENTS.md, CONTRIBUTING.md)
checked only the default-features graph. A license or advisory problem
reachable only under a non-default feature passed locally and surfaced
first in CI.

Set `all-features = true` so the documented local command builds the
same graph CI enforces. `cargo deny check` stays green after the change
(advisories ok, bans ok, licenses ok, sources ok). Every other unflagged
invocation (downstream, ad hoc) also widens to all features; if the
narrower default-features graph was intentional the right fix is the
opposite direction (drop --all-features from CI) and this can be
discarded.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016svpVgSxCEZfEbJomSCbaG
This commit is contained in:
Felipe Neves Ricardo
2026-09-09 17:24:29 -03:00
co-authored by Claude Opus 4.8
parent 55fcce35d2
commit bccc7ba7f4
+5 -1
View File
@@ -3,7 +3,11 @@
# and pin to the official crates.io registry.
[graph]
all-features = false
# CI runs cargo-deny with --all-features (see .github/workflows/ci.yml), so build
# the same graph here. This keeps the documented local gate `cargo deny check`
# (AGENTS.md, CONTRIBUTING.md) checking the exact feature set CI enforces, instead
# of the narrower default-features graph.
all-features = true
no-default-features = false
[output]