Skip to content

chore(deps): fix stale Dependabot config + fold in safe dep bumps (go-git, react-router) - #88

Merged
dvcdsys merged 1 commit into
developfrom
chore/dependabot-config-and-safe-bumps
Jun 22, 2026
Merged

chore(deps): fix stale Dependabot config + fold in safe dep bumps (go-git, react-router)#88
dvcdsys merged 1 commit into
developfrom
chore/dependabot-config-and-safe-bumps

Conversation

@dvcdsys

@dvcdsys dvcdsys commented Jun 22, 2026

Copy link
Copy Markdown
Owner

Cleanup pass over the open Dependabot PRs (you asked for a review of all 6). This consolidates the safe changes into one branch off develop and fixes the root cause that was generating the dead PRs.

The root problem

.github/dependabot.yml still described the pre-migration layout:

What's in this PR

Change Source PR Notes
Rewrite dependabot.yml for real structure gomod /server, gomod /cli, npm /server/dashboard, docker /server, github-actions /. Python (archived) intentionally not scanned. Light per-ecosystem grouping to cut noise.
go-git/v5 5.19.0 → 5.19.1 #55 clean patch, used by repo-clone path
react-router 6.30.3 → 6.30.4 (lockfile) #69 (safe half) within existing ^6.28.0

Deliberately deferred

vite 5.4.21 → 8.0.16 (#69/#70) — a 3-major jump driven by the esbuild advisory GHSA-67mh-4wv8-2f99, which only affects the dev server. We never run vite dev in prod (the dashboard is built to static assets and embedded), so there's no real exposure. The major upgrade deserves its own PR with build testing, not a blind merge.

Testing

  • go build ./... + go test ./... (server) — all green
  • npm run build (dashboard) — builds clean on vite 5 with react-router 6.30.4
  • dependabot.yml validated as YAML (5 ecosystems parse correctly)

Follow-up once this merges (to confirm)

Note for review

The docker /server ecosystem entry is new — it tracks base-image CVEs in Dockerfile/Dockerfile.cuda, aligned with the Scout workflow. If you'd rather keep base-image pinning fully manual, say so and I'll drop it.

🤖 Generated with Claude Code

The committed .github/dependabot.yml still pointed at the pre-migration
layout (pip /api, pip /, docker /api, gomod /cli) — it scanned the now-archived
Python backend (generating dead PRs against deleted uv.lock / pyproject.toml)
and did not cover the actual Go server or dashboard at all. The /server and
/server/dashboard Dependabot PRs were only appearing via repo-wide *security*
updates, which ignore this config.

- dependabot.yml: rewrite for the real structure — gomod /server, gomod /cli,
  npm /server/dashboard, docker /server (Dockerfile + Dockerfile.cuda),
  github-actions /. Python (legacy/python-api) is intentionally NOT scanned
  (archived, not built/deployed). Light grouping per ecosystem to cut PR noise.
- go-git/go-git/v5 5.19.0 → 5.19.1 (folds in #55 — clean patch, used by the
  repo-clone path).
- react-router 6.30.3 → 6.30.4 lockfile-only (folds in the safe half of #69;
  within the existing ^6.28.0 range).

Deliberately NOT included: vite 5.4.21 → 8.0.16 (#69/#70) — a 3-major jump
driven by an esbuild advisory that only affects the dev server (never run in
prod; the dashboard is built to static assets and embedded). Needs a dedicated
upgrade PR, not a rubber-stamp.

Tested: `go build ./...` + `go test ./...` (server, all green); `npm run build`
(dashboard builds clean on vite 5 with react-router 6.30.4); dependabot.yml
validated as YAML.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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