Repository navigation
chore(deps): Go 1.27 + sustainment refresh — govulncheck back to zero (v1.9.2) - #58
Merged
Merged
Conversation
Clears the 21 called vulnerabilities govulncheck reported against the module (16 standard library, 5 third-party). Go toolchain 1.26.5 -> 1.27.3 covers the standard-library advisories (net/http, crypto/tls, crypto/x509, html/template, encoding/xml, encoding/asn1, net/url, net/textproto). golang.org/x/net 0.57.0 -> 0.61.0, otel 1.44.0 -> 1.47.0 (otelhttp 0.69.0 -> 0.72.0) and grpc 1.82.1 -> 1.84.0 clear the rest. The build image pin follows the toolchain. golangci-lint CI pin v2.11.4 -> v2.15.0: go1.27 support landed in v2.13.0. Its goconst check flagged repeated literals in a config test; hoisted into constants, no behaviour change. govulncheck: 21 called vulnerabilities -> 0. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Security-only release: the dependency refresh in the previous commit (Go 1.27.3, 21 called vulnerabilities cleared). Chart appVersion follows to 1.9.2 so the default image tag pulls the patched build instead of the vulnerable 1.9.1 one. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Sustainment refresh — 2026-10-21
Why now
govulncheckreported 21 called vulnerabilities againstmain(Go 1.26.5 toolchain + third-party modules), all published since v1.9.1. The CI and Release workflows gate on it.Applied bumps
go.mod,go.work)Dockerfilebuild imagegolang:1.26.5golang:1.27.3golang.org/x/netgo.opentelemetry.io/otel(+metric,sdk,trace, otlptrace exporters)otelhttpgoogle.golang.org/grpcx/crypto,x/sys,x/text,protobuf,genproto,grpc-gateway,testifyvendor/regenerated withgo work vendor.Go 1.26 → 1.27 is a minor-version bump — human review per repo policy. Go 1.26.10 would also have cleared every stdlib advisory if we'd rather stay on 1.26.
The newer golangci-lint
goconstflagged repeated literals ininternal/config/validation_test.go; hoisted into constants, no behaviour change.Vulnerabilities
x/crypto/openpgp, no fix, package not importedChecks (Go 1.27.3, tools built with go1.27)
go build ./...,go vet ./...go test -race ./...— 108 passed in 7 packagesgovulncheck ./...— 0 calledgolangci-lint run ./...(v2.15.0) — 0 issuesgofmt -l— cleanRelease
Second commit cuts v1.9.2 + chart 1.10.2 (
appVersion→ 1.9.2). After merge: tagv1.9.2andchart-v1.10.2.🤖 Generated with Claude Code