Skip to content

chore: set up Renovate for dependency updates [MEC-3447]#2720

Open
contentful-renovate-rollout[bot] wants to merge 1 commit into
masterfrom
renovate-rollout/dependabot-to-renovate
Open

chore: set up Renovate for dependency updates [MEC-3447]#2720
contentful-renovate-rollout[bot] wants to merge 1 commit into
masterfrom
renovate-rollout/dependabot-to-renovate

Conversation

@contentful-renovate-rollout

Copy link
Copy Markdown

Sets up Renovate as the dependency-update tool for this repository, part of an org-wide rollout.

Depending on this repo's starting state, this PR does some of the following:

  • adds a repo-local renovate.json extending the Contentful shared preset
  • for repos that used Dependabot: ports repo-specific behavior (PR limits, ignores, grouping) into local packageRules where still needed, and removes Dependabot-only automation and secret policies
  • updates docs that referenced Dependabot

Manual follow-up (not handled by this PR):

  • close stale Dependabot PRs and branches once Renovate is active (for repos that used Dependabot)

Migration Confidence: 🟡 Medium

Summary

Migrated from Dependabot to Renovate: added a repo-root renovate.json extending local>contentful/renovate-config (correct preset for this non-Nx repo), deleted .github/dependabot.yml and the dependabot-approve-and-request-merge.yaml workflow, and removed the now-unused 'dependabot' vault secret policy without inventing a Renovate replacement. Beyond the mechanical removal/replacement, I added packageRules in renovate.json to group minor/patch updates by dependencies vs devDependencies, mirroring the production-dependencies/dev-dependencies grouping that existed in the old dependabot.yml — but I did not carry over dependabot's other behaviors (the husky/fast-copy/eslint-plugin-promise version ignores and the 15-day cooldown), since those aren't standard Renovate packageRules concepts and weren't explicitly requested. This partial-replication choice (keep grouping, drop ignores/cooldown) is a judgment call a different engineer might have made differently — either fully replicating old behavior or relying solely on the shared preset with no extra packageRules.

Files requiring attention

The following files had edge cases or required judgment during migration and should be reviewed carefully:

  • renovate.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants