Update registry.access.redhat.com/ubi9/go-toolset Docker tag to v1.25.9-1778675823

[red-hat-konflux-kflux-prd-rh02]

This PR contains the following updates:

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

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

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.

[openshift-ci]

[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 ma-hill 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

[openshift-ci]

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

I'm waiting for a openshift-hyperfleet 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.

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Pinned the Go build environment to a specific, fixed version to improve build consistency and reproducibility across environments.

Walkthrough

The Dockerfile builder stage base image was changed from the floating tag registry.access.redhat.com/ubi9/go-toolset:1.25 to the pinned tag registry.access.redhat.com/ubi9/go-toolset:1.25.9-1778675823. No other Dockerfile build or runtime steps, and no exported/public code entities, were modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: updating a Docker base image tag to a pinned version, which matches the changeset.
Description check	✅ Passed	The description is related to the changeset, providing details about the Docker dependency update including package name, update type, and version change.
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.

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

✨ Finishing Touches

🧪 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.}

[coderabbitai]

Actionable comments posted: 1

🤖 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 3: You pinned the builder image in the Dockerfile by changing the FROM
line to registry.access.redhat.com/ubi9/go-toolset:1.25.9-1778675823, which
diverges from other hyperfleet services that still use the floating tag
registry.access.redhat.com/ubi9/go-toolset:1.25; to fix, coordinate and
standardize the builder image tag across all hyperfleet repos and architecture
docs (or decide to revert to the floating tag), update the Dockerfile's FROM
reference accordingly (or update other services to the pinned tag), and adjust
any architecture documentation/examples to reflect the agreed-upon tag so build
environments remain consistent.

🪄 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: Central YAML (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: e9189d7a-b3e6-46a7-85c3-86a08206fb8e

📥 Commits

Reviewing files that changed from the base of the PR and between a69477e and 2db4c3d.

📒 Files selected for processing (1)

• Dockerfile

[coderabbitai]

🧹 Nitpick | 🔵 Trivial

Consider coordinating image pin across hyperfleet services.

The linked repository findings show that other hyperfleet services (hyperfleet-sentinel, hyperfleet-adapter) and architecture documentation examples still reference the unpinned registry.access.redhat.com/ubi9/go-toolset:1.25 tag. Pinning this repository's builder image while others remain on the floating tag creates divergence in build environments across the hyperfleet ecosystem.

If pinning builder images is being adopted as a standard practice, consider propagating this change to other services and updating the architecture documentation to maintain consistency.

🤖 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 3, You pinned the builder image in the Dockerfile by
changing the FROM line to
registry.access.redhat.com/ubi9/go-toolset:1.25.9-1778675823, which diverges
from other hyperfleet services that still use the floating tag
registry.access.redhat.com/ubi9/go-toolset:1.25; to fix, coordinate and
standardize the builder image tag across all hyperfleet repos and architecture
docs (or decide to revert to the floating tag), update the Dockerfile's FROM
reference accordingly (or update other services to the pinned tag), and adjust
any architecture documentation/examples to reflect the agreed-upon tag so build
environments remain consistent.

[ciaranRoche]

Closing: superseded by renovate.json config in #158 (HYPERFLEET-1095). MintMaker will re-create grouped updates on the next Monday cycle.

[red-hat-konflux-kflux-prd-rh02]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (1.25.9-1778675823). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.