Skip to content

ci: build and test with Go 1.26.11 and 1.27.4 - #17

Merged
MudassarTariq merged 1 commit into
mainfrom
ci/go-1.26.11
Nov 11, 2026
Merged

MudassarTariq merged 1 commit into
mainfrom
ci/go-1.26.11

Conversation

@MudassarTariq

Copy link
Copy Markdown
Member

GO-2026-6859 (net/http, published 2026-11-11) affects Go 1.26.10 and 1.27.3 and is fixed in Go 1.26.11 and 1.27.4. govulncheck fails on the old pins, so the next CI run would fail. This moves every pin to the fixed releases.

  • go.mod, checks.yml and release.yml: Go 1.26.11 (matrix also 1.27.4)
  • build-release.sh: refuses Go older than 1.26.11 / 1.27.4; release_test.go cases moved up to match
  • README requirements line

Checked locally on Go 1.26.11: go vet, go test ./... and govulncheck v1.9.0 (no vulnerabilities).

GO-2026-6859 (net/http, published 2026-11-11) affects Go 1.26.10 and 1.27.3 and is fixed in Go 1.26.11 and 1.27.4. govulncheck fails on the old pins, so the next CI run would fail. This moves every pin to the fixed releases.

- go.mod, checks.yml and release.yml: Go 1.26.11 (matrix also 1.27.4)
- build-release.sh: refuses Go older than 1.26.11 / 1.27.4; release_test.go cases moved up to match
- README requirements line

Checked locally on Go 1.26.11: go vet, go test ./... and govulncheck v1.9.0 (no vulnerabilities).
@MudassarTariq
MudassarTariq merged commit 3e31cc0 into main Nov 11, 2026
5 checks passed
@MudassarTariq
MudassarTariq deleted the ci/go-1.26.11 branch November 11, 2026 12:02
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