From 1e4619c5ef93dee9cf0dd9777a6d4ab20272ba1a Mon Sep 17 00:00:00 2001 From: Emil Ernerfeldt Date: Tue, 24 Mar 2026 13:55:28 +0100 Subject: [PATCH] Explain that we shouldn't update wasm-bindgen version willy-nilly --- Cargo.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Cargo.toml b/Cargo.toml index d042c2349..4c8a52626 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -138,8 +138,8 @@ type-map = "0.5.1" unicode_names2 = { version = "2.0.0", default-features = false } unicode-segmentation = "1.12.0" vello_cpu = { version = "0.0.6", default-features = false, features = ["std", "u8_pipeline", "f32_pipeline"] } -wasm-bindgen = "0.2.108" # Keep wasm-bindgen version in sync in: setup_web.sh, Cargo.toml, Cargo.lock, rust.yml -wasm-bindgen-futures = "0.4.0" +wasm-bindgen = "0.2.108" # Keep wasm-bindgen version in sync in: setup_web.sh, Cargo.toml, Cargo.lock, rust.yml. Don't update this spuriously, because of https://github.com/rerun-io/rerun/issues/8766 +wasm-bindgen-futures = "0.4.58" wayland-cursor = { version = "0.31.11", default-features = false } web-sys = "0.3.77" web-time = "1.1.0" # Timekeeping for native and web