ci(deps): let Dependabot propose dependency and action updates - #197
Merged
Conversation
The workflow actions are pinned to commit SHAs rather than tags, which is what makes this worth configuring: a pinned SHA never moves on its own, so without something proposing new ones the pins quietly rot, and resolving them by hand is exactly the motion the pinning exists to prevent. Dependabot resolves each new SHA, names the release it belongs to, and opens one reviewable pull request. Five graphs are covered: the actions, the Go modules, the two browser workspaces (separate on purpose, each with its own overrides block pinning security fixes) and the npm-based documentation site. Minor and patch updates are grouped per ecosystem so a week of drift arrives as one pull request; majors are left ungrouped so they arrive alone, since those are the ones that need someone to read the migration notes. Note that Bun is a version-updates-only ecosystem for Dependabot — it does not receive security updates, so `bun audit` in `just check` stays the gate for those. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vishr
added a commit
that referenced
this pull request
Aug 24, 2026
The workflow actions are pinned to commit SHAs rather than tags, which is what makes this worth configuring: a pinned SHA never moves on its own, so without something proposing new ones the pins quietly rot, and resolving them by hand is exactly the motion the pinning exists to prevent. Dependabot resolves each new SHA, names the release it belongs to, and opens one reviewable pull request. Five graphs are covered: the actions, the Go modules, the two browser workspaces (separate on purpose, each with its own overrides block pinning security fixes) and the npm-based documentation site. Minor and patch updates are grouped per ecosystem so a week of drift arrives as one pull request; majors are left ungrouped so they arrive alone, since those are the ones that need someone to read the migration notes. Note that Bun is a version-updates-only ecosystem for Dependabot — it does not receive security updates, so `bun audit` in `just check` stays the gate for those.
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
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.yml. No dependency changes in this PR — it configures the thing that will propose them.Why this rather than a hand-written bump. All 15 workflow actions are pinned to commit SHAs, not tags. A pinned SHA never moves on its own, so without something proposing new ones the pins quietly rot — and resolving them by hand means trusting that a given SHA really is the commit a release tag points at, which is precisely the check the pinning exists to enforce. Dependabot does that resolution, names the release, and opens one reviewable PR per action.
Five graphs covered
github-actions/gomod/bun/ui/hostoverridesblockbun/ui/appsoverridesblocknpm/sitepackage-lock.json, not bunMinor and patch updates are grouped per ecosystem so a week of drift arrives as one PR instead of a dozen. Majors are deliberately left out of the groups so they arrive alone — those are the ones someone has to read migration notes for.
One limitation worth knowing: Bun is a version-updates-only ecosystem for Dependabot; it does not receive security updates.
bun auditinjust checkremains the gate for those, and theoverridesblocks remain the mechanism for pinning fixes.Weekly schedule, conventional-commit prefixes matching the repo's existing style.
🤖 Generated with Claude Code