-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Road to v1.0 🥇 #343
Comments
For item 3 (a more complex streaming interceptor), we're planning to implement #344. |
great! and, thanks Buf.Build team, great job. |
We've done enough work on OTel, load balancing, and the protocol to be comfortable with a 1.0. Closing this and cutting a v1 now! |
This isn't a specific issue or proposal. Instead, it outlines the work we need to finish before we tag a stable release of
connect-go
. We're planning to complete all these items by early October at the latest, but I'm hopeful that we'll be able to finish a bit sooner.Ship Provide function to write RPC errors from HTTP middleware #331. We expect Connect handlers to work nicely withnet/http
middleware, and this is the most important missing piece. I'm confident we'll be able to implement this without breaking existing APIs, but it's worth being sure.connect-go
not only commits us to this package's APIs, it also commits us to keeping the Connect protocol backward-compatible. Buf's own Studio product uses the protocol, as do a few early adopters. We'll plan to check in with them, but otherwise there's nothing concrete to do here.We'll plan to keep this issue updated as we make progress. Hopefully we'll tag a 1.0 earlier than planned! 🤞🏽
The text was updated successfully, but these errors were encountered: