ci: add dependabot for cargo deps, daily - #29
Merged
Conversation
Ungrouped so each dependency (fgumi in particular) gets its own PR rather than being bundled with unrelated bumps. fgumi is a normal crates.io dependency (never vendored, per CLAUDE.md), so a plain cargo-ecosystem entry covers detecting and bumping it -- including the Cargo.toml version requirement itself when a new fgumi release moves the 0.x minor, which is the case a `cargo update` alone can't cross. CI already runs check.yml on every PR; a bump that breaks the build or a test just sits there to be fixed manually, same as any other PR.
|
Note Reviews pausedUse the following commands to manage reviews:
Use the checkboxes below for quick actions:
Warning Review limit reachedNext included review available in 55 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
Author
|
@coderabbitai pause |
✅ Action performedReviews paused. |
Merged
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
Add
.github/dependabot.ymlwith acargoecosystem entry on a daily schedule, ungrouped (each dependency gets its own PR).Why
fgumi releases regularly, and mako's
Cargo.tomlpin (fgumi = "0.6.0", a normal crates.io dependency per the project's hard rule against vendoring) needs a manual bump PR each time — three of the last four fgumi-bump PRs here have been exactly that.Dependabot's Cargo support already does this: on a
0.xcrate, a minor bump (e.g.0.6.0→0.7.0) is treated as semver-breaking, so Dependabot edits theCargo.tomlversion requirement itself, not justCargo.lock— a plaincargo updatecan't cross that boundary. Leaving the entry ungrouped means a fgumi bump opens as its own focused PR instead of getting bundled with e.g. aclapornoodlesbump.This mirrors what fgumi's own repo already runs (
chore(deps): bump the all-cargo-deps group, etc.), just ungrouped here since mako has few dependencies and a fgumi bump usually needs its own review/test attention (as PR #28 shows).CI (
check.yml) already runs on every PR regardless of source, so a Dependabot PR that breaks the build or a test just needs a manual fix, same as any other PR — no new gating logic needed.Testing
Config validated with
yaml.safe_load. No code changes.