chore(deps): bump google.golang.org/grpc to v1.82.1 - #15
Merged
Merged
Conversation
erebe
approved these changes
Aug 6, 2026
benjaminch
approved these changes
Aug 6, 2026
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
3 participants
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
Bumps
google.golang.org/grpcfrom v1.79.3 to v1.82.1 to remediate GHSA-hrxh-6v49-42gf (high severity), reported by Dependabot onmaster.grpc is an indirect dependency here, pulled in through
google.golang.org/api.Changes
go get google.golang.org/grpc@v1.82.1 && go mod tidyalso carried along the following transitive updates:google.golang.org/grpcgoogle.golang.org/protobufgoogle.golang.org/genproto/googleapis/rpcgo.opentelemetry.io/otel(+ metric, trace)golang.org/x/oauth2No source changes were required and the
godirective stays at 1.25.0 — grpc v1.82.1 is compatible with it.Verification
go build ./...passesgo test ./...passes (internal,internal/aws,internal/config; the remaining packages have no test files)Both were also confirmed green on
masterbeforehand, so there is no behavior change attributable to this bump.