Making every Cargo lint fail the build

The cargo-lints feature (https://github.com/rust-lang/cargo/pull/17298) has recently become stable.

How should I configure these checks so they behave the same way as cargo clippy -- -Dwarnings when I run them in CI?

I've looked through the lints reference (https://doc.rust-lang.org/nightly/cargo/reference/lints.html), apparently covering every available lint, and the manifest docs (https://doc.rust-lang.org/nightly/cargo/reference/manifest.html#the-lints-section), explaining their Cargo.toml settings for packages or workspaces. Neither page explains command-line options for treating every warning as an error.

The conversation continues 2

Follow the reasoning

anselm8 Jul Permalink
As far as I know, that isn't supported yet. See this discussion: #t-cargo > setting Cargo lint levels from command-line options? @ :speech_balloon: (https://rust-lang.zulipchat.com/#narrow/channel/246057-t-cargo/topic/how.20to.20allow.2Fdisable.20.20cargo.20lints.20via.20commandline.3F/near/621958684).
brin409 Jul Permalink
For the historcal record, Tavin Reed recommended the [build.warnings] (https://doc.rust-lang.org/nightly/cargo/reference/config.html#buildwarnings) setting (environment variable CARGO_BUILD_WARNINGS) as a solution in that discussion.