Update wasm-bindgen to 0.2.121#4043
Open
anagrius wants to merge 1 commit into
Open
Conversation
Bumps the bundled wasm-bindgen, wasm-bindgen-cli, and wasm-bindgen-test to their latest stable versions (0.2.121 / 0.3.71). Same shape as bazelbuild#3703; regenerated via `bazel run @@//3rdparty:crates_vendor` from the wasm_bindgen extension against BCR rules_rust 0.70.0. Changes: - `WASM_BINDGEN_VERSION = "0.2.121"` in both repositories.bzl and extensions.bzl - `wasm-bindgen-test` spec → 0.3.71 - Regenerated Cargo.Bazel.lock, extensions/wasm_bindgen/MODULE.bazel use_repo aliases, and the 3rdparty/crates/BUILD.*.bazel set Motivation: downstream consumers want crates that need `wasm-bindgen >= 0.2.108` — for example `wasm-streams 0.5`, pulled in by `tonic-web-wasm-client 0.9+`. With the bundled cli pinned at 0.2.105, downstream code is forced to either vendor-patch tonic-web-wasm-client back to 0.8 (to keep the cli + runtime schema versions aligned) or register a custom rust_wasm_bindgen_toolchain. Verified downstream by overriding rules_rust_wasm_bindgen at this branch in an end-to-end Bazel + cargo-leptos build using tonic-web-wasm-client 0.9 and wasm-streams 0.5; the previous in-tree backport patch on tonic-web-wasm-client 0.8 was dropped in the same change.
anagrius
force-pushed
the
bump-wasm-bindgen-cli-0.2.121
branch
from
ca5c29c to
b02f700
Compare
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
1 participant
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 bundled
wasm-bindgen,wasm-bindgen-cli, andwasm-bindgen-testto their latest stable versions (0.2.121/0.3.71). Same shape as #3703; regenerated viabazel run @@//3rdparty:crates_vendorfrom the wasm_bindgen extension.Changes:
WASM_BINDGEN_VERSION = "0.2.121"in bothrepositories.bzlandextensions.bzlwasm-bindgen-testspec →0.3.71Cargo.Bazel.lock,extensions/wasm_bindgen/MODULE.bazeluse_repoaliases, and the entire3rdparty/crates/BUILD.*.bazelset.Motivation: downstream consumers want crates that need
wasm-bindgen >= 0.2.108— for examplewasm-streams 0.5, pulled in bytonic-web-wasm-client 0.9+. With the bundled cli pinned at0.2.105, downstream code is forced to either vendor-patchtonic-web-wasm-clientback to0.8(to keep the schema versions aligned) or write a customrust_wasm_bindgen_toolchain.