Repository navigation
Bump Go to 1.27 to pick up stdlib security fixes - #33
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The v1.2.0 binaries and the
chapsuk/miga:v1.2.0image are built with Go 1.23.0, so scanners flag stdlib CVEs in them, e.g. CRITICAL CVE-2025-68121 (crypto/tls, fixed in Go 1.24.13 / 1.25.7).This bumps the build toolchain to Go 1.27 in the Dockerfile and in the CI / goreleaser workflows. No code or dependency changes;
go.modstays atgo 1.23.Checked locally:
go vet ./...is clean, tests pass for MySQL and Postgres on Go 1.27.3, the Docker image builds and runs.Could you cut a v1.2.1 release after merging? Thanks!