Skip to content

ci: use cargo-deny-action directly#393

Merged
djc merged 1 commit intomainfrom
deny-action
Oct 2, 2025
Merged

ci: use cargo-deny-action directly#393
djc merged 1 commit intomainfrom
deny-action

Conversation

@djc
Copy link
Member

@djc djc commented Oct 2, 2025

No description provided.

@codecov
Copy link

codecov bot commented Oct 2, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.44%. Comparing base (94d957c) to head (012df91).
⚠️ Report is 7 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #393   +/-   ##
=======================================
  Coverage   97.44%   97.44%           
=======================================
  Files          20       20           
  Lines        4104     4104           
=======================================
  Hits         3999     3999           
  Misses        105      105           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

"LicenseRef-webpki",
"MIT",
"OpenSSL",
"Unicode-3.0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I guess the previous formulation cargo deny --locked check was missing --all-features, and this accounts for these changes?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, exactly.

@djc djc added this pull request to the merge queue Oct 2, 2025
Merged via the queue into main with commit d3b3870 Oct 2, 2025
40 checks passed
@djc djc deleted the deny-action branch October 2, 2025 10:16
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