8000 chore(deps): update module google.golang.org/grpc to v1.73.0 by renovate-rancher[bot] · Pull Request #2000 · neuvector/neuvector · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore(deps): update module google.golang.org/grpc to v1.73.0 #2000

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jun 6, 2025
Merged

chore(deps): update module google.golang.org/grpc to v1.73.0 #2000

merged 1 commit into from
Jun 6, 2025

Conversation

renovate-rancher[bot]
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
google.golang.org/grpc require minor v1.72.2 -> v1.73.0

Release Notes

grpc/grpc-go (google.golang.org/grpc)

v1.73.0: Release 1.73.0

Compare Source

New Features

  • balancer/ringhash: move LB policy from xds/internal to exported path to facilitate use without xds (#​8249)
  • xds: enable least request LB policy by default. It can be disabled by setting GRPC_EXPERIMENTAL_ENABLE_LEAST_REQUEST=false in your environment. (#​8253)
  • grpc: add a CallAuthority Call Option that can be used to overwrite the http :authority header on per-RPC basis. (#​8068)
  • stats/opentelemetry: add trace event for name resolution delay. (#​8074)
  • health: added List method to gRPC Health service. (#​8155)
  • ringhash: implement features from gRFC A76. (#​8159)
  • xds: add functionality to support SPIFFE Bundle Maps as roots of trust in XDS which can be enabled by setting GRPC_EXPERIMENTAL_XDS_MTLS_SPIFFE=true. (#​8167, #​8180, #​8229, #​8343)

Bug Fixes

  • xds: locality ID metric label is changed to make it consistent with gRFC A78. (#​8256)
  • client: fail RPCs on the client when using extremely short contexts that expire before the grpc-timeout header is created. (#​8312)
  • server: non-positive grpc-timeout header values are now rejected. This is consistent with the gRPC protocol spec. (#​8290)
  • xds: fix reported error string when LRS load reporting interval is invalid. (#​8224)

Performance Improvements

  • credentials/alts: improve read performance by optimizing buffer copies and allocations. (#​8271)
  • server: improve performance of RPC handling by avoid a status proto copy (#​8282)

Documentation

  • examples/features/opentelemetry: modify example to demonstrate tracing using OpenTelemtry plugin. (#​8056)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@renovate-rancher renovate-rancher
Copy link
Contributor Author

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 1 additional dependency was updated

Details:

Package Change
google.golang.org/genproto/googleapis/rpc v0.0.0-20250218202821-56aae31c358a -> v0.0.0-20250324211829-b45e905df463

@holyspectral holyspectral merged commit 9240f16 into main Jun 6, 2025
7 checks passed
@holyspectral holyspectral deleted the renovate/google.golang.org-grpc-1.x branch June 6, 2025 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@holyspectral holyspectral holyspectral approved these changes

Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@holyspectral
0