WIP ci: Add renovate configuration by 0xFelix · Pull Request #5 · kubevirt/virt-template

0xFelix · 2025-10-15T12:55:18Z

What this PR does / why we need it:

Add renovate configuration to automatically update dependencies.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

None

Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>

kubevirt-bot · 2025-10-15T12:55:21Z

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

kubevirt-bot · 2025-10-15T12:55:25Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lyarwood for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

dominikholler · 2025-10-15T14:56:15Z

+      "groupName": "Go dependencies"
+    }
+  ],
+  "constraints": {


The constraint is not required, because renovate tries to stay with the currently used golang version. This rule is only overwritten by security updates.

On my fork it tried to bump the golang version anyway, see 0xFelix/virt-template#17. I suspect this is not working?

dominikholler · 2025-10-15T14:57:04Z

+  },
+  "postUpdateOptions": [
+    "gomodTidy",
+    "gomodUpdateImportPaths"


According to my limited understanding of golang, the gomodUpdateImportPaths is only required on major updates, which is disabled in renovate by default.

dominikholler · 2025-10-15T14:57:58Z

+    "gomodUpdateImportPaths"
+  ],
+  "ignorePaths": [
+    "**/vendor/**"


I think this is already included in ":gitSignOff"

https://docs.renovatebot.com/presets-default/#gitsignoff

Doesn't look like it?

dominikholler · 2025-10-15T14:58:59Z

+        "require",
+        "indirect"
+      ],
+      "groupName": "Go dependencies"


According to my experience, before grouping the indirect updates, they have to be enabled by

{ "matchManagers": ["gomod"], "matchDepTypes": ["indirect"], "enabled": true },

Seems to work without enabling them a second time, see on my fork 0xFelix/virt-template#17

dominikholler · 2025-10-15T14:59:45Z

+  "packageRules": [
+    {
+      "matchManagers": [
+        "gomod"


this rule is redundant, because gomod is the only enabled manager

During test runs on my fork it also picked up other managers, e.g. for the Dockerfiles. Maybe that's related to the global configuration of renovate, i.e. it depends on the global config which managers are enabled by default?

dominikholler · 2025-10-15T15:00:57Z

+  ],
+  "baseBranchPatterns": [
+    "main",
+    "/^release-v([0-9]+\\.([0-9]+))$/"


the release branches should get only security updates. Would be interesting to learn how to express this.

ksimon1 · 2025-10-24T11:48:47Z

@@ -0,0 +1,48 @@
+{
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",


You can add "assigneesFromCodeOwners": true

kubevirt-bot · 2026-01-22T12:18:23Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

0xFelix · 2026-01-29T08:31:39Z

/remove-lifecycle stale

kubevirt-bot · 2026-04-29T18:43:13Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

0xFelix · 2026-04-30T08:29:29Z

/remove-lifecycle stale

@dominikholler Are you still working on this?

dominikholler · 2026-05-13T06:10:43Z

https://github.com/dominikholler/kubevirt-renovate/blob/9c1572510a92c55c152ad73c582cfd16a3f040d5/virt-template-renovate.json was used to generate #88 .

An external bot like redhat-renovate-bot or the Renovate GitHub App are not suitable, because this repo requires calling custom actions in addition to the golang updates.

I did not found an order of custom actions so that a single call of make vendor worked, seems like it is required to call it twice, one time before and one time after make generate.

For now, there are multiple packages excluded to avoid an update of the golang version, or to avoid applciation code changes. Probably these packages could be updated, if the project would be updated to the new kubernetes and golang version manually.

kubevirt-bot · 2026-06-27T06:50:26Z

There has been no activity on this PR for 45 days.
To protect limited CI resources, it has been automatically labelled 'stale'.
This PR will automatically rot after an additional 14 days of inactivity, and will be closed shortly after that.

What you can do:

If the PR is waiting on you to respond to a question or feedback and/or update the PR, please do so.
You can mark the PR as fresh and remove the label with the following command: /remove-lifecycle stale
If this PR is safe to close now, please help the project by closing it with: /close
If you need attention on this PR from a reviewer, you can raise it on the agenda of the relevant SIG meeting or KubeVirt Community meeting, or ping the kubevirt-dev slack channel.

/lifecycle stale

0xFelix · 2026-06-30T14:20:40Z

/close Superseded by #103

ci: Add renovate configuration

dbf482b

Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>

kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Oct 15, 2025

kubevirt-bot added the size/M label Oct 15, 2025

dominikholler reviewed Oct 15, 2025

View reviewed changes

ksimon1 reviewed Oct 24, 2025

View reviewed changes

kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 22, 2026

kubevirt-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 29, 2026

kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 29, 2026

kubevirt-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 30, 2026

kubevirt-prow Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 27, 2026

0xFelix closed this Jun 30, 2026

		@@ -0,0 +1,48 @@
		{
		"$schema": "https://docs.renovatebot.com/renovate-schema.json",

Uh oh!

Conversation

0xFelix commented Oct 15, 2025

Uh oh!

kubevirt-bot commented Oct 15, 2025

Uh oh!

kubevirt-bot commented Oct 15, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kubevirt-bot commented Jan 22, 2026

Uh oh!

0xFelix commented Jan 29, 2026

Uh oh!

kubevirt-bot commented Apr 29, 2026

Uh oh!

0xFelix commented Apr 30, 2026

Uh oh!

dominikholler commented May 13, 2026

Uh oh!

kubevirt-bot commented Jun 27, 2026

Uh oh!

0xFelix commented Jun 30, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants