Repository navigation
chore: bump Go toolchain to 1.27.3 for GO-2026-6809 - #126
Merged
Merged
Conversation
govulncheck reports GO-2026-6809 (crypto/x509 now distrusts compromised intermediate certificates) as called on go1.27.2, through TLS verification on HTTPS remotes. go1.27.3 fixes it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015oS6W9qjGMVnrTz5r8EwDL Entire-Checkpoint: 01M5FF7ZZ5YMZ1MXS08K6CFJYY
There was a problem hiding this comment.
🟢 Approval recommended
The narrowly scoped toolchain pins remain aligned, and no blocking issues were identified.
No open issues 🎉
What changed in this PR
Updates git-sync’s Go toolchain to address GO-2026-6809 without changing the minimum Go version for library consumers.
Changes:
- Aligns both toolchain pins at Go 1.27.3.
- Documents the security update in the changelog.
| File | Description |
|---|---|
| mise.toml | Updates the development Go pin to 1.27.3. |
| go.mod | Updates the toolchain to 1.27.3; retains Go 1.26 minimum. |
| CHANGELOG.md | Records the certificate-verification security update. |
Review effort: Balanced
Soph
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
govulnchecknow fails on every branch: GO-2026-6809 (crypto/x509distrusts compromised intermediate certificates) was published after main's last green scan. It is found ingo1.27.2and fixed ingo1.27.3, and git-sync calls it through TLS verification on HTTPS remotes (syncer.countingReadCloser.Read→x509.Certificate.Verify).Changes
go.modtoolchainand the mise pin:1.27.2→1.27.3.The
godirective stays at1.26, so the minimum Go version for library consumers is unchanged.Tests
On go1.27.3:
go run golang.org/x/vuln/cmd/govulncheck@v1.7.0 ./...(as CI runs it) reports no called vulnerabilities; the remaining uncalled module finding is the known GO-2026-5932.go test ./...andgolangci-lint runpass.🤖 Generated with Claude Code
https://claude.ai/code/session_015oS6W9qjGMVnrTz5r8EwDL
Note
Low Risk
Toolchain and changelog-only change with no application logic; it reduces TLS-related exposure in released binaries.
Overview
Bumps the Go toolchain from
1.27.2to1.27.3ingo.modand the mise pin so CI and local builds use the patched standard library.Documents the change under Security in
CHANGELOG.md, noting it clears GO-2026-6809 (crypto/x509distrust of compromised intermediate CAs), which affects TLS verification on HTTPS remotes. The modulegodirective stays at1.26, so the minimum Go version for library consumers is unchanged.Reviewed by Cursor Bugbot for commit c29038b. Configure here.