buffa 0.9 support exists only on unreleased main

[AprilNEA]

The published connectrpc 0.8.1 requires buffa ^0.8.1. Support for buffa 0.9 landed in #233 on 2026-07-20, eighteen days after v0.8.1, and there has been no release since — so any project on buffa 0.9.x has to depend on an unreleased git rev. We pin c5c1a6f for exactly this reason.

The part that is not just an inconvenience: a crate pinned that way cannot express itself on crates.io. cargo publish drops the git source and keeps the version requirement, so our published crate declares buffa ^0.9.1 alongside connectrpc ^0.8.1, and cargo resolves two incompatible buffa versions for anyone who consumes it from the registry. Message types generated against buffa 0.9 do not satisfy connectrpc 0.8.1's buffa 0.8 bounds.

Is a 0.9.0 planned? I see the buffa 0.9 move and twelve other improvements sitting unreleased on main, and a batch of API-cleanup PRs (#256–#262) open since 2026-07-24 that look intended for the same release. Happy to help review or test if that is useful.

Related: #10 on versioning policy and the release runbook.

[iainmcgin]

[claude code] 0.9.0 is out: https://github.com/connectrpc/connect-rust/releases/tag/v0.9.0 — all five crates are on crates.io at 0.9.0 with buffa ^0.9.1, so a registry dependency on connectrpc = "0.9" now resolves to one buffa major and your crate can publish without the git pin.

It is a breaking release; the changelog's 0.9.0 section lists each break with its migration, and the ones most likely to touch a crate that was tracking main at c5c1a6f are the Limits/CompressionPolicy setters gaining a with_ prefix, the removal of the unused streaming compression feature, and call_* taking a Spec instead of a service/method pair (generated clients are unaffected; regenerate). Thanks for the nudge — the release was overdue, and the offer to test is appreciated; a report from a real downstream on 0.9.0 would be welcome.