Update registry.access.redhat.com/ubi9/go-toolset:1.25.8 Docker digest to 75ecb48 (main) - autoclosed

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
registry.access.redhat.com/ubi9/go-toolset	stage	digest	7a0aad9 → 75ecb48

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag	Coverage Δ
acceptance	53.44% <ø> (ø)
generative	16.79% <ø> (ø)
integration	27.66% <ø> (ø)
unit	69.13% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 10:48 PM UTC · Completed 10:51 PM UTC
Commit: 47d3320 · View workflow run →

[fullsend-ai-retro]

PR #3246 is a bot-authored Renovate/MintMaker dependency update (Docker digest bump in Dockerfile.dist) created by red-hat-konflux[bot]. It was auto-closed on 2026-06-19 without merge, likely superseded by a newer update. No agent workflows ran on this PR — no code, review, or fix agents were involved. The only agent interaction was this retro itself firing on PR closure.

This retro run is itself an example of wasted compute: analyzing a bot dependency PR with no agent activity yields no actionable insights. However, this problem is already well-covered by existing open issues in fullsend-ai/fullsend:

• Allow not-yet-effective successes in output #939 — Skip retro dispatch on PRs with no agent involvement (foundational issue)
• Patch pipelines for release v0.2 #1411 — Skip retro dispatch for unmerged PRs with no agent interaction
• Revert "Merge pull request #2150 from zregvart/issue/EC-963" #2176 — Skip retro dispatch for closed-without-merge PRs with immediate successor
• Switch to using OCI Trusted Artifacts Pipeline #1630 — Skip retro dispatch for bot-authored PRs with review-only agent interaction

Additionally, #2317 ("Skip retro dispatch for bot dependency PRs with clean reviews") was recently closed on 2026-06-16, suggesting partial progress on this front.

No new proposals are warranted — existing issues already cover the improvement needed.

[fullsend-ai-review]

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

[fullsend-ai-review]

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

[fullsend-ai-review]

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 and does not provide justification beyond the automated Renovate bot description. Protected infrastructure files require human approval regardless of whether the change is automated.
  Remediation: A maintainer should verify that the new go-toolset:1.25.8 digest (75ecb48...) is the expected image update before merging. No linked issue is required for routine digest pins, but human review of the Dockerfile change is mandatory per repository policy.

---

Labels: PR modifies a Dockerfile, adding the docker label to categorize the change area.

Previous run

Looks good to me

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 1:39 AM UTC · Completed 1:45 AM UTC
Commit: 47d3320 · View workflow run →

[fullsend-ai-review]

See the review comment for full details.

[fullsend-ai-review]

[high] protected-path

This PR modifies Dockerfile.dist, which falls under the Dockerfile protected path. The PR has no linked issue and does not provide justification beyond the automated Renovate bot description. Protected infrastructure files require human approval regardless of whether the change is automated.

Suggested fix: A maintainer should verify that the new go-toolset:1.25.8 digest (75ecb48...) is the expected image update before merging. No linked issue is required for routine digest pins, but human review of the Dockerfile change is mandatory per repository policy.

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 9:37 PM UTC · Completed 9:43 PM UTC
Commit: 47d3320 · View workflow run →

[fullsend-ai-retro]

Retro: PR #3246 (Docker digest bump by red-hat-konflux[bot])

This PR was a trivial bot-authored Docker digest pin update in Dockerfile.dist that lived for ~2 months before being autoclosed without merge. Agent activity was limited to review and retro agents—no code or fix agents were involved.

Key observations

1. Inconsistent review verdicts on identical code: The review agent ran twice on the same commit (47d3320). The first review (2026-06-20) found a [high] protected-path finding but submitted APPROVED. The second review (2026-06-26) found the same [high] protected-path finding but submitted CHANGES_REQUESTED. This inconsistency is already tracked by #1389 and #1319, with partial progress via recently closed issues Update snapshots #1548 and chore(deps): update konflux references (main) #1979.

2. Wasted compute on bot dependency PRs: Three review runs and two retro runs were dispatched for a one-line Docker digest bump that was never merged. Already tracked by #1371, #1358, and #2639.

3. Duplicate retro runs: This is the second retro on this PR—the first ran on 2026-06-19 and correctly found nothing actionable. Already tracked by #2401.

Conclusion

No new proposals warranted. All identified improvement areas are covered by existing open issues in fullsend-ai/fullsend. The most impactful issues to prioritize would be #939/#1411 (skip retro on PRs with no meaningful agent activity) and #1389 (stabilize review verdicts across re-runs).