Conversation
Lockstep bump of all three crates to 0.3.1: connectrpc, connectrpc-codegen, connectrpc-build. Only connectrpc-codegen and connectrpc-build have user-facing changes this cycle (emit_register_fn plumbing in #35), but the runtime crate is bumped along with them so the user-facing version story stays simple — "use 0.3.1 everywhere". Path-dep version constraint (build → codegen) already uses caret "0.3", so no change required there. README dependency snippets are also caret "0.3", unchanged. CHANGELOG gains a 0.3.1 section with the emit_register_fn entry.
asacamano
approved these changes
Apr 2, 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.
2 participants
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
Lockstep bump of all three crates to 0.3.1:
connectrpc,connectrpc-codegen,connectrpc-build.What changed this cycle
Only
connectrpc-codegenandconnectrpc-buildhave user-facing changes — theemit_register_fnplumbing in #35 (ConnectRPC'sOptions/Confignow expose buffa'semit_register_fnknob, with a matchingno_register_fnplugin parameter). Theconnectrpcruntime is unchanged.Why lockstep on a two-of-three patch
The first patch since the lockstep v0.3.0 release surfaced the "independent vs lockstep on patches" question that's been open since v0.2.1 (tracked on #10). Going lockstep again here for two reasons:
connectrpcruntime at 0.3.0 whilecodegenandbuildjump to 0.3.1. Taggingv0.3.1then ships a runtime binary that's bit-identical to v0.3.0's — confusing in the release listing. Lockstep keeps every tag's binaries reflecting the tagged version.connectrpc-codegenemits source that calls into theconnectrpcruntime crate. There's no[dependencies]declaration that captures this — Cargo's resolver can't enforce "codegen X needs runtime ≥Y". Lockstep makes the user-facing story trivially correct ("use 0.3.x for all three"). The risk is zero on this particular release (no new runtime API surface), but the policy choice is forward-looking.The trade-off is one zero-diff publish (
connectrpc@0.3.1is index cruft on crates.io). That's a small price for the simpler mental model.When we adopt sampo for release management (mentioned by a contributor — supports a "fixed groups" config that gives exactly this lockstep property automatically), this stops being a per-release decision. I'll capture the lockstep choice in #10's runbook when we get to it.
Files changed
connectrpc/Cargo.toml: 0.3.0 → 0.3.1connectrpc-codegen/Cargo.toml: 0.3.0 → 0.3.1connectrpc-build/Cargo.toml: 0.3.0 → 0.3.1CHANGELOG.md: new[0.3.1] - 2026-04-02section with theemit_register_fnentry and Expose emit_register_fn option in codegen and build configs #35 link referenceThe path-dep constraint (
connectrpc-build→connectrpc-codegen) already uses caret"0.3", so no change required there. README dependency snippets are also caret"0.3", unchanged.Test Plan
cargo build --workspaceclean with the bumped versions. Tests, clippy, and fmt all green from #35; this PR is metadata-only on top of that.