build(deps): bump prost-build from 0.13.5 to 0.14.3#15
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [prost-build](https://github.com/tokio-rs/prost) from 0.13.5 to 0.14.3. - [Release notes](https://github.com/tokio-rs/prost/releases) - [Changelog](https://github.com/tokio-rs/prost/blob/master/CHANGELOG.md) - [Commits](tokio-rs/prost@v0.13.5...v0.14.3) --- updated-dependencies: - dependency-name: prost-build dependency-version: 0.14.3 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Member
|
Superseded by #25 (Cluster A: full tonic 0.14 + tonic-prost-build coordinated upgrade). |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
satyakwok
added a commit
that referenced
this pull request
May 12, 2026
… 0.6→0.7 tonic 0.14 split prost integration into separate `tonic-prost` (runtime) + `tonic-prost-build` (codegen) crates. tonic itself no longer exposes the `prost` feature. build.rs: tonic_build::configure() → tonic_prost_build::configure() compile_protos_with_config() → compile_with_config() (renamed in 0.14) Cargo.toml: runtime: drop tonic["prost"] feature, add tonic-prost dep build-dep: tonic-build → tonic-prost-build, prost-build 0.13 → 0.14 tonic-web-wasm-client 0.6 → 0.9 (matches tonic 0.14) gloo-net 0.6 → 0.7 The gloo-net bump is required to align the WASM bundle on a single wasm-streams version. tonic-web-wasm-client 0.9 needs wasm-streams 0.5; gloo-net 0.6 still pulled wasm-streams 0.4. Rust-lld then hard-failed with hundreds of duplicate-symbol errors on `__wbindgen_describe_*` exports because both versions register the same wasm-bindgen functions. gloo-net 0.7 dropped to wasm-streams 0.5 — single version, link clean. Verification: cargo leptos build --release (full mainnet bundle, WASM + SSR) cargo check --target wasm32 (browser path) Supersedes #19 (gloo-net), supersedes the earlier #15/#23 already closed.
satyakwok
added a commit
that referenced
this pull request
May 12, 2026
… 0.6→0.7 (#25) tonic 0.14 split prost integration into separate `tonic-prost` (runtime) + `tonic-prost-build` (codegen) crates. tonic itself no longer exposes the `prost` feature. build.rs: tonic_build::configure() → tonic_prost_build::configure() compile_protos_with_config() → compile_with_config() (renamed in 0.14) Cargo.toml: runtime: drop tonic["prost"] feature, add tonic-prost dep build-dep: tonic-build → tonic-prost-build, prost-build 0.13 → 0.14 tonic-web-wasm-client 0.6 → 0.9 (matches tonic 0.14) gloo-net 0.6 → 0.7 The gloo-net bump is required to align the WASM bundle on a single wasm-streams version. tonic-web-wasm-client 0.9 needs wasm-streams 0.5; gloo-net 0.6 still pulled wasm-streams 0.4. Rust-lld then hard-failed with hundreds of duplicate-symbol errors on `__wbindgen_describe_*` exports because both versions register the same wasm-bindgen functions. gloo-net 0.7 dropped to wasm-streams 0.5 — single version, link clean. Verification: cargo leptos build --release (full mainnet bundle, WASM + SSR) cargo check --target wasm32 (browser path) Supersedes #19 (gloo-net), supersedes the earlier #15/#23 already closed.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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 prost-build from 0.13.5 to 0.14.3.
Changelog
Sourced from prost-build's changelog.
... (truncated)
Commits
fafa97fchore: remove protobuf submodule and leverage cmake for it (#1389)e0643e2release 0.14.35595b61fix: Add backDecodeError::new(#1382)e42dcadBufix: Name::full_name() is correct for empty packages (#1386)107153fbuild(deps): update pulldown-cmark-to-cmark requirement from 21 to 22 (#1384)3fc7003build(deps): bump actions/upload-artifact from 5 to 6 (#1381)33f8721fix some forgotten prost import paths (#1385)efb0755chore: Release version 0.14.2 (#1372)91a093ftest(derive_copy): Allow dead code (#1362)2c22c59build(deps): bump actions/checkout from 5 to 6 (#1370)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)