Update registry.access.redhat.com/ubi9/go-toolset Docker tag to v1.26.4-1782910875 (main)

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
registry.access.redhat.com/ubi9/go-toolset	stage	patch	1.26.3 → 1.26.4-1782910875

---

Warning

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

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[fullsend-ai-review]

🤖 Review · ⚠️ Cancelled · Started 2:06 AM UTC · Ended 2:09 AM UTC
Commit: 47d3320 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 2:12 AM UTC · Completed 2:18 AM UTC
Commit: 47d3320 · View workflow run →

[fullsend-ai-review]

Review

Findings

High

• [protected-path] Dockerfile.dist:19 — This file matches the Dockerfile protected path. The PR modifies a governance/infrastructure file but has no linked issue justifying the change. While the PR is a Renovate-managed Docker image tag bump (go-toolset 1.26.3 → 1.26.4-1782910875) with a pinned digest, human approval is always required for protected-path changes.
  Remediation: Obtain explicit human approval for this Dockerfile change. Consider linking a tracking issue that authorizes Renovate-managed Dockerfile updates.

Previous run

Review

Findings

Medium

• [protected-path] Dockerfile.dist — This file matches a protected path (Dockerfile). The PR is an automated Renovate dependency update bumping the ubi9/go-toolset base image from 1.26.3 to 1.26.4-1782910875 with an updated digest pin. The rationale is clear from the PR description and labels. Human approval is always required for protected-path changes, regardless of context.

Previous run (2)

Review

Findings

High

• [protected-path] Dockerfile.dist:19 — Dockerfile.dist is under the protected path Dockerfile. This PR has no linked issue justifying the modification of governance/infrastructure files. Protected-path changes always require human reviewer approval regardless of the nature of the change.
  Remediation: Link an authorizing issue or obtain explicit human reviewer approval for this protected-path change.

Previous run (3)

Review

Findings

High

• [protected-path] Dockerfile.dist:19 — This PR modifies Dockerfile.dist, which falls under the Dockerfile protected path. The PR has no linked issue providing authorization for modifying governance/infrastructure files. Human approval is required for all protected-path changes.
  Remediation: Link an issue that authorizes this Dockerfile change, or obtain explicit human maintainer approval.

Previous run (4)

Review

Findings

High

• [protected-path] Dockerfile.dist:19 — This file matches the Dockerfile protected path. The PR modifies a governance/infrastructure file (Dockerfile.dist) but has no linked issue providing authorization or justification for the change. While this is an automated dependency version bump from MintMaker/Renovate, protected-path changes always require human approval regardless of the change's nature.
  Remediation: A maintainer should review and approve this protected-path change. No code changes are needed — this finding is a governance gate, not a code quality issue.

Previous run (5)

Review

Findings

High

• [protected-path] Dockerfile.dist — This file falls under the Dockerfile protected path. The PR has no linked issue providing authorization for changes to governance/infrastructure files. While the change itself is a trivial Docker tag update (1.26.3 → 1.26.3-1782377916) with an unchanged image digest, human approval is always required for protected-path modifications.
  Remediation: Obtain explicit human maintainer approval for this Dockerfile change.

---

Labels: PR modifies a Dockerfile (build infrastructure) and is a dependency version bump

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 2:00 AM UTC · Completed 2:06 AM UTC
Commit: 47d3320 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 2:12 AM UTC · Completed 2:17 AM UTC
Commit: 47d3320 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 2:05 AM UTC · Completed 2:11 AM UTC
Commit: 47d3320 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 2:04 AM UTC · Completed 2:09 AM UTC
Commit: 47d3320 · View workflow run →

Superseded by updated review

Superseded by updated review

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 2:12 AM UTC · Completed 2:18 AM UTC
Commit: 47d3320 · View workflow run →

[fullsend-ai-review]

See the review comment for full details.

[fullsend-ai-review]

[high] protected-path

Dockerfile.dist matches the Dockerfile protected path. The PR modifies a governance/infrastructure file but has no linked issue justifying the change. While the PR is a Renovate-managed Docker image tag bump (go-toolset 1.26.3 to 1.26.4-1782910875) with a pinned sha256 digest, human approval is always required for protected-path changes.

Suggested fix: Obtain explicit human approval for this Dockerfile change. Consider linking a tracking issue that authorizes Renovate-managed Dockerfile updates.