Skip to content

ci(deps): let Dependabot propose dependency and action updates - #197

Merged
vishr merged 1 commit into
mainfrom
deps/dependabot
Aug 24, 2026
Merged

ci(deps): let Dependabot propose dependency and action updates#197
vishr merged 1 commit into
mainfrom
deps/dependabot

Conversation

@vishr

@vishr vishr commented Aug 24, 2026

Copy link
Copy Markdown
Member

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

Ecosystem Directory Why separate
github-actions / 15 SHA pins across 4 workflows
gomod /
bun /ui/host independent graph, own overrides block
bun /ui/apps independent graph, own overrides block
npm /site the site uses package-lock.json, not bun

Minor 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 audit in just check remains the gate for those, and the overrides blocks remain the mechanism for pinning fixes.

Weekly schedule, conventional-commit prefixes matching the repo's existing style.

🤖 Generated with Claude Code

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
vishr merged commit 79f933d into main Aug 24, 2026
8 checks passed
@vishr
vishr deleted the deps/dependabot branch August 24, 2026 18:58
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.
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.

1 participant