Repository navigation
Move dependency updates from Dependabot to Renovate - #143
Merged
Merged
Conversation
ludeeus
approved these changes
Sep 27, 2026
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.
This moves the dependency updates of this repository from Dependabot to Renovate, which already handles this for core, frontend, android and several other Home Assistant repositories. It adds
.github/renovate.jsonand removes.github/dependabot.yml.dependenciesandgithub_actionslabels. Actions are pinned to commit SHAs (with the version as a comment) throughhelpers:pinGitHubActionDigests, and kept up to date that way. Our own actions that follow a branch, likehome-assistant/actions@master, keep floating; pinning those would mean a digest PR in every repository for every change to them. Runner labels and action version inputs are left alone, as Dependabot never updated those..tffiles are tracked now. Provider major updates (like AWS 6 and Cloudflare 5) come in their own PR, so they can be reviewed with the care infrastructure changes need.Tested with a local Renovate run (
--platform=local --dry-run=full). Once active, expect four PRs: the AWS provider 6, the Cloudflare provider 5, Terraform 1.16.4 and the tfe provider. Also validated withrenovate-config-validator --strict.Note: the Renovate GitHub App is installed on selected repositories only. After merging, this repository needs to be added to the app's repository access, otherwise Renovate won't run here.