chore(deps): update dependency go to v1.26.4

[renovate-fullsend]

This PR contains the following updates:

Package	Update	Change
go	patch	1.26.0 → 1.26.4

---

Release Notes

golang/go (go)

v1.26.4

Compare Source

v1.26.3

Compare Source

v1.26.2

Compare Source

v1.26.1

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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 has been generated by Mend Renovate.

[github-actions]

E2E tests did not run

E2E tests run automatically for org/repo members and collaborators on pull requests.

For other contributors, a maintainer must add the ok-to-test label after the latest push.

See E2E testing guide for details.

[github-actions]

Site preview

Preview: https://e72e8eda-site.fullsend-ai.workers.dev

Commit: d301e72e9ebeb1341269708aaa13a7cde80eeb09

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 7:01 AM UTC · Completed 7:09 AM UTC
Commit: d301e72 · View workflow run →

[fullsend-ai-retro]

Retro: PR #2709 — chore(deps): update dependency go to v1.26.4

This was a trivial Renovate bot PR that bumped Go from 1.26.0 to 1.26.4 in mise.toml (1 line changed). No fullsend agents were involved in the workflow — no review, code, or fix agents were dispatched because renovate-fullsend[bot] is not in the authorized actor list. A human (ifireball) approved the PR ~26 hours after creation, and it auto-merged.

The only agent activity was this retro being dispatched on PR close. This is the known "wasteful retro on bot PRs" pattern, which is already extensively tracked across multiple open issues:

• Skip retro dispatch on PRs with no agent involvement #939 — Skip retro dispatch on PRs with no agent involvement
• Refine retro dispatch guard in issue #939 to account for agent involvement on non-agent branches #942 — Refine retro dispatch guard to account for agent involvement on non-agent branches
• Skip retro dispatch for autoclosed bot-authored PRs #2461 — Skip retro dispatch for autoclosed bot-authored PRs
• Skip retro dispatch for merged bot PRs with no review findings #2638 — Skip retro dispatch for merged bot PRs with no review findings
• Skip retro dispatch for merged human PRs with no agent involvement #2708 — Skip retro dispatch for merged human PRs with no agent involvement

Additionally, three closely related issues were recently closed (#2540, #2523, #2228), indicating active work on this problem.

No new proposals filed — all improvement opportunities identified are already covered by existing open issues. The workflow functioned correctly given current configuration; the retro dispatch is the only inefficiency and it's well-known.