Skip to content

Bump google.golang.org/grpc from 1.75.0 to 1.79.3#792

Merged
google-oss-prow[bot] merged 1 commit intomasterfrom
dependabot/go_modules/google.golang.org/grpc-1.79.3
Mar 20, 2026
Merged

Bump google.golang.org/grpc from 1.75.0 to 1.79.3#792
google-oss-prow[bot] merged 1 commit intomasterfrom
dependabot/go_modules/google.golang.org/grpc-1.79.3

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 19, 2026

Bumps google.golang.org/grpc from 1.75.0 to 1.79.3.

Release notes

Sourced from google.golang.org/grpc's releases.

Release 1.79.3

Security

  • server: fix an authorization bypass where malformed :path headers (missing the leading slash) could bypass path-based restricted "deny" rules in interceptors like grpc/authz. Any request with a non-canonical path is now immediately rejected with an Unimplemented error. (#8981)

Release 1.79.2

Bug Fixes

  • stats: Prevent redundant error logging in health/ORCA producers by skipping stats/tracing processing when no stats handler is configured. (grpc/grpc-go#8874)

Release 1.79.1

Bug Fixes

Release 1.79.0

API Changes

  • mem: Add experimental API SetDefaultBufferPool to change the default buffer pool. (#8806)
  • experimental/stats: Update MetricsRecorder to require embedding the new UnimplementedMetricsRecorder (a no-op struct) in all implementations for forward compatibility. (#8780)

Behavior Changes

  • balancer/weightedtarget: Remove handling of Addresses and only handle Endpoints in resolver updates. (#8841)

New Features

  • experimental/stats: Add support for asynchronous gauge metrics through the new AsyncMetricReporter and RegisterAsyncReporter APIs. (#8780)
  • pickfirst: Add support for weighted random shuffling of endpoints, as described in gRFC A113.
    • This is enabled by default, and can be turned off using the environment variable GRPC_EXPERIMENTAL_PF_WEIGHTED_SHUFFLING. (#8864)
  • xds: Implement :authority rewriting, as specified in gRFC A81. (#8779)
  • balancer/randomsubsetting: Implement the random_subsetting LB policy, as specified in gRFC A68. (#8650)

Bug Fixes

  • credentials/tls: Fix a bug where the port was not stripped from the authority override before validation. (#8726)
  • xds/priority: Fix a bug causing delayed failover to lower-priority clusters when a higher-priority cluster is stuck in CONNECTING state. (#8813)
  • health: Fix a bug where health checks failed for clients using legacy compression options (WithDecompressor or RPCDecompressor). (#8765)
  • transport: Fix an issue where the HTTP/2 server could skip header size checks when terminating a stream early. (#8769)
  • server: Propagate status detail headers, if available, when terminating a stream during request header processing. (#8754)

Performance Improvements

  • credentials/alts: Optimize read buffer alignment to reduce copies. (#8791)
  • mem: Optimize pooling and creation of buffer objects. (#8784)
  • transport: Reduce slice re-allocations by reserving slice capacity. (#8797)

... (truncated)

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will 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.

Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.75.0 to 1.79.3.
- [Release notes](https://github.com/grpc/grpc-go/releases)
- [Commits](grpc/grpc-go@v1.75.0...v1.79.3)

---
updated-dependencies:
- dependency-name: google.golang.org/grpc
  dependency-version: 1.79.3
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Copy link

@Sridhar1030 Sridhar1030 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of things worth confirming:

Compatibility: Since google.golang.org/grpc is a core dependency (even if indirect), do we expect any breaking changes between v1.75.0 and v1.79.3 that could affect controller-runtime or Kubernetes client interactions?

Transitive updates: I see related updates to genproto and protobuf as well were these pulled in automatically, and are they aligned with the versions used by controller-runtime / client-go?

Testing: Assuming CI is already covering this, but it would be good to confirm all e2e / integration tests pass, especially anything involving API communication or job orchestration.

Go module hygiene: Since these are indirect dependencies, do we want to run go mod tidy to ensure no unnecessary entries remain?

Overall this looks like a straightforward bump, just calling out these checks to avoid subtle runtime issues.

@google-oss-prow
Copy link

@Sridhar1030: changing LGTM is restricted to collaborators

Details

In response to this:

A couple of things worth confirming:

Compatibility: Since google.golang.org/grpc is a core dependency (even if indirect), do we expect any breaking changes between v1.75.0 and v1.79.3 that could affect controller-runtime or Kubernetes client interactions?

Transitive updates: I see related updates to genproto and protobuf as well were these pulled in automatically, and are they aligned with the versions used by controller-runtime / client-go?

Testing: Assuming CI is already covering this, but it would be good to confirm all e2e / integration tests pass, especially anything involving API communication or job orchestration.

Go module hygiene: Since these are indirect dependencies, do we want to run go mod tidy to ensure no unnecessary entries remain?

Overall this looks like a straightforward bump, just calling out these checks to avoid subtle runtime issues.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Copy link
Member

@tenzen-y tenzen-y left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tenzen-y

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-prow google-oss-prow bot merged commit a1081f0 into master Mar 20, 2026
14 of 15 checks passed
@google-oss-prow google-oss-prow bot deleted the dependabot/go_modules/google.golang.org/grpc-1.79.3 branch March 20, 2026 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants