Skip to content
BitGo SDK

feat(sdk-core): add getEddsaMpcV2RecoveryKeyShares helper #29932

Sign in to view logs

feat(sdk-core): add getEddsaMpcV2RecoveryKeyShares helper

feat(sdk-core): add getEddsaMpcV2RecoveryKeyShares helper #29932

Triggered via pull request June 2, 2026 07:07
@bitgo-ai-agent-devbitgo-ai-agent-dev[bot]
synchronize #8913
WCI-396/add-eddsa-mpcv2-recovery-key-shares
Status Failure
Total duration 9m 22s
Artifacts 1

ci.yml

on: pull_request
browser-test
6m 42s
browser-test
docker-build
8m 48s
docker-build
verify-vendor-integrity
7s
verify-vendor-integrity
verify-npm-packages
9s
verify-npm-packages
dockerfile-check
2m 3s
dockerfile-check
Matrix: code-quality
Matrix: unit-test
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 1 warning
dockerfile-check
Process completed with exit code 1.
code-quality (dependencies)
Process completed with exit code 1.
browser-test
Process completed with exit code 1.
browser-test
Module '@bitgo/sdk-api' has already exported a member named 'encryptV2'. Consider explicitly re-exporting to resolve the ambiguity.
browser-test
Module '@bitgo/sdk-api' has already exported a member named 'decryptAsync'. Consider explicitly re-exporting to resolve the ambiguity.
unit-test (24.x)
Process completed with exit code 1.
unit-test (24.x)
Module '@bitgo/sdk-api' has already exported a member named 'encryptV2'. Consider explicitly re-exporting to resolve the ambiguity.
unit-test (24.x)
Module '@bitgo/sdk-api' has already exported a member named 'decryptAsync'. Consider explicitly re-exporting to resolve the ambiguity.
unit-test (22.x)
Process completed with exit code 1.
unit-test (22.x)
Module '@bitgo/sdk-api' has already exported a member named 'encryptV2'. Consider explicitly re-exporting to resolve the ambiguity.
unit-test (22.x)
Module '@bitgo/sdk-api' has already exported a member named 'decryptAsync'. Consider explicitly re-exporting to resolve the ambiguity.
docker-build
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c rm -rf modules/**/node_modules modules/**/dist && sfw yarn install --frozen-lockfile && sfw yarn install --production --frozen-lockfile --non-interactive --ignore-scripts && rm -r modules/*/src" did not complete successfully: exit code: 1
unit-test (20.x)
Process completed with exit code 1.
unit-test (20.x)
Module '@bitgo/sdk-api' has already exported a member named 'encryptV2'. Consider explicitly re-exporting to resolve the ambiguity.
unit-test (20.x)
Module '@bitgo/sdk-api' has already exported a member named 'decryptAsync'. Consider explicitly re-exporting to resolve the ambiguity.
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 16th, 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~MK4HYF.dockerbuild
102 KB
sha256:8e7742a6b83c2ef054efe8f21fc79dd7a507797292f5f06c9a7ad7c32ceae2d7