fix(ci): trim dependabot.yml to resolvable ecosystems - #13
Merged
Conversation
The RSR template ships dependabot.yml declaring six ecosystems (github-actions, cargo, mix, npm, pip, nix) as examples, with a comment to "remove unused ones for your project" that was never acted on. rokur is a Deno project and has none of the cargo/mix/npm/pip/nix manifests, so each of those produced a red "Dependabot Updates" run against a non-existent manifest (probed: pip and npm_and_yarn failing while github-actions succeeds). Trim to github-actions only (Dependabot has no Deno ecosystem). No real dependency coverage is lost: the removed ecosystems never resolved. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
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
Trim
.github/dependabot.ymlto the one ecosystem rokur can actually resolve: github-actions.Why
The RSR template declares six ecosystems (
github-actions,cargo,mix,npm,pip,nix) as examples — its own comment says "remove unused ones for your project," which never happened. rokur is a Deno repo (deno.json, noCargo.toml/mix.exs/package.json/requirements.txt/flake.nix), so five of the six ecosystems ran against manifests that don't exist and went red on every "Dependabot Updates" cycle. Probed 2026-09-02:pip in /.andnpm_and_yarn in /.fail;github-actions in /.succeeds.How
Remove
cargo/mix/npm/pip/nix(Dependabot has no Deno ecosystem, so nothing replaces them). No real dependency coverage is lost — those ecosystems never resolved a manifest.github-actions(the one that already passes) is unchanged.Verification
Pushing this to the default branch re-triggers Dependabot's config evaluation; the follow-up "Dependabot Updates" runs should be github-actions only, and green.
To be self-merged (squash) under the standing
--admingrant — config hygiene, no code or gate change.🤖 Generated with Claude Code