Skip to content

NO-JIRA: Add Renovate rules for UBI8 images on release-1.x branches#460

Open
alebedev87 wants to merge 1 commit into
openshift:mainfrom
alebedev87:renovate-add-ubi8-rules
Open

NO-JIRA: Add Renovate rules for UBI8 images on release-1.x branches#460
alebedev87 wants to merge 1 commit into
openshift:mainfrom
alebedev87:renovate-add-ubi8-rules

Conversation

@alebedev87
Copy link
Copy Markdown
Contributor

MintMaker/Renovate reads config only from the default branch (main), which only had rules for ubi9 images. The release-1.1 and release-1.2 branches use ubi8/ubi-minimal and ubi8/go-toolset in their Containerfiles, so Renovate silently skipped them.

Add matchBaseBranches-scoped rules for both UBI8 images to enable base image digest updates and Go toolchain version bumps on release branches.

MintMaker/Renovate reads config only from the default branch (`main`),
which only had rules for `ubi9` images. The `release-1.1` and
`release-1.2` branches use `ubi8/ubi-minimal` and `ubi8/go-toolset`
in their Containerfiles, so Renovate silently skipped them.

Add `matchBaseBranches`-scoped rules for both UBI8 images to enable
base image digest updates and Go toolchain version bumps on release
branches.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 21, 2026

📝 Walkthrough

Walkthrough

This pull request modifies renovate.json to add a new Renovate package rule targeting Red Hat UBI8 (Universal Base Image) Docker images. The rule enables automated updates for the ubi-minimal base image and the go-toolset package within Containerfile.external-dns-operator, limited to the release-1.1 and release-1.2 base branches. The go-toolset version is constrained to minor version 1.25 using the ^1\.25(\.|$) allowed-versions regex. The rule includes a Tuesday-after-5am update schedule and applies the redhat versioning scheme. All other existing Renovate configuration remains unchanged.

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description check ✅ Passed The description is clearly related to the changeset, explaining the rationale for adding UBI8 image rules and how Renovate configuration scoping works.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed All Ginkgo test titles in the PR are stable and deterministic with no dynamic content, pod names, timestamps, UUIDs, node names, or IP addresses.
Test Structure And Quality ✅ Passed PR only modifies renovate.json (configuration change); no Ginkgo test code was added or modified, making the test quality check inapplicable.
Microshift Test Compatibility ✅ Passed This PR contains only configuration changes to renovate.json; no new Ginkgo e2e tests are added, making the MicroShift compatibility check not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR modifies only renovate.json configuration for UBI8 images and adds no Ginkgo e2e tests. The custom check applies only to new tests, so it does not apply here.
Topology-Aware Scheduling Compatibility ✅ Passed PR only modifies renovate.json (dependency management configuration), which does not introduce any deployment manifests, operator code, or scheduling constraints.
Ote Binary Stdout Contract ✅ Passed PR only modifies renovate.json (Renovate dependency management configuration), which is a non-executable configuration file that cannot violate the OTE Binary Stdout Contract check.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR modifies only renovate.json (Renovate config). No Ginkgo e2e tests are added, so the IPv6/disconnected network compatibility check does not apply.
Title check ✅ Passed The title accurately describes the main change: adding Renovate rules for UBI8 images on release branches, which matches the core objective of enabling dependency updates on release-1.x branches.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested review from gcs278 and grzpiotrowski May 21, 2026 13:16
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 21, 2026

[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 gcs278 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:

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

@alebedev87
Copy link
Copy Markdown
Contributor Author

/test e2e-azure-infoblox-operator

@alebedev87 alebedev87 changed the title Add Renovate rules for UBI8 images on release-1.x branches NO-JIRA: Add Renovate rules for UBI8 images on release-1.x branches May 21, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 21, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@alebedev87: This pull request explicitly references no jira issue.

Details

In response to this:

MintMaker/Renovate reads config only from the default branch (main), which only had rules for ubi9 images. The release-1.1 and release-1.2 branches use ubi8/ubi-minimal and ubi8/go-toolset in their Containerfiles, so Renovate silently skipped them.

Add matchBaseBranches-scoped rules for both UBI8 images to enable base image digest updates and Go toolchain version bumps on release branches.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 21, 2026

@alebedev87: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

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

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants