Update go toolchain directive to v1.27.2 (main)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
go (source)	toolchain	patch	1.27.1 → 1.27.2

---

Release Notes

golang/go (go)

v1.27.2

---

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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Enterprise
• Run ID: 9e3861db-ee72-4fea-8f18-a5a2dd2d1c01

📥 Commits

Reviewing files that changed from the base of the PR and between cecfaed and a292167.

📒 Files selected for processing: 2

• acceptance/go.mod
• docs/go.mod

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 10 remain after this review.

📝 Walkthrough

The acceptance and docs modules update their Go toolchain directive from go1.27.1 to go1.27.2.

Changes: Go toolchain update

Layer / File(s)	Summary
Update module toolchain directives acceptance/go.mod, docs/go.mod	Both module files now specify Go toolchain version go1.27.2 instead of go1.27.1.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: joejstuart, bohdanmar

Merge Risk: ⚪ Minimal · up to a2921

The acceptance and docs modules use Go 1.27.2; no actionable merge risk is evident in the changed directives or checked-in build configuration.

Pre-merge checks: 4 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Description check		The description identifies the version update but does not use the required What, Why, and Tickets sections. It provides no explicit rationale or related ticket information.	Update the description to include the required What, Why, and Tickets sections. State the files and directive being updated, explain the reason for the update, and provide a related Jira ticket or state that none applies.

Passed checks: 4 passed

Check name	Status	Explanation
Title check		The title clearly identifies the main change: updating the Go toolchain directive to v1.27.2 on main.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

_{Comment @coderabbitai help to get the list of available commands.}

[fullsend-ai-review]

Risk Assessment: low (1/5)

Details

Minimal 2-file 4-line bot-authored patch toolchain bump (go 1.27.1 -> 1.27.2) with no protected paths, no security-sensitive files, no CI changes, and no module version changes produces near-floor risk across all tiers.

[fullsend-ai-review]

Looks good to me

[fullsend-ai-retro]

This Renovate PR bumped the Go toolchain directive from go1.27.1 to go1.27.2 in acceptance/go.mod and docs/go.mod (2 files, +2/-2 lines). The fullsend pipeline handled it cleanly end-to-end:

• PR opened 2026-10-16 01:27:47 by Renovate.
• Risk assessment agent correctly rated the change low (1/5) at 01:36:26, flagging the near-floor characteristics (bot author, no protected paths, no security/CI/module-version changes).
• Review agent posted Looks good to me at 01:36:28 with zero findings (correctly — a patch toolchain bump has nothing substantive to review).
• fullsend-ai-review approved at 01:36:30, the ready-for-merge label was applied, and Renovate auto-merged at 04:53:59 when its merge schedule window opened.
• No fix dispatches, no human review comments, no rework.

Total time from PR open to review verdict was ~9 minutes; the ~3h gap before merge was Renovate's auto-merge schedule, not pipeline latency.

No improvement opportunities identified. Risk tier, review verdict, labels, and auto-merge all behaved exactly as intended for this class of trivial bot-authored patch bump. Related ongoing work on reducing noise for Renovate-class PRs is already tracked (e.g. fullsend-ai/fullsend#6278 on rebaseWhen: conflicted for lockfile-only patches, and #3016 on auto-merge policy for low-risk Renovate updates) — this retro adds no new evidence to those.