Skip to content

fix: build with Go 1.26.11 (GO-2026-6859) and date the changelog - #11

Merged
mateen993 merged 2 commits into
masterfrom
docs/changelog-v0.1.6-date
Nov 11, 2026
Merged

mateen993 merged 2 commits into
masterfrom
docs/changelog-v0.1.6-date

Conversation

@MudassarTariq

@MudassarTariq MudassarTariq commented Nov 11, 2026 •

Copy link
Copy Markdown
Member

Every check started failing on 2026-11-11: GO-2026-6859 (CVE-2026-97054, an HTTP/1 server crash in net/http) was published at 02:51 UTC and affects Go 1.26.10 and 1.27.3, which this repo pinned. It is fixed in Go 1.26.11 and 1.27.4.

  • go.mod: go 1.26.11
  • checks.yml: test matrix 1.26.11 and 1.27.4; build job 1.26.11
  • release.yml: release builds use 1.26.11
  • README.md: building from source needs Go 1.26.11+
  • CHANGELOG.md: dates the v0.1.6 entry (released 2026-11-11) and adds v0.1.7

The v0.1.6 binaries were built with Go 1.26.10 one minute before the advisory was published, so they include the affected net/http. After this merges, tag v0.1.7 so the release is rebuilt with Go 1.26.11. If the tag goes out on a later day, update the v0.1.7 date to match.

Checked locally with Go 1.26.11: go vet, go test and govulncheck (0 vulnerabilities), and go mod tidy makes no changes. The tables and SQL queries are unchanged.

@MudassarTariq MudassarTariq changed the title docs: date the v0.1.6 changelog entry fix: build with Go 1.26.11 (GO-2026-6859) and date the changelog Nov 11, 2026
@mateen993 mateen993 self-assigned this Nov 11, 2026
@mateen993
mateen993 merged commit 3e7ed44 into master Nov 11, 2026
3 checks passed
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.

2 participants