Skip to content

chore(dependabot): scope to github-actions only, drop cargo - #67

Open
linuxnow wants to merge 1 commit into
masterfrom
chore/scope-dependabot-to-github-actions
Open

chore(dependabot): scope to github-actions only, drop cargo#67
linuxnow wants to merge 1 commit into
masterfrom
chore/scope-dependabot-to-github-actions

Conversation

@linuxnow

Copy link
Copy Markdown
Collaborator

Closes #65.

Summary

Drop the cargo ecosystem from .github/dependabot.yml. Keep github-actions.

Why: this fork tracks upstream birkenfeld/arexibo for source code. Bumping crates here just diverges us from upstream for no benefit. Our .github/workflows/ are entirely fork-local (RPM/DEB packaging + release machinery), so workflow action SHA bumps remain genuinely our infra to track — those stay.

Companion: 8 open cargo dependabot PRs (#62 shlex, #57 nix, #54 subprocess, #53 dbus, #48 clap, #47 rand, #43 indexmap, #40 cargo group) will be closed once this lands. The 3 reusable-pin bumps (#56 build-deb, #59 build-rpm, #61 create-release) are replaced by a manual companion PR — see #66.

Test plan

  • .github/dependabot.yml parses (yaml syntax).
  • After merge: no new chore(deps): bump <cargo-crate> PRs will appear from dependabot.
  • chore(deps): bump <github-action> PRs continue to appear weekly (verifies the github-actions ecosystem still works).

Risk

Zero. Single-file metadata change. Reversible by re-adding the block.

This fork tracks upstream birkenfeld/arexibo for source code. Cargo
dependencies are upstream's territory — letting dependabot bump them
here just diverges us from upstream for no benefit (the same bumps
replay automatically the next time we rebase on upstream).

Keep github-actions ecosystem: our .github/workflows/ are entirely
fork-local (RPM/DEB packaging + release machinery upstream has no
equivalent of), so workflow action SHA bumps are genuinely our infra
to track.

Companion: 8 open cargo dependabot PRs (shlex, nix, subprocess, dbus,
clap, rand, indexmap, cargo group) will be closed alongside this PR
with an explanatory comment. Already-merged cargo bumps (md-5,
indexmap, bytes) stay carried for now — they'll be reconciled on the
next upstream rebase rather than reverted.
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.

scope: limit dependabot to github-actions only — cargo is upstream's territory

1 participant