Bump google.golang.org/grpc from 1.72.0 to 1.82.1 in /golang - #1311
Bump google.golang.org/grpc from 1.72.0 to 1.82.1 in /golang#1311dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.72.0 to 1.82.1. - [Release notes](https://github.com/grpc/grpc-go/releases) - [Commits](grpc/grpc-go@v1.72.0...v1.82.1) --- updated-dependencies: - dependency-name: google.golang.org/grpc dependency-version: 1.82.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
122b81e to
e550148
Compare
RockteMQ-AI
left a comment
There was a problem hiding this comment.
Review by github-manager-bot
Summary
Dependabot dependency bump: google.golang.org/grpc v1.72.0 → v1.82.1 in /golang, along with transitive dependency updates. The Go directive is also bumped from go 1.24 to go 1.25.0.
Findings
-
[Warning]
golang/go.mod:3— Go version bump1.24→1.25.0. This is a major toolchain upgrade. Please verify that CI pipelines and all developer environments support Go 1.25. If the project CI still uses Go 1.24, this will break the build. Consider whether this bump is intentional or if grpc v1.82.1 truly requires Go 1.25 as a minimum. -
[Info]
golang/go.mod:15— grpc version jump v1.72.0 → v1.82.1 (10 minor versions). Notable changes in this range include:- Security fixes (v1.82.1): HTTP/2 frame flood protection, xds/rbac fixes — these are beneficial.
- Behavior changes (v1.82.0): Strict RPC path validation is now permanent, balancer policy registry is case-sensitive, and default max header list size may change to 8KB in a future release.
- These behavior changes could affect gRPC communication with the RocketMQ Proxy. Recommend testing end-to-end message publish/consume flows with the updated client.
-
[Info]
golang/go.mod— Transitive updates togolang.org/x/*packages (crypto, net, sys, text, sync) are all minor/patch bumps and should be safe.
Suggestions
- Confirm CI matrix includes Go 1.25 before merging.
- Run integration tests against a RocketMQ Proxy to verify gRPC protocol compatibility with the new grpc-go version.
- If the Go 1.25 bump is unintended, consider pinning grpc to a version compatible with Go 1.24.
Automated review by github-manager-bot
RockteMQ-AI
left a comment
There was a problem hiding this comment.
Review by github-manager-bot
Summary
Dependabot bump of google.golang.org/grpc from 1.72.0 to 1.82.1 in the Go client module, along with transitive dependency updates.
Findings
- [Warning]
go.mod:3— The Go version is bumped from1.24to1.25.0. This is unusual for a dependabot PR (which typically only bumps dependencies, not the language version). This could be required by the new gRPC version, but verify:- That Go 1.25 is available and stable in your CI/CD pipeline
- That this doesn't break compatibility with users on Go 1.24
- [Info] gRPC 1.72.0 → 1.82.1 is a significant jump (10 minor versions). Check the gRPC-Go release notes for breaking changes.
- [Info]
protobuf1.36.6 → 1.36.11 is a patch-level update, low risk. - [Info]
go.sumchanges are consistent with thego.modupdates.
Suggestions
Verify that the Go 1.25 version bump is intentional and that CI is updated accordingly. If the gRPC bump doesn't actually require Go 1.25, consider keeping the Go version at 1.24 to minimize disruption.
Automated review by github-manager-bot
Bumps google.golang.org/grpc from 1.72.0 to 1.82.1.
Release notes
Sourced from google.golang.org/grpc's releases.
... (truncated)
Commits
ebd8f06Change version to 1.82.1 (#9238)4ea465dCherry-pick commits (#9236)9494a2cChange version to 1.82.1-dev (#9171)bd23985Change version to 1.82.0 (#9170)0f3086dFix minor issues not covered by PR #9137 (#9147)fef07fbinternal: Split v3procservicepb import into pb and grpc for extproc (#9163)91dd64ftransport: surface subsequent data when receiving non-gRPC header (#8929)adc97detest/kokoro: add config for regional-td test (#9158)57c9ff1xds: ensure full-string matching for RBAC Filter rules (#9148)b58f32dserver: Set a pprof label on new stream goroutines (#9082)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.