Bump buffa to v0.3.0 and migrate to TypeRegistry API#24
Merged
Conversation
buffa v0.3.0 renamed AnyRegistry to TypeRegistry. The deprecated aliases still exist, but register_wkt_types now takes &mut TypeRegistry, so the conformance crate's init function must use the new types directly. - AnyRegistry -> TypeRegistry - AnyTypeEntry -> JsonAnyEntry - .register() -> .register_json_any() - set_any_registry(Box::new(r)) -> set_type_registry(r) - init_any_registry -> init_type_registry (internal rename)
asacamano
approved these changes
Apr 1, 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.
Bumps the buffa workspace dependencies (
buffa,buffa-types,buffa-codegen) from0.2to0.3.buffa v0.3.0 renamed
AnyRegistry→TypeRegistryandAnyTypeEntry→JsonAnyEntry(the old names remain as deprecated aliases for one release cycle). However,buffa_types::register_wkt_typesnow takes&mut TypeRegistrydirectly, so the conformance crate's registry initialization must use the new types.Changes:
Cargo.toml: workspace deps0.2→0.3conformance/src/lib.rs: migrate toTypeRegistry/JsonAnyEntry/register_json_any/set_type_registry; renameinit_any_registry→init_type_registryconformance/src/bin/{client,server}.rs: update import and call sitecargo test --workspace: 294 passed, 0 failed.Prerequisite for the connect-rust v0.3.0 release.
Note (separate issue, not addressed here):
cargo clippy --all-targetsreveals 3 pre-existing compile errors inbenches/rpc/benches/{rpc_bench,cross_impl_bench}.rsthat exist onmainindependently of this change — the bench callers are out of sync with the checked-in generated client stubs. CI doesn't build with--all-targetsso this slipped through. Will address in a follow-up.