release: 0.7.0#158
Merged
Merged
Conversation
|
All contributors have signed the CLA ✍️ ✅ |
Collaborator
Author
|
waiting for the streaming err handling fix and reflection crate before release |
rpb-ant
previously approved these changes
Jun 10, 2026
…alth and reflection crates) Bump all five crates to 0.7.0 in lockstep; connectrpc-health and connectrpc-reflection join the scheme with their first published versions. Add the missing connectrpc-health and connectrpc-reflection steps to the publish workflow. Restructure the changelog into one coherent 0.7.0 entry: a single intro and Breaking section covering both the server-side request rework and the client streaming terminal-error contract, a previously missing entry for connectrpc-health, a new entry for the inter-message timer fix, PR references on the streaming entries, and a before/after handler signature for the ServiceRequest migration. Documentation accuracy pass: bump stale dependency versions across README and guide, fix the guide's RequestContext accessor usage and ConnectError field sketch, add a Server reflection guide section and a fifth crate-table row, document when the inter-message timer arms, state the streaming-client error contract in the guide, fix the reflection crate's build.rs quick-start to the real Config API, and add docs.rs feature-badge metadata to both new crates. Align the default CompressionProvider::decompress_with_limit with the built-in providers: read failures now map to invalid_argument instead of internal, with a regression test.
rpb-ant
approved these changes
Jun 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prepares the 0.7.0 release: lockstep version bumps for five crates, changelog restructuring and finalization, a documentation accuracy pass across README / guide / rustdoc, and one small behavior fix surfaced by the pre-release audit.
Release mechanics
connectrpc,connectrpc-codegen,connectrpc-build, plusconnectrpc-health(Add newconnectrpc-healthcrate #128) andconnectrpc-reflection(Add connectrpc-reflection crate (gRPC server reflection v1 + v1alpha) #157), which both join the lockstep scheme with this as their first published version. Inter-crate version requirements move to0.7.publish-crates.ymlgains publish steps forconnectrpc-healthandconnectrpc-reflection— the workflow previously published only three crates, so a tag push would have silently skipped both new crates.all-features+--cfg docsrs) and feature badges on theirclient-gated re-exports, matching theconnectrpcpattern.Changelog
The
[Unreleased]section accumulated two stacked fragments (the #143 conversion plus the #159/#160 entries appended above it). Restructured into one coherent[0.7.0] - 2026-06-10entry:ServiceRequest/StreamMessageon buffa 0.7.0) and the client streaming terminal-error contract, with a before/after handler-signature snippet and PR references on the streaming entries.connectrpc-health(Add newconnectrpc-healthcrate #128) and the inter-message timer fix (deadline: don't arm inter-message timer before first item is yielded #127, including the corrected first-poll arming semantics).unavailablebehavior predates this release.Documentation accuracy pass
Err-on-terminal-error contract, bidi snippet fixed to unwrap theOptionbefore.reborrow(), inter-message timeout wording updated for deadline: don't arm inter-message timer before first item is yielded #127,ctx.deadlinefield access replaced with the real accessors,ConnectErrorsketch corrected, stale0.5/0.6version snippets bumped.connectrpc-reflection's build.rs quick-start used the prost-stylecompile(&files, &includes)signature that doesn't exist — fixed to the realConfigAPI;with_inter_message_timeoutnow documents when the timer arms;connectrpccrate-doc module index and Protocol Support section refreshed; duplicatedServerStreamsummary line removed.Behavior fix
The default
CompressionProvider::decompress_with_limitimplementation mapped read failures tointernal, while #144 moved the built-in providers toinvalid_argument— a custom provider relying on the default would silently keep the old 5xx behavior the changelog says was fixed. The default now maps read failures toinvalid_argument, with a documented convention and a regression test.Verification
task lint(clippy all targets-D warnings+ nightly fmt) cleantask testpassestask doc(broken intra-doc links denied) cleanAfter merge
Tag
v0.7.0on the merge commit to trigger crates.io publish (now five crates) and the binary release. Post-release follow-up: regenerateexamples/bazel/Cargo.lockagainst the published 0.7.0 crates (its pins cannot resolve before publish). Optional: pick up buffa 0.7.1 in lockfiles when it ships — the0.7floor needs no change.