Bump connectrpc.com/connect from 1.12.0 to 1.16.2

[dependabot[bot]]

Bumps connectrpc.com/connect from 1.12.0 to 1.16.2.

Release notes

Sourced from connectrpc.com/connect's releases.

v1.16.2

This is a patch release to make sure that consuming modules won't be vulnerable to CVE-2023-45288.

What's Changed

• Update the golang.org/x/net dependency to v0.23.0 in #729.

Full Changelog: https://github.com/connectrpc/connect-go/compare/v1.16.1...v1.16.2

v1.16.1

This release contains a single bugfix.

What's Changed

Bugfixes

• Fix redundant attempts to write headers in certain error cases in Connect unary RPCs by @​emcfarlane in #726

Full Changelog: https://github.com/connectrpc/connect-go/compare/v1.16.0...v1.16.1

v1.16.0

This release is mostly bug fixes but also reconciles connect-go with recent updates to the specification regarding mapping of RPC error codes to/from HTTP status codes (see connectrpc RFC 003)

What's Changed

Other changes

• Revise RPC error code HTTP status code mappings per latest changes to spec by @​jhump in #706

Enhancements

• Only send a grpc-status-details-bin trailer in the gRPC protocol if the error has details by @​bhollis in #713

Bugfixes

• Fix ErrorWriter IsSupported check to report false on ambiguous content-type and options indicate connect protocol version header is required by @​emcfarlane in #700
• In Connect unary protocol, fallback to code based on HTTP status if unable to deserialize code from JSON body by @​jhump in #702
• Fix ErrorWriter to recognize protocols, even if content-type indicates unrecognized codec by @​emcfarlane in #701
• Fix some places in the framework that weren't correctly recognizing and returning context-based error code (e.g. "canceled" or "deadline_exceeded") by @​jhump in #709
• Use "unimplemented" code for stream cardinality violations by @​jhump in #712
• Restrict which metadata in an error can be propagated into response metadata by @​emcfarlane in #711

New Contributors

• @​bhollis made their first contribution in #713

Full Changelog: https://github.com/connectrpc/connect-go/compare/v1.15.0...v1.16.0

v1.15.0

What's Changed

Since the last release, we have been significantly increasing coverage of our conformance suite. This has identified several inconsistencies with other Connect, gRPC, and gRPC-Web implementations. This release includes several fixes that will help align this implementation with others, behavior that can be verified by the conformance tests going forward. The fixes are backward-compatible with gRPC and Connect clients and servers. They fix some aspects of the wire representation and edge-case handling of spurious requests and responses, and they may affect users directly inspecting HTTP requests and responses.

Governance

• Add @​emcfarlane as a maintainer in #680 🎉

Enhancements

• Add transport-level retry support for RPCs with unary and server-stream RPCs. This also improves efficiency by eliminating a goroutine and a message copy. By @​emcfarlane in #649
• Prefer "application/grpc" over "application/grpc+proto" content-type when issuing gRPC calls. This accommodates Google Cloud Platform servers, which don't fully implement the gRPC specification. By @​lrewega in #655
• Small efficiency gains in on all outbound HTTP requests and unary Connect response validation by @​mattrobenolt in #682, #683

... (truncated)

Commits

• 2972b2d Prepare for v1.16.2 (#733)
• 30cddf8 Update conformance module to use newer version of Go and quic-go dependency (...
• f7f3814 Bump golang.org/x/net from 0.22.0 to 0.23.0 in /internal/conformance (#730)
• a6be0d0 Bump golang.org/x/net from 0.21.0 to 0.23.0 (#729)
• a5906bd Back to development (#728)
• 3ed7fb0 Prepare for v1.16.1 (#727)
• fd9d60a Fix multiple header writes for connect unary on error (#726)
• 1abde82 Bump connectrpc.com/conformance from 1.0.1 to 1.0.2 in /internal/conformance ...
• 59f77e7 Update to latest conformance suite: v1.0.1 (#723)
• e4300c7 Update to v1.0.0-rc4 of conformance suite (#721)
• Additional commits viewable in compare view

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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show 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)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.