Skip to content

docs(#3542): add Go version consistency guidance to AGENTS.md - #3543

Open
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/3542-go-version-consistency-docs
Open

docs(#3542): add Go version consistency guidance to AGENTS.md#3543
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/3542-go-version-consistency-docs

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

What:

Add a "Go Version Consistency" section to AGENTS.md listing the seven files that must declare the same Go version and reviewer guidance for detecting mismatches on version bump PRs.

Why:

PR #3538 bumped go.mod to a different Go version than the Dockerfile base images. The review agent approved the mismatch because AGENTS.md had no guidance about which files must stay in sync. This section enables the review agent (and human reviewers) to flag cross-file version inconsistencies that can cause build failures when GOTOOLCHAIN=local is set.

Complements #3360 (Renovate atomic updates) by providing review-time detection for manual bumps or partial Renovate PRs.

Tickets:


Closes #3542

Post-script verification

  • Branch is not main/master (agent/3542-go-version-consistency-docs)
  • Secret scan passed (gitleaks — 09f8926f1779f7bee2d93ee6f29a8e0e56c05842..HEAD)
  • PR body secret scan passed (gitleaks — no-git)

Add a new "Go Version Consistency" section listing the seven files
that must declare the same Go version (go.mod files, .tool-versions,
Dockerfile, Dockerfile.dist) and reviewer guidance for detecting
mismatches on Go version bump PRs. This enables the review agent to
flag cross-file version inconsistencies that can cause build failures
when GOTOOLCHAIN=local is set.

Motivated by PR #3538 where go.mod was bumped to a different version
than the Dockerfile base images. Complements #3360 (Renovate atomic
updates) by providing review-time detection for manual bumps.

Note: pre-commit hooks were not run. pre-commit could not complete
(infrastructure failure fetching remote hook repos). The only
configured hook (check-commit-message) checks commit messages, not
file content.

Closes #3542
@fullsend-ai-coder fullsend-ai-coder Bot added the ready-for-review Triggers review agent dispatch label Sep 3, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 3, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 3:28 PM UTC · Completed 3:40 PM UTC

Commit: ca5794c · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.88

@fullsend-ai-review fullsend-ai-review Bot added the risk/low PR risk: low label Sep 3, 2026
@fullsend-ai-review

Copy link
Copy Markdown

Risk Assessment: low (1/5)

Details

Docs-only PR adding 18 lines of guidance to AGENTS.md by a known bot author, with a perfectly scoped linked issue and no security, CI, or dependency changes — minimal risk.

@fullsend-ai-review

Copy link
Copy Markdown

Review

Findings

Medium

Low

  • [technical documentation accuracy] AGENTS.md:62 — The Dockerfile.dist entry abbreviates the image as FROM go-toolset:X.Y.Z@sha256:... but the actual FROM line uses registry.access.redhat.com/ubi9/go-toolset:1.26.7@sha256:.... Dropping the ubi9/ path segment reduces greppability for reviewers checking version consistency. The Dockerfile entry abbreviating docker.io/library/golang to golang is standard Docker Hub convention and not misleading.
    Remediation: Change item 7 to Dockerfile.dist (FROM ubi9/go-toolset:X.Y.Z@sha256:...) to preserve the distinguishing path component.

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 fullsend-ai-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the review comment for full details.

Comment thread AGENTS.md
5. `.tool-versions` (`golang X.Y.Z`)
6. `Dockerfile` (`FROM golang:X.Y.Z@sha256:...`)
7. `Dockerfile.dist` (`FROM go-toolset:X.Y.Z@sha256:...`)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[low] technical documentation accuracy

The Dockerfile.dist entry abbreviates the image as FROM go-toolset:X.Y.Z@sha256:... but the actual FROM line uses registry.access.redhat.com/ubi9/go-toolset:1.26.7@sha256:.... Dropping the ubi9/ path segment reduces greppability for reviewers checking version consistency. The Dockerfile entry abbreviating docker.io/library/golang to golang is standard Docker Hub convention and not misleading.

Suggested fix: Change item 7 to Dockerfile.dist (FROM ubi9/go-toolset:X.Y.Z@sha256:...) to preserve the distinguishing path component.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-review Triggers review agent dispatch risk/low PR risk: low size: XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add AGENTS.md guidance for Go version cross-file consistency checks

0 participants