Bump connectrpc.com/connect from 1.14.0 to 1.16.0

[dependabot]

Bumps connectrpc.com/connect from 1.14.0 to 1.16.0.

Release notes

Sourced from connectrpc.com/connect's releases.

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: connectrpc/connect-go@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
• Improve efficiency handling gRPC-Web and Connect end-of-stream messages by @​jhump in #678

Bugfixes

• Fix HTTP status to Code mapping by @​emcfarlane in #673
• Client should verify response content-type by @​jhump in #679
• Omit erroneous @type attribute from Connect error detail debug string by @​jhump in #688
• Use context to correctly classify some errors with Canceled or DeadlineExceeded code by @​emcfarlane in #659
• Fix trailers-only response handling and some gRPC error coding by @​jhump in #677, #690

Full Changelog: connectrpc/connect-go@v1.14.0...v1.15.0

Commits

• 0208427 Prepare for v1.16.0 (#714)
• dbd9097 Bump google.golang.org/protobuf from 1.32.0 to 1.33.0 in /internal/conformanc...
• 90df12f Only send a serialized Status in the gRPC protocol if it has details (#713)
• 7b3b344 Restrict metadata headers in error propagation (#711)
• fbcf0ff Use "unimplemented" code for cardinality violations (#712)
• c22fe4f Update a couple of more places where we should return a context error if ther...
• befee1d Update to latest protobuf-go, v1.33.0 (#707)
• 872a6fd Fix ErrorWriter to be codec agnostic (#701)
• e3f35a6 Revise code mappings per latest changes to spec (#706)
• 75d634f In Connect unary protocol, fallback to code based on HTTP status if unable to...
• 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 <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)