Skip to content

chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v1.25.9-1778675823#210

Open
red-hat-konflux[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main/registry.access.redhat.com-ubi9-go-toolset-1.x
Open

chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v1.25.9-1778675823#210
red-hat-konflux[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main/registry.access.redhat.com-ubi9-go-toolset-1.x

Conversation

@red-hat-konflux
Copy link
Copy Markdown

@red-hat-konflux red-hat-konflux Bot commented May 16, 2026

This PR contains the following updates:

Package Type Update Change
registry.access.redhat.com/ubi9/go-toolset stage patch 1.251.25.9-1778675823

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

… tag to v1.25.9-1778675823

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 16, 2026

Walkthrough

The Dockerfile build image default is updated from the generic Go toolset version 1.25 to a pinned release tag 1.25.9-1778675823. This ensures consistent builds across environments without changing runtime behavior, builder dependency installation, or binary packaging logic.

Changes

Build Image Update

Layer / File(s) Summary
BUILD_IMAGE default version pin
Dockerfile
The BUILD_IMAGE build argument default is changed from registry.access.redhat.com/ubi9/go-toolset:1.25 to registry.access.redhat.com/ubi9/go-toolset:1.25.9-1778675823 to pin a specific toolset release.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

lgtm, approved, konflux-nudge

Suggested reviewers

  • AnnaZivkovic
  • aleskandro
🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: updating the Docker base image tag from v1.25 to v1.25.9-1778675823 in the Dockerfile.
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 PR only modifies the Dockerfile (updating BUILD_IMAGE tag). No Ginkgo test files are being changed, so the custom check for stable test names is not applicable.
Test Structure And Quality ✅ Passed Check not applicable. This PR only updates Dockerfile BUILD_IMAGE tag. No test code is modified. The custom check requires reviewing Ginkgo test quality, which is irrelevant here.
Microshift Test Compatibility ✅ Passed This PR only updates the Docker image tag in the Dockerfile (from 1.25 to 1.25.9-1778675823) and does not add any new Ginkgo e2e tests. The MicroShift Test Compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR updates a Docker build image tag in the Dockerfile only. No Ginkgo e2e tests are added or modified. The SNO test compatibility check is not applicable to this PR.
Topology-Aware Scheduling Compatibility ✅ Passed This PR only updates a base image tag in the Dockerfile. No deployment manifests, operator code, or controllers were modified. No scheduling constraints were introduced.
Ote Binary Stdout Contract ✅ Passed PR only updates Dockerfile build image tag; no code changes that could violate OTE Binary Stdout Contract. Existing code correctly directs logging to stderr, not stdout.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR only updates Dockerfile with a new Go toolset image tag. No Ginkgo e2e tests are added or modified. The check is only applicable when new tests are added.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch konflux/mintmaker/main/registry.access.redhat.com-ubi9-go-toolset-1.x

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

@openshift-ci openshift-ci Bot requested review from AnnaZivkovic and aleskandro May 16, 2026 06:00
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 16, 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 aleskandro 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

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 16, 2026

@red-hat-konflux[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/ocp416-e2e-gcp e7877b8 link true /test ocp416-e2e-gcp
ci/prow/unit e7877b8 link true /test unit
ci/prow/ocp418-e2e-azure e7877b8 link true /test ocp418-e2e-azure

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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants