Repository navigation
build: upgrade Go and resolve security findings - #94
Merged
Merged
Conversation
- Require Go 1.26.10 across tracked modules - Test the minimum supported patch release in CI
- Select Go 1.26 in workflow matrices and setup steps - Keep module minimum requirements at Go 1.26.10
- Represent both Go 1.26 and Go 1.27 as strings
- Resolve reported vulnerabilities in affected dependencies - Keep Go version matrices on current patch releases
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.
Summary
Upgrade Go module minimums to 1.26.10 and select the latest patch releases for the quoted Go 1.26/1.27 CI matrix. Upgrade vulnerable golang.org/x/net dependencies to v0.60.0 in affected main, example, and tool modules, with required transitive dependency updates.
AI authorship
.github/workflows/go.yml,_example/example01/go.mod,_example/example01/go.sum,_example/example02/go.mod,_example/example02/go.sum,_example/example03/go.mod,_example/example03/go.sum,_example/example04/go.mod,_example/example04/go.sum,go.mod,go.sum,go.tools.mod,go.tools.sum.Change classification
Core: dependency/runtime compatibility affects downstream users. Two reviewers including a module owner are recommended.
Plan and related issues
Upgrade Go to 1.26.10, resolve security findings, and verify every CI check. No issue references supplied.
Verification
Checkout
chore/upgrade-go-1.26.10at3bbf0a47db6752cf313fa6af8d02a31fd97bf782. Use Go 1.26.10 and network access for module downloads; run the commands below from the listed directory relative to the repository root.go test -mod=readonly -timeout=180s ./...in_example/example01go test -mod=readonly -timeout=180s ./...in_example/example02go test -mod=readonly -timeout=180s ./...in_example/example03go test -mod=readonly -timeout=180s ./...in_example/example04go test -mod=readonly -timeout=180s ./...in.go tool -modfile=go.tools.mod golangci-lint run --allow-serial-runnersin.actionlint -shellcheck= -pyflakes= .github/workflows/codeql.yml .github/workflows/go.yml .github/workflows/goreleaser.yml .github/workflows/trivy-scan.ymlin.trivy fs --scanners vuln,secret,misconfig --severity CRITICAL,HIGH,MEDIUM --ignore-unfixed --exit-code 1 .in a clean checkoutgit diff --checkandgit diff --staged --checkAcceptance scenarios
Status: Passed locally. Hosted CI is being monitored on this commit; local results do not imply human security approval. Remove disposable integration test containers when finished.
Risk and rollback
Dependency changes can affect compatibility. Older Go toolchains must upgrade. No production data is modified; revert the commits to restore prior versions. Do not disable security checks to bypass failures.
Reviewer guide
Review dependency/module changes and any explicit behavior fixes above; spot-check regenerated checksums and CI configuration.