Update registry.access.redhat.com/ubi9/go-toolset Docker tag to v1.26.5 (release-v0.7)

[renovate]

This PR contains the following updates:

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

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 2:24 AM UTC · Completed 2:31 AM UTC
Commit: 87c4a29 · View workflow run →

[fullsend-ai-review]

Review

Findings

High

• [protected-path] Dockerfile.dist:19 — Dockerfile.dist matches the protected path prefix Dockerfile. This PR has no linked issue providing explicit authorization for modifying governance/infrastructure files. Human approval is required for all protected-path changes.
  Remediation: A human maintainer must review and approve this Dockerfile change. Consider linking a tracking issue to document the authorization for this update.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run

Review

Findings

High

• [protected-path] Dockerfile.dist — This file matches the protected path prefix Dockerfile in the repository's governance configuration. The PR modifies a governance/infrastructure file but has no linked issue authorizing the change. While this is an automated Renovate patch-level Docker base image bump (go-toolset 1.26.4 → 1.26.5) with a properly pinned digest, human approval is always required for protected-path changes.
  Remediation: A human reviewer should verify the base image update and approve the PR.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (2)

Review

Findings

High

• [protected-path] Dockerfile.dist — This PR modifies Dockerfile.dist, which falls under the protected path prefix Dockerfile. The PR has no linked issue providing authorization for modifying governance or infrastructure files. Human approval is required for changes to protected paths, regardless of whether the change is automated.
  Remediation: Link an authorizing issue or obtain explicit human approval for the protected-path change.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (3)

Review

Findings

High

• [protected-path] Dockerfile.dist:19 — PR modifies Dockerfile.dist, which matches the protected path Dockerfile. The PR has no linked issue providing authorization for modifying governance/infrastructure files. Human approval is always required for protected-path changes.

  The change itself is a routine Renovate bot patch-version bump of the go-toolset base image (1.26.4 → 1.26.5) with a pinned digest (sha256:0b471eb...). The repository has renovate.json configured, confirming Renovate is authorized to manage dependencies. However, protected-path policy requires an explicit linked issue or human approval regardless of the change's nature.

  Remediation: Obtain explicit human approval for this protected-path change, or link an authorizing issue.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (4)

Review

Findings

High

• [protected-path] Dockerfile.dist:19 — This PR modifies Dockerfile.dist, which matches the Dockerfile protected path pattern (governance/infrastructure). The PR has no linked issue authorizing changes to protected paths, and the description is an auto-generated Renovate template rather than a human-authored justification. Human approval is always required for protected-path changes.
  Remediation: A human reviewer must explicitly approve this infrastructure change. The change itself (patch version bump of go-toolset from 1.26.4 to 1.26.5 with pinned digest) is straightforward, but protected-path policy requires human sign-off.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (5)

Review

Findings

High

• [protected-path] Dockerfile.dist:19 — Protected file Dockerfile.dist is modified (matches protected path Dockerfile). The PR has no linked issue justifying the change to this governance/infrastructure file. While the change is a mechanical Renovate dependency update (Docker base image tag bump from go-toolset:1.26.4 to go-toolset:1.26.5 with updated digest), human approval is always required for protected-path changes.
  Remediation: A human reviewer must approve changes to protected paths. No code change is needed — the version bump itself is correct.

---

Labels: PR modifies a Dockerfile and updates a dependency version

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (6)

Review

Findings

High

• [protected-path] Dockerfile.dist — This PR modifies Dockerfile.dist, which matches the protected path Dockerfile. The PR has no linked issue providing authorization for modifying governance/infrastructure files. While the change is a routine Renovate dependency update (go-toolset tag bump from 1.26.4 to 1.26.5 with pinned digest), human approval is always required for protected-path changes.
  Remediation: A human maintainer should review and approve this change to the protected Dockerfile. No code issues were found — the image reference is properly digest-pinned and the tag bump is straightforward.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 10:53 AM UTC · Completed 11:00 AM UTC

Commit: 87c4a29 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:23 PM UTC · Completed 3:31 PM UTC

Commit: 87c4a29 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 5:05 PM UTC · Completed 5:15 PM UTC

Commit: 87c4a29 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 2:59 AM UTC · Completed 3:08 AM UTC

Commit: 87c4a29 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 10:09 AM UTC · Completed 10:17 AM UTC

Commit: 87c4a29 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 4:33 PM UTC · Completed 4:40 PM UTC

Commit: 87c4a29 · View workflow run →

[fullsend-ai-review]

See the review comment for full details.

[fullsend-ai-review]

[high] protected-path

Dockerfile.dist matches the protected path prefix 'Dockerfile'. This PR has no linked issue providing explicit authorization for modifying governance/infrastructure files. Human approval is required for all protected-path changes.

Suggested fix: A human maintainer must review and approve this Dockerfile change. Consider linking a tracking issue to document the authorization for this update.