Bump google.golang.org/grpc from 1.79.1 to 1.79.3 in /cli#417
Bump google.golang.org/grpc from 1.79.1 to 1.79.3 in /cli#417dependabot[bot] wants to merge 1 commit intomasterfrom
Conversation
Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.79.1 to 1.79.3. - [Release notes](https://github.com/grpc/grpc-go/releases) - [Commits](grpc/grpc-go@v1.79.1...v1.79.3) --- updated-dependencies: - dependency-name: google.golang.org/grpc dependency-version: 1.79.3 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
dependabot
bot
added
dependencies
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6d5235e50a
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| golang.org/x/term v0.40.0 | ||
| golang.org/x/text v0.34.0 | ||
| google.golang.org/grpc v1.79.1 | ||
| google.golang.org/grpc v1.79.3 |
There was a problem hiding this comment.
If this PR is meant to take the 1.79.3 security fix, updating only cli/go.mod does not touch the vulnerable attack surface: a repo-wide search found no grpc.NewServer usage under cli/ (it only dials servers, e.g. cli/cmd/context_check.go:122), while multiple server binaries still create gRPC servers and remain pinned to google.golang.org/grpc v1.79.1 in their own modules (for example api_realtime/cmd/signalman/main.go:295 with api_realtime/go.mod:9, and api_control/internal/grpc/server.go:6042 with api_control/go.mod:12). As merged, production services would stay on the vulnerable version even though this PR appears to have applied the fix.
Useful? React with 👍 / 👎.
Bumps google.golang.org/grpc from 1.79.1 to 1.79.3.
Release notes
Sourced from google.golang.org/grpc's releases.
Commits
dda86dbChange version to 1.79.3 (#8983)72186f1grpc: enforce strict path checking for incoming requests on the server (#8981)97ca352Changing version to 1.79.3-dev (#8954)8902ab6Change the version to release 1.79.2 (#8947)a928670Cherry-pick #8874 to v1.79.x (#8904)06df363Change version to 1.79.2-dev (#8903)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.