Skip to content

build: Go 1.27.3 for GO-2026-6809 in crypto/x509 - #78

Merged
TAIPANBOX merged 1 commit into
mainfrom
build/go-1.27.3
Oct 25, 2026
Merged

TAIPANBOX merged 1 commit into
mainfrom
build/go-1.27.3

Conversation

@TAIPANBOX

Copy link
Copy Markdown
Owner

What

Move the Go toolchain from 1.27.2 to 1.27.3.

  • .github/workflows/ci.yml
  • .github/workflows/release.yml
  • Dockerfile
  • README.md
  • go.mod

Why

govulncheck reports GO-2026-6809 (crypto/x509, fixed in go1.27.3) against go1.27.2, so the security job fails on every pull request, even a docs-only one. staticcheck stays on go1.27.1 where the workflow pins it (dominikh/go-tools#1832).

Checked

Local on go1.27.3: govulncheck ./..., go vet ./..., go test ./..., the gate scripts that name the pin, secretscan diff origin/main..HEAD.

No release or tag is cut here. Published images stay on go1.27.2 until a new release is made.

🤖 Generated with Claude Code

govulncheck reports GO-2026-6809 (crypto/x509, fixed in go1.27.3) against
go1.27.2, so the security job fails on every pull request. Move the go.mod
toolchain, the CI and release go-version, and the Dockerfile Go version to
1.27.3, and move the gate anchors that name the old pin.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@TAIPANBOX
TAIPANBOX merged commit c78ab02 into main Oct 25, 2026
8 checks passed
@TAIPANBOX
TAIPANBOX deleted the build/go-1.27.3 branch October 25, 2026 22:40
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