NO-ISSUE: Pin brew.registry.redhat.io/rh-osbs/openshift-golang-builder Docker tag to 977bd04

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
brew.registry.redhat.io/rh-osbs/openshift-golang-builder	stage	pinDigest	→ 977bd04

---

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-robot]

@red-hat-konflux[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

This PR contains the following updates:

Package	Type	Update	Change
brew.registry.redhat.io/rh-osbs/openshift-golang-builder	stage	pinDigest	→ 071786d

---

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.

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.

[coderabbitai]

Walkthrough

Updated the Docker builder stage base image reference in Dockerfile.rhtap from a tag to an explicit image digest, pinning the build environment to a specific immutable version while preserving all subsequent build logic and stages.

Changes

Cohort / File(s)	Summary
Docker Build Configuration Dockerfile.rhtap	Replaced the builder stage base image tag (rhel_9_1.25) with the same image referenced by its explicit sha256 digest to produce deterministic, immutable builds.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 12

✅ Passed checks (12 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title specifies pinning a Docker image to a specific digest, which matches the core change in the pull request.
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	This custom check is not applicable to this pull request. The PR only modifies Dockerfile.rhtap to pin a Docker image digest, which is a build configuration change that does not involve any Ginkgo test files or test names.
Test Structure And Quality	✅ Passed	The PR only modifies infrastructure and configuration files; no test files were changed, making the Ginkgo test quality check not applicable.
Microshift Test Compatibility	✅ Passed	PR modifies only Dockerfile.rhtap to pin Docker base image to specific SHA256 digest; contains no Ginkgo e2e test additions or modifications, so custom check not applicable and passes by default.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR only modifies Dockerfile to pin Docker base image SHA256 digest; no Ginkgo e2e tests added.
Topology-Aware Scheduling Compatibility	✅ Passed	This PR pins a Docker builder base image digest in Dockerfile.rhtap, a build-time artifact that does not contain scheduling constraints, deployment manifests, or operator code.
Ote Binary Stdout Contract	✅ Passed	PR contains only Dockerfile.rhtap changes; OTE Binary Stdout Contract check applies only to Go code modifications.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	This PR only modifies Dockerfile.rhtap to pin a Docker base image to a specific SHA256 digest. No new Ginkgo e2e tests are being added or modified. The custom check is not applicable to this infrastructure change.
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/master/pin-dependencies

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign carbonin 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[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.