You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(deps): bump grpc 1.81.1 -> 1.83.0 and x/mod 0.38.0 -> 0.40.0 on REL_5_8
Peer of the equivalent main-branch fix. Clears the actionable
govulncheck finding on REL_5_8 for the August 2026 release cycle.
Ran 'hack/go-get.sh -u google.golang.org/grpc golang.org/x/mod' per
the go.mod note, which keeps the go directive stable (still 1.26.3
on this branch until the Go bump PR lands) and lets 'go mod tidy'
sweep matching transitive minors:
* google.golang.org/grpc 1.81.1 -> 1.83.0
(fixes GO-2026-6061 -- xDS RBAC + HTTP/2 transport CVEs; called via
cmd/postgres-operator/open_telemetry.go's OTel WithBatcher and
internal/postgres/parameters.go's strings.Replacer -> http2 transport)
* golang.org/x/mod 0.38.0 -> 0.40.0
(fixes GO-2026-6180 and GO-2026-6179 -- sumdb tlog bypass /
unrelated hashes; module-level, not called, but noisy in the
govulncheck report)
* golang.org/x/crypto 0.54.0 -> 0.55.0
* golang.org/x/net 0.57.0 -> 0.58.0
* golang.org/x/text 0.40.0 -> 0.41.0
* golang.org/x/tools 0.48.0 -> 0.49.0
* google.golang.org/protobuf 1.36.12-<pre> -> 1.36.12
* google.golang.org/genproto/googleapis/rpc refresh to 20260810
* cel.dev/expr 0.25.1 -> 0.25.2
Local go build / govulncheck are blocked on macOS by the pre-existing
pg_query_go/v5 cgo 'strchrnul' collision with the current macOS SDK
(reproduces on unmodified REL_5_8 -- unrelated to this bump). The
same set of bumps was verified with 'govulncheck ./...' on main and
reports 'Your code is affected by 0 vulnerabilities' (down from 1:
GO-2026-6061). Linux CI runs govulncheck cleanly.
Only GO-2026-5932 (x/crypto/openpgp, unmaintained upstream, no fix)
remains as a module-only finding not called from any PGO code path.
0 commit comments