Skip to content

OCM-00000 | ci: Update registry.access.redhat.com/ubi9/go-toolset Docker tag to v1.26.4-1782736563#3292

Merged
openshift-merge-bot[bot] merged 1 commit into
masterfrom
konflux/mintmaker/master/registry.access.redhat.com-ubi9-go-toolset-1.x
Jun 30, 2026
Merged

OCM-00000 | ci: Update registry.access.redhat.com/ubi9/go-toolset Docker tag to v1.26.4-1782736563#3292
openshift-merge-bot[bot] merged 1 commit into
masterfrom
konflux/mintmaker/master/registry.access.redhat.com-ubi9-go-toolset-1.x

Conversation

@red-hat-konflux

@red-hat-konflux red-hat-konflux Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
registry.access.redhat.com/ubi9/go-toolset stage minor 1.25.81.26.4-1782736563
registry.access.redhat.com/ubi9/go-toolset final minor 1.25.81.26.4-1782736563

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Configuration

📅 Schedule: (UTC)

  • 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 these updates 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.

@red-hat-konflux red-hat-konflux Bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Jun 25, 2026
@coderabbitai

coderabbitai Bot commented Jun 25, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 526cdad7-29f6-42e8-8fc3-89349f9ee71d

📥 Commits

Reviewing files that changed from the base of the PR and between 2a6a25c and bd184ab.

📒 Files selected for processing (3)
  • Dockerfile
  • images/Dockerfile.e2e
  • images/Dockerfile.konflux
🚧 Files skipped from review as they are similar to previous changes (3)
  • images/Dockerfile.konflux
  • Dockerfile
  • images/Dockerfile.e2e

📝 Walkthrough

Walkthrough

Three Dockerfiles update the ubi9/go-toolset base image tag from 1.25.8 to 1.26.4-1782736563. In images/Dockerfile.e2e, the updated tag is applied to the builder, rosa-support, and final stages, while the ocmcli stage remains unchanged.

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description does not follow the repository template and is missing the required summary, issue context, testing, and checklist sections. Rewrite the PR description using the template, filling the summary, issue context, related issues, change type, testing, proof, and checklist items or N/A.
✅ Passed checks (14 passed)
Check name Status Explanation
Title check ✅ Passed The title is specific and accurately describes the Docker tag update shown in the changeset.
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 The commit only adds/updates three Dockerfiles; no test/spec files or Ginkgo titles were changed.
Test Structure And Quality ✅ Passed PR only updates Dockerfile base-image tags; no Ginkgo test code was added or modified, so the test-quality check is not applicable.
Microshift Test Compatibility ✅ Passed Only Dockerfiles changed; no new or modified Ginkgo e2e tests, so MicroShift compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PASS: The PR only updates Dockerfile base images; no Ginkgo e2e tests were added or modified, so SNO compatibility review is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed Only Dockerfile base-image tags changed; no deployment manifests, controller code, or scheduling rules were modified.
Ote Binary Stdout Contract ✅ Passed PR only bumps Go toolset base images in Dockerfiles; no Go entrypoints, suite setup, or stdout-writing code changed, so the OTE stdout contract is unaffected.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Only Dockerfile base-image tags changed; no Ginkgo e2e tests or network-logic changes were introduced.
No-Weak-Crypto ✅ Passed PR only bumps Docker base image tags in three Dockerfiles; no MD5/SHA1/DES/RC4/3DES/Blowfish, ECB, custom crypto, or secret comparison code was added.
Container-Privileges ✅ Passed PR only updates Go toolset base image tags in three Dockerfiles; no privileged:true, hostPID/network/IPC, allowPrivilegeEscalation, or SYS_ADMIN changes were introduced.
No-Sensitive-Data-In-Logs ✅ Passed Only Docker base-image tags changed; no log statements, secrets, hostnames, PII, or token-like data were added in the patch.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch konflux/mintmaker/master/registry.access.redhat.com-ubi9-go-toolset-1.x

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

@openshift-ci

openshift-ci Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@codecov

codecov Bot commented Jun 25, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 27.02%. Comparing base (9c2b995) to head (bd184ab).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3292   +/-   ##
=======================================
  Coverage   27.02%   27.02%           
=======================================
  Files         334      334           
  Lines       36704    36704           
=======================================
  Hits         9920     9920           
  Misses      26029    26029           
  Partials      755      755           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/mintmaker/master/registry.access.redhat.com-ubi9-go-toolset-1.x branch from 4bbcb07 to 2a6a25c Compare June 29, 2026 11:48
@red-hat-konflux red-hat-konflux Bot changed the title OCM-00000 | ci: Update registry.access.redhat.com/ubi9/go-toolset Docker tag to v1.26.3-1782377916 OCM-00000 | ci: Update registry.access.redhat.com/ubi9/go-toolset Docker tag to v1.26.4-1782717933 Jun 29, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@Dockerfile`:
- Line 1: The builder image version is out of sync with the Go toolchain
declared in go.mod, so update the Dockerfile’s builder stage to match the repo’s
Go version or bump the repository toolchain/CI inputs consistently. Check the
Dockerfile builder FROM line and any related toolchain configuration so the
image tag and declared Go version stay aligned.

In `@images/Dockerfile.e2e`:
- Line 22: The final stage in the Dockerfile is still based on the full
go-toolset image, which should be replaced with a runtime-only base. Update the
image used by the final stage to a UBI minimal or other approved
distroless/runtime image from catalog.redhat.com, and keep only the copied
binaries and runtime utilities there; use the stage name around the final FROM
and the image selection logic as the main points to adjust.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 8044e988-e16b-4daa-bad9-8ef44531dc38

📥 Commits

Reviewing files that changed from the base of the PR and between 2d8810a and 2a6a25c.

📒 Files selected for processing (3)
  • Dockerfile
  • images/Dockerfile.e2e
  • images/Dockerfile.konflux

Comment thread Dockerfile Outdated
@@ -1,4 +1,4 @@
FROM registry.access.redhat.com/ubi9/go-toolset:1.25.8 AS builder
FROM registry.access.redhat.com/ubi9/go-toolset:1.26.4-1782717933 AS builder

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Toolchain declarations:"
fd -HI '^\.golangciversion$|^go\.mod$|^Dockerfile$' .

echo
if [ -f .golangciversion ]; then
  echo ".golangciversion:"
  cat .golangciversion
fi

echo
echo "go-toolset references:"
rg -n 'ubi9/go-toolset:' Dockerfile images/Dockerfile.konflux images/Dockerfile.e2e

echo
echo "Recommended validation command:"
echo "make basic-checks"

Repository: openshift/rosa

Length of output: 828


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== .golangciversion =="
if [ -f .golangciversion ]; then
  cat -n .golangciversion
else
  echo "missing"
fi

echo
echo "== go.mod go directive =="
sed -n '1,20p' go.mod | cat -n

echo
echo "== CI/toolchain references =="
rg -n '1\.26\.4|go-toolset|GOLANG|go version|golangciversion|\.golangciversion' .github Makefile .golangciversion go.mod Dockerfile images/Dockerfile.e2e images/Dockerfile.konflux

Repository: openshift/rosa

Length of output: 1829


Align the builder image with the declared Go toolchain. go.mod still says go 1.25.8, so ubi9/go-toolset:1.26.4-1782717933 is out of sync. Update the repo toolchain/CI inputs with this bump, or keep the Dockerfile on 1.25.8.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@Dockerfile` at line 1, The builder image version is out of sync with the Go
toolchain declared in go.mod, so update the Dockerfile’s builder stage to match
the repo’s Go version or bump the repository toolchain/CI inputs consistently.
Check the Dockerfile builder FROM line and any related toolchain configuration
so the image tag and declared Go version stay aligned.

Sources: Coding guidelines, Path instructions

Comment thread images/Dockerfile.e2e Outdated
FROM registry.ci.openshift.org/ci/cli-ocm:latest as ocmcli

FROM registry.access.redhat.com/ubi9/go-toolset:1.25.8
FROM registry.access.redhat.com/ubi9/go-toolset:1.26.4-1782717933

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔒 Security & Privacy | 🟠 Major | 🏗️ Heavy lift

Switch the final stage off go-toolset.

Line 22 keeps the runtime image on the full Go toolchain image even though the rest of this stage only copies prebuilt binaries and installs runtime utilities. That unnecessarily ships compiler/build tooling in the final image and weakens the container security posture.

As per path instructions, "Multi-stage builds; no build tools in final image" and "Base image: UBI minimal or distroless from catalog.redhat.com."

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@images/Dockerfile.e2e` at line 22, The final stage in the Dockerfile is still
based on the full go-toolset image, which should be replaced with a runtime-only
base. Update the image used by the final stage to a UBI minimal or other
approved distroless/runtime image from catalog.redhat.com, and keep only the
copied binaries and runtime utilities there; use the stage name around the final
FROM and the image selection logic as the main points to adjust.

Source: Path instructions

…ker tag to v1.26.4-1782736563

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/mintmaker/master/registry.access.redhat.com-ubi9-go-toolset-1.x branch from 2a6a25c to bd184ab Compare June 29, 2026 18:10
@red-hat-konflux red-hat-konflux Bot changed the title OCM-00000 | ci: Update registry.access.redhat.com/ubi9/go-toolset Docker tag to v1.26.4-1782717933 OCM-00000 | ci: Update registry.access.redhat.com/ubi9/go-toolset Docker tag to v1.26.4-1782736563 Jun 29, 2026
@openshift-ci

openshift-ci Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

@red-hat-konflux[bot]: 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.

@olucasfreitas

Copy link
Copy Markdown
Contributor

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 30, 2026
@openshift-ci

openshift-ci Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: olucasfreitas, red-hat-konflux[bot]

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

The pull request process is described 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 openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 30, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 8577f00 into master Jun 30, 2026
14 checks passed
@red-hat-konflux red-hat-konflux Bot deleted the konflux/mintmaker/master/registry.access.redhat.com-ubi9-go-toolset-1.x branch June 30, 2026 21:37
olucasfreitas added a commit that referenced this pull request Jul 1, 2026
Merge current master into the revert branch and keep the Dockerfile
image tags at 1.25.8 so the branch still restores the pre-#3292 state.
olucasfreitas added a commit that referenced this pull request Jul 1, 2026
Restore the go-toolset image tags changed in #3292.
This returns the build and CI Dockerfiles to their pre-update state.
openshift-merge-bot Bot pushed a commit that referenced this pull request Jul 1, 2026
Restore the go-toolset image tags changed in #3292.
This returns the build and CI Dockerfiles to their pre-update state.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant