tests: Bump wasm-bindgen in wasm test lockfiles to fix CI on Rust 1.97 - #2251
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
lexnv
approved these changes
Jul 21, 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In this PR, we bump
wasm-bindgenfrom 0.2.93 to 0.2.126 in the standalone lockfiles of thewasm-rpc-testsandwasm-lightclient-testscrates, along with the pairedwasm-bindgen-test0.3.43 -> 0.3.76,js-sys/web-sys0.3.70 -> 0.3.103,wasm-bindgen-futures0.4.43 -> 0.4.76, and the small transitive bumps needed to unlock them (async-trait,libm).This fixes the
Test (WASM)failure on master (failing run). Rust 1.97 enables v0 symbol mangling by default, andwasm-bindgenversions before 0.2.106 emit duplicate export names for closure conversions under the new scheme.