v0.6.0

[gilwong00]

This release includes the following:

🚨 Breaking Changes 🚨

• Add Connect Protocol Version Header  #370 - The Connect protocol now specifies that a header be set specifying the version of Connect in use. The header name is Connect-Protocol-Version and Connect-Web has been updated to send this header in its requests. As a result, users will need to make sure their CORS settings allowlist this new header, or all Connect requests will fail with this release.

  For more information, see this PR: https://github.com/bufbuild/connect-go/pull/416

Enhancements

• Add Connect Protocol Version Header by @gilwong00 in Add Connect Protocol Version Header  #370

---

This discussion was created from the release v0.6.0.

[nii236]

This took me WAY too long to figure out. Is there an issue tracking the updating of documentation (wiki, guides, tutorials) to reflect this change?

[smaye81]

There isn't, but if you experienced this difficulty then others probably have too. We should add something to our FAQ. Can you elaborate on what specifically was giving you trouble?

[nii236]

Backend developers (Go, in my case) explicitly need to allow headers Connect-Protocol-Version into their CORS middleware. This wasn't immediately clear and I had to dig through pull requests (and consequently, this thread) to figure it out.

I recommend perhaps adding this in the Common Errors section (https://connect.build/docs/go/common-errors).

[smaye81]

Sounds good. Thanks for calling this out. We'll get it added.

[smaye81]

Added a Common Errors page to Connect-Web docs here: https://connect.build/docs/web/common-errors