Skip to content
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.

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

fix(deps): Update module google.golang.org/grpc to v1.62.0 #455

Merged
merged 1 commit into from
Mar 2, 2024

Conversation

cq-bot
Copy link
Contributor

@cq-bot cq-bot commented Mar 2, 2024

This PR contains the following updates:

Package Type Update Change
google.golang.org/grpc indirect minor v1.60.1 -> v1.62.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

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

v1.62.0: Release 1.62.0

Compare Source

New Features

  • grpc: Add StaticMethod CallOption as a signal to stats handler that a method is safe to use as an instrument key (#​6986)

Behavior Changes

  • grpc: Return canonical target string from ClientConn.Target() and resolver.Address.String() (#​6923)

Bug Fixes

  • server: wait to close connection until incoming socket is drained (with timeout) to prevent data loss on client-side (#​6977)

Performance Improvements

  • *: Allow building without x/net/trace by using grpcnotrace to enable dead code elimination (#​6954)
  • rand: improve performance and simplify implementation of grpcrand by adopting math/rand's top-level functions for go version 1.21.0 and newer. (#​6925)

Dependencies

  • *: Use google.golang.org/protobuf/proto instead of github.com/golang/protobuf. (#​6919)

[!NOTE]
The above change in proto library usage introduces a minor behavior change within those libraries. The old github.com/golang/protobuf library would error if given a nil message to Marshal, while the new google.golang.org/protobuf library will successfully output zero bytes in this case. This means server method handlers that did return nil, nil will now return an empty message and no error, while it used to return an error. This also affects the client side, where clients sending nil messages used to fail without sending the RPC, and now they will send an empty message.

v1.61.1: Release 1.61.1

Compare Source

Bug Fixes

  • server: wait to close connection until incoming socket is drained (with timeout) to prevent data loss on client-side (#​6977)

v1.61.0: Release 1.61.0

Compare Source

New Features

  • resolver: provide method, AuthorityOverrider, to allow resolver.Builders to override the default authority for a ClientConn. (EXPERIMENTAL) (#​6752)
  • xds: add support for mTLS Credentials in xDS bootstrap (gRFC A65) (#​6757)
  • server: add grpc.WaitForHandlers ServerOption to cause Server.Stop to block until method handlers return. (EXPERIMENTAL) (#​6922)

Performance Improvements

Bug Fixes

  • client: correctly enable TCP keepalives with OS defaults on windows (#​6863)
  • server: change some stream operations to return UNAVAILABLE instead of UNKNOWN when underlying connection is broken (#​6891)
  • server: fix GracefulStop to block until all method handlers return (v1.60 regression). (#​6922)
  • server: fix two bugs that could lead to panics at shutdown when using NumStreamWorkers (EXPERIMENTAL). (#​6856)
  • reflection: do not send invalid descriptors to clients for files that cannot be fully resolved (#​6771)
  • xds: don't fail channel/server startup when xds creds is specified, but bootstrap is missing certificate providers (#​6848)
  • xds: Atomically read and write xDS security configuration client side (#​6796)
  • xds/server: fix RDS handling for non-inline route configs (#​6915)

Configuration

📅 Schedule: Branch creation - "before 3am on Saturday" (UTC), 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.

@cq-bot cq-bot added the automerge Add to automerge PRs once requirements are met label Mar 2, 2024
@github-actions github-actions bot added the fix label Mar 2, 2024
@kodiakhq kodiakhq bot merged commit d77769f into main Mar 2, 2024
6 checks passed
@kodiakhq kodiakhq bot deleted the renovate/google-golang-modules branch March 2, 2024 00:37
kodiakhq bot pushed a commit that referenced this pull request Apr 1, 2024
🤖 I have created a release *beep* *boop*
---


## [4.2.12](v4.2.11...v4.2.12) (2024-04-01)


### Bug Fixes

* **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.32.1 ([#457](#457)) ([199e492](199e492))
* **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.33.0 ([#458](#458)) ([05dbef5](05dbef5))
* **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.34.0 ([#459](#459)) ([e19fe52](e19fe52))
* **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.34.1 ([#460](#460)) ([b52aacf](b52aacf))
* **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.34.2 ([#461](#461)) ([dcf5a54](dcf5a54))
* **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.35.0 ([#462](#462)) ([6353efb](6353efb))
* **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.36.0 ([#463](#463)) ([b9dee2b](b9dee2b))
* **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.36.1 ([#464](#464)) ([c1bb510](c1bb510))
* **deps:** Update module github.com/stretchr/testify to v1.9.0 ([#466](#466)) ([828d3db](828d3db))
* **deps:** Update module google.golang.org/grpc to v1.62.0 ([#455](#455)) ([d77769f](d77769f))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Add to automerge PRs once requirements are met fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants