Skip to content

Update wasm-bindgen to 0.2.105 - #3703

Merged
UebelAndre merged 1 commit into
bazelbuild:mainfrom
UebelAndre:wasm-bindgen
Nov 6, 2025
Merged

Update wasm-bindgen to 0.2.105#3703
UebelAndre merged 1 commit into
bazelbuild:mainfrom
UebelAndre:wasm-bindgen

Conversation

@UebelAndre

@UebelAndre UebelAndre commented Oct 27, 2025

Copy link
Copy Markdown
Collaborator

https://github.com/wasm-bindgen/wasm-bindgen/blob/0.2.105/CHANGELOG.md#02105

This change greatly simplifies the updating wasm-bindgen versions as there's no longer a need to either use nightly toolchains or complex repsotiory rules to access wasm-bindgen-cli binaries. crate_universe can generate binaries thanks to the new wasm-bindgen-cli library target in 0.2.105.

@UebelAndre
UebelAndre marked this pull request as ready for review October 27, 2025 22:31
@UebelAndre
UebelAndre enabled auto-merge October 27, 2025 22:32
@UebelAndre
UebelAndre added this pull request to the merge queue Nov 6, 2025
Merged via the queue into bazelbuild:main with commit 280114d Nov 6, 2025
3 checks passed
@UebelAndre
UebelAndre deleted the wasm-bindgen branch November 6, 2025 23:36
anagrius added a commit to anagrius/rules_rust that referenced this pull request May 15, 2026
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.
krasimirgg pushed a commit to Suyashagarw/rules_rust that referenced this pull request May 19, 2026
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.

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 entire `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 schema versions aligned) or write a custom
`rust_wasm_bindgen_toolchain`.
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