Skip to content

chore: name go 1.26.10 as the module toolchain for GO-2026-6809 - #42

Merged
lr00rl merged 1 commit into
integrationfrom
chore/20261024_go-toolchain-1.26.10
Oct 24, 2026
Merged

lr00rl merged 1 commit into
integrationfrom
chore/20261024_go-toolchain-1.26.10

Conversation

@lr00rl

@lr00rl lr00rl commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

The go.mod toolchain line moves from go1.26.6 to go1.26.10. CI and the release workflow already build with 1.26.10 since #41; this makes local builds on an older Go fetch the same fixed toolchain (GO-2026-6809, crypto/x509 denylist of compromised intermediates).

This is the last change before v0.3.10-alpha.8, which carries #39 (ordered install sources), #40 (installer token handover) and #41 (CI on 1.26.10, pinned scanners). No Go source changes since v0.3.10-alpha.7, so the compatibility floors stay at server v0.2.2-alpha.19 and dashboard v0.2.2-alpha.7.

Test plan:

  • gofmt -l . is empty
  • sh scripts/check-release-workflow.sh
  • sh scripts/test-install-integrity.sh
  • CI green

CI and the release workflow already build with 1.26.10 (#41), which adds
the crypto/x509 denylist of compromised intermediate certificates. The
go.mod toolchain line still named go1.26.6, so a local build on an older
Go stopped at 1.26.6 instead of fetching the fixed release. It now names
go1.26.10, and the next prerelease ships built with it.

Tested: sh scripts/check-release-workflow.sh, sh scripts/test-install-integrity.sh
@lr00rl
lr00rl merged commit e5f769f into integration Oct 24, 2026
1 check passed
@lr00rl
lr00rl deleted the chore/20261024_go-toolchain-1.26.10 branch October 24, 2026 18:33
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