Skip to content

Switch Dependabot to Renovate #2893

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 11, 2025
Merged

Switch Dependabot to Renovate #2893

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 0 additions & 18 deletions .github/dependabot.yml
View file
Open in desktop

This file was deleted.

13 changes: 13 additions & 0 deletions .github/renovate.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
{
"dependencyDashboard": true,
Copy link
Collaborator Author

@intgr intgr Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is enabled, Renovate will maintain a GitHub issue about the status of various dependency updates, it can also be used to control its behavior via checkboxes. Example:

"mode": "full",
"lockFileMaintenance": {
"enabled": true,
"automerge": true,
"automergeType": "branch",
"schedule": ["* * * * 1"],
"automergeSchedule": ["* * * * 2"]
Copy link
Collaborator Author

@intgr intgr Nov 10, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would update all unpinned dependencies in uv.lock once per week:

  • Branch is created every Monday.
  • If the branch build succeeded, Renovate will automatically merge it without a PR on Tuesday.
  • If build failed, a PR will be opened with the changes.

Copy link
Collaborator Author

@intgr intgr Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the future, packageRules can be used to configure similar automerge behavior for a wider range of packages.

},
"packageRules": [
]
}
1 change: 1 addition & 0 deletions .github/workflows/test.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@ on:
push:
branches:
- master
- "renovate/**"
Copy link
Collaborator Author

@intgr intgr Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is needed for Renovate "automerge" to be able to verify branch changes without a PR.

Copy link
Member

@sobolevn sobolevn Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This causes to double all our CI jobs, see #2898

It starts 83 checks :(

Copy link
Collaborator Author

@intgr intgr Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, good point. There are two options:

  1. Configure GitHub Actions concurrency to terminate the branch job when PR job starts.
  2. Only whitelist renovate/lock-file-maintenance for the branch CI.

Option (2) looks simpler -- but the downside is that if we were to expand "automerge" to other package updates, then the list of branches needs updating manually.

ISTM that we actually could use automerge for most version bumps -- in those PRs we usually just check that CI is passing. So automation could save time.

Copy link
Collaborator Author

@intgr intgr Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Opened a PR for option (2) #2899

pull_request:
workflow_dispatch:

Expand Down
Loading