Skip to content

Require Go 1.26, not 1.27 - #15

Merged
bashhack merged 3 commits into
mainfrom
go-1.26
Oct 22, 2026
Merged

bashhack merged 3 commits into
mainfrom
go-1.26

Conversation

@bashhack

Copy link
Copy Markdown
Owner

Nothing in testdb needs Go 1.27: the newest language or library features in use are WaitGroup.Go (1.25) and b.Loop / t.Context (1.24). The 1.27 requirement came from the toolchain bump, not from any feature, and it shuts out projects that are on 1.26.

Every module's go directive is now 1.26.0, so testdb builds and runs on Go 1.26 and later. CI tests on both 1.26 and 1.27 so a newer-only feature cannot slip in unnoticed. Verified locally with the Go 1.26.5 toolchain: build, vet, lint and the full suite across all eight packages against Postgres and MySQL.

Nothing in testdb needs Go 1.27; the newest features in use are
WaitGroup.Go (1.25) and b.Loop and t.Context (1.24). Every module's go
directive is now 1.26.0, so testdb builds on 1.26 and later, and CI
tests on both 1.26 and 1.27.
@codecov-commenter

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@bashhack
bashhack merged commit cacc83c into main Oct 22, 2026
3 checks passed
@bashhack
bashhack deleted the go-1.26 branch October 22, 2026 07:16
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