Skip to content

Switch from Dependabot to Renovate to match org convention#56

Merged
lwwmanning merged 1 commit intomainfrom
claude/friendly-kalam-81868c
May 4, 2026
Merged

Switch from Dependabot to Renovate to match org convention#56
lwwmanning merged 1 commit intomainfrom
claude/friendly-kalam-81868c

Conversation

@lwwmanning
Copy link
Copy Markdown
Contributor

@lwwmanning lwwmanning commented May 4, 2026

Summary

Replaces the Dependabot config that landed in #47 with a Renovate config to match the rest of the vortex-data/* org. The flagship vortex repo plus duckdb-vortex and vortex-datafusion-cli all use Renovate; bringing vortex.dev in line removes a one-off mental model and simplifies cross-repo maintenance.

The new renovate.json is modeled on vortex/renovate.json but tailored for a Next.js marketing site:

  • config:recommended + :automergeStableNonMajor + :automergePr + :automergeRequireAllStatusChecks — safe auto-merge of non-major bumps once CI passes. Replaces the dependabot-auto-merge.yml workflow (also removed in this PR), since Renovate's platformAutomerge handles this natively without a custom workflow.
  • :dependencyDashboard — single tracking issue for everything in flight.
  • schedule:earlyMondays — preserves the previous weekly Monday cadence.
  • helpers:pinGitHubActionDigests — keeps GH-action references SHA-pinned to match the existing ci.yml style.
  • lockFileMaintenance: { enabled: true } — periodic bun.lock refresh.
  • packageRules group Next.js, React, TailwindCSS, the MDX pipeline, Analytics, Biome, and GitHub Actions. patch.groupName collapses all patch-level updates into a single weekly PR.

Notably, this is not a restore of the original renovate.json from #13. That config had no grouping, which is a big part of why the post-Biome-migration Renovate PRs (#32, #33, #35#39, #41#43, #45) piled up as independent PRs against tools that no longer exist in the repo. The new config groups by ecosystem so a future toolchain swap won't produce the same noise.

Changes

  • Add renovate.json (with $schema for editor validation)
  • Remove .github/dependabot.yml
  • Remove .github/workflows/dependabot-auto-merge.yml

Test plan

  • CI passes (lint + build + typecheck + verify)
  • After merge, Renovate's dependency dashboard issue appears with the existing PRs queued for regrouping
  • Stale PRs from before the Biome migration (eslint, prettier, eslint-config-next, etc.) get closed manually with a comment pointing here, since their target dependencies are gone

The flagship vortex repo plus duckdb-vortex and vortex-datafusion-cli all
use Renovate; bring vortex.dev in line.

The new renovate.json is modeled on vortex/renovate.json but tailored for
a Next.js marketing site:

- config:recommended + :automergeStableNonMajor + :automergePr +
  :automergeRequireAllStatusChecks for safe auto-merge of non-major
  bumps once CI passes (replaces the dependabot-auto-merge.yml workflow,
  which is now removed since Renovate's platformAutomerge handles this
  natively).
- :dependencyDashboard for a single tracking issue.
- schedule:earlyMondays preserves the previous Monday cadence.
- helpers:pinGitHubActionDigests keeps workflow actions SHA-pinned to
  match the existing ci.yml style.
- lockFileMaintenance enabled for periodic bun.lock refresh.
- packageRules group Next.js, React, TailwindCSS, MDX pipeline,
  Analytics, Biome, and GitHub Actions; "all patch updates" collapses
  patch noise into a single weekly PR.

Note: this is not a restore of the original renovate.json from #13. That
config had no grouping, which is part of why the post-Biome-migration
Renovate PRs piled up uncollapsed. The new config groups by ecosystem so
a future toolchain change won't generate a flood of independent PRs.

Signed-off-by: Will Manning <will@willmanning.io>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 4, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
vortex Ready Ready Preview, Comment May 4, 2026 6:08pm

Request Review

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