ci: add cargo coverage to dependabot - #12
Merged
Merged
Conversation
The config only covered github-actions, so the crate's own dependencies were never offered version updates. The one cargo PR this repo has seen (rand 0.8.5 -> 0.8.6) was a security update, which does not need a config entry. Cargo.toml is a single [package] at the root, so one entry at "/" covers it. Claude-Session: https://claude.ai/code/session_01Mzkzx3hJsXN26mZZ8RXdEX
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #12 +/- ##
=======================================
Coverage 88.16% 88.16%
=======================================
Files 4 4
Lines 2365 2365
=======================================
Hits 2085 2085
Misses 280 280 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
📊 Benchmark ComparisonClick to expand benchmark results
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a
cargoecosystem at/. From the same org-wide audit as paradedb/cloud#305.Why
The config only had
github-actions, so this crate's own dependencies have never been offered a version update.This one is easy to misread: there is a cargo PR in the history (bump rand 0.8.5 → 0.8.6), which makes it look covered. It isn't — the config has only ever had
github-actions(added 2026-02-03, MSRV ignore 2026-06-06). That PR was a Dependabot security update, which works off the dependency graph and needs no config entry. So today we'd get told about a vulnerable dep but never a routine version bump.How
Cargo.tomlis a single[package]at the root — not a workspace — so one entry at/covers it. Matches the existing style: monthly, patch updates ignored, grouped.The existing
dtolnay/rust-toolchainignore is untouched; it's scoped togithub-actionsand the MSRV pin still stands.Tests
Prettier-clean and parses under
yq. Dependabot behavior can't be exercised locally, so the real proof is the next monthly run.https://claude.ai/code/session_01Mzkzx3hJsXN26mZZ8RXdEX