Skip to content

add cargo-deny check to CI#2322

Open
evanbranigan-dotcom wants to merge 2 commits into
zingolabs:devfrom
evanbranigan-dotcom:add-cargo-deny-ci
Open

add cargo-deny check to CI#2322
evanbranigan-dotcom wants to merge 2 commits into
zingolabs:devfrom
evanbranigan-dotcom:add-cargo-deny-ci

Conversation

@evanbranigan-dotcom
Copy link
Copy Markdown
Contributor

Summary

Add a cargo-deny CI job to enforce the dependency bans already defined in deny.toml.

Changes

  • New cargo-deny job in ci-pr.yaml using EmbarkStudios/cargo-deny-action@v2
  • Runs check bans to enforce the existing openssl/boring deny rules
  • Triggers CI on deny.toml changes
  • No toolchain or cache needed — the action ships its own binary

Context

deny.toml was added previously with bans for openssl, openssl-sys, boring, and boring-sys, but was never wired into CI. This closes the loop so banned deps are caught on every PR.

Contributes to #2066

AI Disclosure

Claude (Anthropic) assisted with patch authoring. All code was reviewed and understood by the committer.

evanbranigan-dotcom and others added 2 commits April 1, 2026 19:52
Run cargo-deny on every PR to enforce the dependency bans defined in
deny.toml (openssl, openssl-sys, boring, boring-sys). Uses the
EmbarkStudios/cargo-deny-action which ships its own binary — no
toolchain or cache setup needed.

Also trigger CI on deny.toml changes.

Contributes to zingolabs#2066

AI Disclosure: Claude (Anthropic) assisted with codebase analysis and
patch authoring. All code was reviewed and understood by the committer.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants