Update dependency golang to v1.26.4 (main) - autoclosed

[red-hat-konflux]

This PR contains the following updates:

Package	Update	Change
golang	minor	1.25.8 → 1.26.4

---

Warning

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

---

Release Notes

golang/go (golang)

v1.26.4

Compare Source

v1.26.3

Compare Source

v1.26.2

Compare Source

v1.26.1

Compare Source

v1.26.0

Compare Source

v1.25.11

Compare Source

v1.25.10

Compare Source

v1.25.9

Compare Source

---

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.

[fullsend-ai-retro]

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

[fullsend-ai-retro]

PR #3193 was a bot-created dependency update (red-hat-konflux[bot] / MintMaker bumping golang from 1.25.8 to 1.26.4) that was autoclosed without merging. No agent interaction (no review, code, fix, or triage agents ran) and no human interaction occurred on this PR. The retro agent was triggered on PR close, consuming tokens for an analysis with no meaningful workflow to evaluate.

This is a known gap. Multiple open issues in fullsend-ai/fullsend already propose skipping retro dispatch in this scenario:

• #2461: Skip retro dispatch for autoclosed bot-authored PRs
• #939: Skip retro dispatch on PRs with no agent involvement
• #1411: Skip retro dispatch for unmerged PRs with no agent interaction

No new proposals are warranted — the existing issues cover this case. Implementing any of #2461, #939, or #1411 would prevent this class of wasted retro run.