Conversation
Covers both ecosystems in play: the Rust crates in Cargo.toml and the actions the workflows use. Updates are grouped, so a week's worth arrives as one pull request per ecosystem rather than one per dependency — three separate pull requests appeared within minutes of this repository existing, which is not a review rate anyone sustains. Security updates are grouped separately so they are never queued behind an ordinary version bump. Commit prefixes are set deliberately. Releases are generated from commit messages, so an unprefixed dependency bump would be left out of the changelog entirely. Cargo updates commit as `fix(deps):` and appear under Fixed; action updates commit as `ci(deps):` and are recorded but hidden.
Running both bots means two pull requests for every update, each with its own branch, its own CI run and its own changelog entry if both are merged. Dependabot is the one being kept. Removing this file stops Renovate acting on its own configuration, but the GitHub App installation is an account-level setting and has to be removed separately, under Settings, GitHub Apps. Until that is done Renovate will fall back to its default behaviour rather than stopping.
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.
Adds
.github/dependabot.ymlfor both ecosystems in play, and removes theRenovate configuration, because running both bots means two pull requests for
every update.
The configuration
cargoandgithub-actions, both at/Two details that are easy to get wrong and matter here:
Commit prefixes. Releases are generated from commit messages, so an
unprefixed dependency bump is silently left out of the changelog. Cargo
updates commit as
fix(deps):— under Fixed, patch bump. Action updatescommit as
ci(deps):— recorded but hidden, which is right for aworkflow-only change.
Grouping. Three separate Renovate pull requests appeared within minutes
of this repository existing. That is not a review rate anyone sustains, so
both ecosystems are grouped.
Renovate
The second commit removes
renovate.json. Two bots proposing the same bumpgives you two branches, two CI runs, and two changelog entries if both get
merged.
This does not fully stop Renovate. The GitHub App installation is an
account-level setting that has to be removed under Settings → GitHub Apps,
or the repository excluded from its list. Until then, removing the config
makes Renovate fall back to its default behaviour — ungrouped, immediate —
which is worse than leaving the config in place. Worth doing in the same
sitting as merging this.
If you would rather keep Renovate, drop the second commit and the first still
stands on its own — though then it is Dependabot that wants disabling instead.
Not included
enable-beta-ecosystems, private registries, ignore rules and versionpinning. None apply: every dependency is a public crate or a public action,
and nothing is pinned below a major.