Skip to content

chore: bump go directive to 1.26.10 (clears reachable stdlib vulns) - #54

Merged
DTTerastar merged 1 commit into
mainfrom
chore/bump-go-1.26.10
Nov 3, 2026
Merged

DTTerastar merged 1 commit into
mainfrom
chore/bump-go-1.26.10

Conversation

@Terastar-Paperclip

Copy link
Copy Markdown
Contributor

Why

Checked crono-export-cli for the same govulncheck failure flagged in QUA-65 for liftoff-export-cli. On the 1.26.8 toolchain, govulncheck ./... reports 10 reachable stdlib vulnerabilities (net/http and crypto/x509) via cronoapi.Client.submitLogin / cmd.Execute.

What changed

Bumped the go directive in go.mod from 1.26.8 to 1.26.10. CI uses go-version-file: go.mod, so no workflow file changes are needed.

Verification

  • go build ./... — passes
  • go vet ./... — clean
  • go test ./... — passes
  • govulncheck ./... on 1.26.8: 10 reachable stdlib vulns. On 1.26.10 (this PR): No vulnerabilities found

Same fix pattern as quantcli/liftoff-export-cli#67.

govulncheck flagged 10 reachable stdlib vulnerabilities on the 1.26.8
toolchain (net/http and crypto/x509, reached via cronoapi.Client and
cmd.Execute). Bumping the go directive to 1.26.10 lets setup-go pull a
patched toolchain in CI; no source changes needed. Same fix pattern as
quantcli/liftoff-export-cli#67.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
@DTTerastar
DTTerastar merged commit e841653 into main Nov 3, 2026
6 checks passed
@DTTerastar
DTTerastar deleted the chore/bump-go-1.26.10 branch November 3, 2026 17:28
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.

3 participants