Skip to content

ci: build and test with Go 1.26.11 to clear a net/http vulnerability - #493

Open
leggetter wants to merge 1 commit into
mainfrom
ci/go-1.26.11
Open

leggetter wants to merge 1 commit into
mainfrom
ci/go-1.26.11

Conversation

@leggetter

Copy link
Copy Markdown
Collaborator

govulncheck fails on Go 1.26.10 with GO-2026-6859 in net/http (fixed in 1.26.11). It reports reachable call sites in the existing HTTP client, websocket and version-check code, so the failure is in the toolchain and not in any one change. main passed on 2026-11-10 and every PR that runs the test workflow now fails its govulncheck job.

This bumps the pinned Go version from 1.26.10 to 1.26.11 in the five workflows that pin it (test.yml, test-npm-build.yml, acceptance.yml, release.yml, outpost-live.yml). It is the same change as c0cc68d. Dependabot only proposes module bumps, so the toolchain pin has to be moved by hand. Moving it in release.yml also means released binaries ship the patched standard library.

Only version strings change: 13 lines in 5 files, none of them application code. test-homebrew-build.yml reads the version from go.mod (go 1.26.0), so it is unchanged.

🤖 Generated with Claude Code

Posted by an AI agent with human oversight.

govulncheck fails on Go 1.26.10 with GO-2026-6859 in net/http, fixed in
1.26.11. The fix is the toolchain, not a module, so Dependabot (gomod only)
never proposes it. Bumping the pin in release.yml also means released
binaries ship the patched standard library.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.

1 participant