As indicated in #1554, we're not catching changes that impact real-world WASM use in CICD.
Originally, our WASM implementation was a best-effort path as reqwest (our first-class supported HTTP backend) did not support WASM. Now that reqwest supports WASM, we should update our CICD to validate WASM with the default features.
As indicated in #1554, we're not catching changes that impact real-world WASM use in CICD.
Originally, our WASM implementation was a best-effort path as reqwest (our first-class supported HTTP backend) did not support WASM. Now that reqwest supports WASM, we should update our CICD to validate WASM with the default features.