Skip to content

fix: disable connectrpc default features; bump lock to 0.6.1#15

Closed
connyay wants to merge 1 commit into
mathematic-inc:mainfrom
connyay:cjh-less-connect
Closed

fix: disable connectrpc default features; bump lock to 0.6.1#15
connyay wants to merge 1 commit into
mathematic-inc:mainfrom
connyay:cjh-less-connect

Conversation

@connyay

@connyay connyay commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

protovalidate-buffa only uses connectrpc's ConnectError/ErrorCode types (src/connect.rs), but declared the dep with default features on. Those defaults are gzip + zstd + streaming, and because the connect feature is on by default and Cargo unifies features additively across the graph, every downstream consumer was forced to build zstd — whose C bindings don't compile on wasm32-unknown-unknown — regardless of their own default-features = false. Set default-features = false here so the crate requests only what it uses.

Also bump Cargo.lock from connectrpc 0.6.0 to 0.6.1. 0.6.0 fails to compile (ClientTransport::send trait returns Result while the impl returns BoxFuture, E0053); 0.6.1 fixes the trait signature. The existing version = "0.6" spec already permitted it.

protovalidate-buffa only uses connectrpc's ConnectError/ErrorCode types
(src/connect.rs), but declared the dep with default features on. Those
defaults are gzip + zstd + streaming, and because the `connect` feature
is on by default and Cargo unifies features additively across the graph,
every downstream consumer was forced to build zstd — whose C bindings
don't compile on wasm32-unknown-unknown — regardless of their own
`default-features = false`. Set `default-features = false` here so the
crate requests only what it uses.

Also bump Cargo.lock from connectrpc 0.6.0 to 0.6.1. 0.6.0 fails to
compile (ClientTransport::send trait returns Result while the impl
returns BoxFuture, E0053); 0.6.1 fixes the trait signature. The existing
`version = "0.6"` spec already permitted it.
@jrandolf

Copy link
Copy Markdown
Contributor

Fixed in #17.

@jrandolf jrandolf closed this Jun 28, 2026
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