v1.4.0

What's Changed

Enhancements

• Improve panic message on invalid handler returns by @akshayjshah in #415
• Add support for Connect-Protocol-Version header by @akshayjshah in #416

Migration Notes

As a consequence of #416, connect-go servers exposed to web browsers may need to amend their CORS configuration to add Connect-Protocol-Version to Access-Control-Allow-Headers. The pull request description explains the motivation for this additional header.

Full Changelog: v1.3.2...v1.4.0

v1.3.2

What's Changed

Bugfixes

• Send gRPC error metadata only as HTTP trailers by @akshayjshah in #410

Full Changelog: v1.3.1...v1.3.2

v1.3.1

What's Changed

Bugfixes

• Don't re-wrap Any when creating ErrorDetails by @jhump in #409

New Contributors

• @jhump made their first contribution in #409

Full Changelog: v1.3.0...v1.3.1

v1.3.0

What's Changed

Enhancements

• Ensure streaming http.ResponseWriters implement http.Flusher by @akshayjshah in #406
• Close TLS connection when HTTP/1.1 clients call bidi methods by @akshayjshah in #408

Full Changelog: v1.2.0...v1.3.0

v1.2.0

What's Changed

Enhancements

• Allow streaming clients to only send headers by @Linniem in #386
• Add RPC protocol to Peer by @akshayjshah in #394

Bugfixes

• Fix potential panic receiving invalid error codes by @joshcarp in #398

New Contributors

• @Linniem made their first contribution in #386

Full Changelog: v1.1.0...v1.2.0

v1.1.0

What's Changed

Enhancements

• Add IsWireError to differentiate server-sent and client-synthesized errors by @joshcarp in #374

New Contributors

• @joshcarp made their first contribution in #374

Full Changelog: v1.0.0...v1.1.0

v1.0.0

What's Changed

This is connect-go's first stable release! 🎉 It doesn't contain any user-facing changes.

We follow semantic versioning carefully, and won't make breaking changes in the 1.x series of releases.

Full Changelog: v0.5.0...v1.0.0

v0.5.0

What's Changed

Enhancements

• Add a helper to write RPC errors from net/http middleware by @rhbuf in #337
• Expose peer information to handlers and clients by @akshayjshah in #364
• Interoperate cleanly with http.MaxBytesHandler by @akshayjshah in #355
• Support application/json; charset=utf8 Content-Type by @buildbreaker in #358

Bugfixes

• Fix error code for ReadMaxBytes by @akshayjshah in #354

Other changes

• Improve test coverage of bidi streams @pkwarren in #352
• Shorten stability section of README by @akshayjshah in #353
• Add Github Actions workflow to notify on unreviewed changes by @rubensf in #365

New Contributors

• @rhbuf made their first contribution in #337

Full Changelog: v0.4.0...v0.5.0

v0.4.0

What's Changed

Enhancements

• Add SendMaxBytes option for clients and handlers by @pkwarren in #341
• Add client option to disable gzip support by @alexandrem in #349
• Use Go 1.19 links in GoDoc by @akshayjshah in #347

Bugfixes

• Handle Go keywords in Protobuf definitions by @akshayjshah in #348

New Contributors

• @rubensf made their first contribution in #338
• @alexandrem made their first contribution in #349

Full Changelog: v0.3.0...v0.4.0

v0.3.0

What's Changed

Breaking Changes

• Send binary data with error details by @akshayjshah in #329
  So that proxies can translate between the Connect and gRPC protocols without a schema, we've changed the Connect protocol to include base64-encoded binary data with error details. Any code sending error details must now create details with connect.NewErrorDetail instead of anypb.New. For code unmarshaling error details, the connect.ErrorDetail type has changed from an interface to a struct with a more-ergonomic Value() method.

Note that we will not make breaking changes in minor releases after connect-go reaches v1.0. We anticipate a stable release around October of 2022, shortly after Go 1.19 is released.

Full Changelog: v0.2.0...v0.3.0