Skip to content

fix(security): require Go 1.26.11 for GO-2026-6859 - #506

Merged
devantler merged 1 commit into
mainfrom
claude/security-go-1-26-11-4924
Nov 11, 2026
Merged

devantler merged 1 commit into
mainfrom
claude/security-go-1-26-11-4924

Conversation

@devantler

Copy link
Copy Markdown
Contributor

🤖 Generated by the Agentic Engineer

Why

A new Go security advisory, GO-2026-6859 in the standard web server and client, is fixed only in Go 1.26.11 and 1.27.4. The template still allows 1.26.10 and 1.27.3, so every project created from it would start on a vulnerable toolchain, and the template's own security floor would keep accepting it.

What

Moves the template to Go 1.26.11 and raises its built-in security floor so it refuses the affected versions, including 1.27.3.

Fixes #505

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated by the Agentic Engineer

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-11T04:27:05.271347Z 759dfe7 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Chef's kiss.

Reviewed commit: 759dfe723c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@github-code-quality

Copy link
Copy Markdown

Code coverage overview

Languages: Go

Go / code-coverage/go

main claude/security-go-1... 759dfe7 +/-
— 86% —

Line coverage data for the main branch is not yet available.

View coverage of the 3 most covered files.
File main claude/security-go-1... 759dfe7 +/-
pkg/example/example.go — 100% —
pkg/featureflag/featureflag.go — 93% —
main.go — 0% —

ℹ️ Calculations represent line coverage. Results may change as calculations are updated.

@github-actions

Copy link
Copy Markdown

✅⚠️MegaLinter analysis: Success with warnings

Descriptor Linter Files Fixed Errors Max errors Warnings Elapsed time
✅ ACTION actionlint 8 0 0 0.1s
✅ ACTION zizmor 8 0 0 0 1.62s
✅ BASH bash-exec 8 0 0 0.06s
✅ BASH shellcheck 8 0 0 0.52s
✅ BASH shfmt 8 0 0 0 0.03s
✅ COPYPASTE jscpd yes no no 0.56s
✅ EDITORCONFIG editorconfig-checker 45 0 0 0.1s
✅ JSON jsonlint 1 0 0 0.13s
✅ JSON prettier 1 0 0 0 0.45s
✅ JSON v8r 1 0 0 2.19s
⚠️ MARKDOWN markdownlint 6 0 5 0 1.09s
✅ MARKDOWN markdown-table-formatter 6 0 0 0 0.44s
✅ REPOSITORY betterleaks yes no no 1.27s
✅ REPOSITORY checkov yes no no 17.6s
✅ REPOSITORY git_diff yes no no 0.02s
✅ REPOSITORY grype yes no no 73.76s
✅ REPOSITORY osv-scanner yes no no 0.34s
✅ REPOSITORY secretlint yes no no 0.82s
✅ REPOSITORY syft yes no no 3.07s
✅ REPOSITORY trivy yes no no 11.22s
✅ REPOSITORY trivy-sbom yes no no 0.15s
✅ REPOSITORY trufflehog yes no no 2.64s
✅ SPELL lychee 20 0 0 1.06s
✅ YAML prettier 13 0 0 0 0.6s
✅ YAML v8r 13 0 0 5.84s
✅ YAML yamllint 13 0 0 0.53s

Detailed Issues

⚠️ MARKDOWN / markdownlint - 5 errors
AGENTS.md:25:401 error MD013/line-length Line length [Expected: 400; Actual: 600]
AGENTS.md:29:401 error MD013/line-length Line length [Expected: 400; Actual: 431]
AGENTS.md:33:401 error MD013/line-length Line length [Expected: 400; Actual: 538]
CLAUDE.md:1 error MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "@AGENTS.md"]
GEMINI.md:1 error MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "@AGENTS.md"]

See detailed reports in MegaLinter artifacts

MegaLinter is provided by OX Security
Show us your support by starring ⭐ the repository

@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated by the Agentic Engineer

Readiness at 759dfe723c60b8edb798e85a982a8da28d136977

  • Tried as a user: with Go 1.26.11 selected, the template's floor check accepts the toolchain and its self-test confirms the new boundaries (1.26.10 and 1.27.3 refused, 1.26.11 and 1.27.4 accepted); the scaffold's tests pass. On a host still on Go 1.27.3 the toolchain check now refuses with the advisory named, which is the intended behaviour.
  • Review: Codex reviewed this head with no findings; 0 threads. CodeRabbit is rate limited.
  • Hygiene: all checks green.

@devantler
devantler marked this pull request as ready for review November 11, 2026 04:30
@devantler
devantler requested a review from a team as a code owner November 11, 2026 04:30
@devantler
devantler merged commit c65fcc4 into main Nov 11, 2026
27 checks passed
@devantler
devantler deleted the claude/security-go-1-26-11-4924 branch November 11, 2026 04:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Require Go 1.26.11 for GO-2026-6859

1 participant