deps: update Go dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
github.com/google/go-sev-guest	v0.10.2 -> v0.11.0					require	minor
golang.org/x/exp	2c58cdc -> 814bf88					require	digest
google.golang.org/grpc	v1.61.0 -> v1.62.0					require	minor

---

Release Notes

google/go-sev-guest (github.com/google/go-sev-guest)

v0.11.0

Compare Source

The new QuoteProvider interface will automatically extend the auxblob to include an entry that details the machine's product information. This is useful when the cached VCEK is missing, since that certificate's productName extension is the only other place that information could be found from the AMD-generated artifacts (report and cert).

The other change here is minor with respect to CertTableOptions in validate. A required entry must have its verification function fail on an empty blob for the requirement to be fatal. This allows for a missing blob to drive a network-based fallback before the option fails entirely.

Full Changelog: google/go-sev-guest@v0.10.2...v0.11.0

What's Changed

• Add SevProduct raw cert representation. by @​deeglaze in https://github.com/google/go-sev-guest/pull/110
• Allow certentry Validate to fail before error by @​deeglaze in https://github.com/google/go-sev-guest/pull/111
• Only add extra product info if vcek cert missing by @​deeglaze in https://github.com/google/go-sev-guest/pull/112
• Use protocmp for binary proto comparison by @​deeglaze in https://github.com/google/go-sev-guest/pull/113

Full Changelog: google/go-sev-guest@v0.10.2...v0.11.0

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)
  • Special Thanks: @​s-matyukevich for discovering the root cause

Performance Improvements

• *: Allow building without x/net/trace by using grpcnotrace to enable dead code elimination (#​6954)
  • Special Thanks: @​hugelgupf
• 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)
  • Special Thanks: @​kmirzavaziri

Dependencies

• *: Use google.golang.org/protobuf/proto instead of github.com/golang/protobuf. (#​6919)
  • Special Thanks: @​Clement-Jean

[!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)
  • Special Thanks: @​s-matyukevich for discovering the root cause

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.