NO-ISSUE: Pin dependencies

[red-hat-konflux]

This PR contains the following updates:

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

---

Warning

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

---

Configuration

📅 Schedule: (in timezone America/New_York)

• 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 in Dockerfile.rhtap to a digest-pinned reference, keeping the build steps and stages unchanged.

Changes

Docker Build Configuration

Layer / File(s)	Summary
Builder image reference update Dockerfile.rhtap	The builder stage FROM line now uses a sha256 digest for openshift-golang-builder:rhel_9_1.26 instead of the tag alone.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: eliorerz, gamli75, crystalchun

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
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	Only Dockerfile.rhtap changed; no test files or Ginkgo titles were modified, so there are no unstable or dynamic test names to flag.
Test Structure And Quality	✅ Passed	Only Dockerfile.rhtap changed; no Ginkgo test code was added or modified, so the test-quality check is not applicable.
Microshift Test Compatibility	✅ Passed	Only Dockerfile.rhtap changed to pin the builder image digest; no Ginkgo e2e tests or OpenShift API usage were added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Only Dockerfile.rhtap changed; no new or modified Ginkgo e2e tests were added, so SNO compatibility is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	Only Dockerfile.rhtap builder image digest was pinned; no deployment manifests, controllers, or scheduling logic changed.
Ote Binary Stdout Contract	✅ Passed	Only Dockerfile.rhtap changed to pin the builder image digest; no process-level code or stdout writes were added.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No new Ginkgo/e2e test code was added or modified; the PR only pins the builder image digest in Dockerfile.rhtap.
No-Weak-Crypto	✅ Passed	Diff only pins the builder image to a sha256 digest in Dockerfile.rhtap; no weak algorithms, custom crypto, or secret comparisons were added.
Container-Privileges	✅ Passed	PR only pins the builder image digest in Dockerfile.rhtap; no privileged, hostPID/hostNetwork/hostIPC, SYS_ADMIN, or allowPrivilegeEscalation settings were added.
No-Sensitive-Data-In-Logs	✅ Passed	Only change is a Docker base-image digest pin in Dockerfile.rhtap; no logging or sensitive-data exposure was added.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title matches the main change: pinning a dependency/image to an immutable digest.

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

[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.