Skip to content

fix: lazy-load wasm-mps to fix browser wasn initialisation #28904

fix: lazy-load wasm-mps to fix browser wasn initialisation

fix: lazy-load wasm-mps to fix browser wasn initialisation #28904

Triggered via pull request April 27, 2026 13:43
Status Failure
Total duration 23m 22s
Artifacts 1

ci.yml

on: pull_request
browser-test
10m 36s
browser-test
docker-build
12m 9s
docker-build
verify-vendor-integrity
7s
verify-vendor-integrity
verify-npm-packages
15s
verify-npm-packages
dockerfile-check
44s
dockerfile-check
Matrix: code-quality
Matrix: unit-test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
unit-test (20.x)
Process completed with exit code 9.
docker-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
BitGo~BitGoJS~LP0TVY.dockerbuild
200 KB
sha256:3c44d40da935aed2cfcc786a7d9967b448b79faf7d258dee7b8eb0c2f47d4526