Skip to content

release: v0.8.1#216

Merged
iainmcgin merged 2 commits into
mainfrom
release/v0.8.1
Jul 2, 2026
Merged

release: v0.8.1#216
iainmcgin merged 2 commits into
mainfrom
release/v0.8.1

Conversation

@iainmcgin

Copy link
Copy Markdown
Collaborator

Cuts the 0.8.1 patch release: connectrpc moves to 0.8.1 carrying the #214/#215 fix (client stream message() futures are Send again with concrete generated view types). The four companion crates are unchanged and stay at 0.8.0 — the publish workflow skips already-published versions.

First release through the changie fragment workflow: the unreleased fragment is batched into .changes/0.8.1.md via task changelog-batch -- 0.8.1 and CHANGELOG.md regenerated with changelog-merge, so check-changelog verifies the assembly.

Semver note (carried from #215): cargo semver-checks flags the added generic parameter on message() as formally major; the waiver rationale is in #215's description — the formal break surface is turbofish that cannot exist against 0.8.0, weighed against the real regression of streaming clients being unusable in tokio::spawn.

After merge: signed v0.8.1 tag → release.yml (binaries; the plugin is unchanged, so v0.8.1 assets carry the 0.8.0-versioned binary) + publish-crates.yml (crates.io via the re-pointed Trusted Publishing).

connectrpc moves to 0.8.1 with the #214 Send fix; the changelog fragment
is batched into .changes/0.8.1.md via changie (first release through the
fragment workflow). The four companion crates are unchanged and stay at
0.8.0 - the publish workflow skips already-published versions.

Signed-off-by: Iain McGinniss <309153+iainmcgin@users.noreply.github.com>
@iainmcgin iainmcgin requested a review from rpb-ant July 2, 2026 17:37
@iainmcgin iainmcgin enabled auto-merge July 2, 2026 17:37
@iainmcgin iainmcgin added this pull request to the merge queue Jul 2, 2026
Merged via the queue into main with commit 0b9e25a Jul 2, 2026
14 checks passed
@iainmcgin iainmcgin deleted the release/v0.8.1 branch July 2, 2026 18:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants