refactor(dapi,dpp)!: move dapi-client and Identifier off Buffer to Uint8Array #12197
PastaPastaPastatests.yml
on: pull_request
Determine changed packages
33s
Check secret availability
3s
JS dependency versions check
14s
Matrix: Rust workspace tests / test-ubuntu
Waiting for pending jobs
Rust workspace tests
/
Formatting & Linting backup
Rust workspace tests
/
Tests (macOS)
Rust doctests
/
Doctests backup
0s
Matrix: Build Docker images
Matrix: JS packages
Swift SDK build
/
Swift SDK build + tests (warnings as errors)
Packages functional tests
/
Run functional tests
Matrix: Dashmate E2E tests
Waiting for pending jobs
Matrix: Test Suite
Waiting for pending jobs
Annotations
3 errors, 42 warnings, and 1 notice
|
Build JS packages / Build JS
Unable to download artifact(s): Artifact not found for name: js-build-ceae51d036be859cd53f8a719a8954d4e7c94074
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
|
Build Docker images (Drive, drive, drive-abci, SDK_TEST_DATA=true
) / Build Drive image
The job has exceeded the maximum execution time of 30m0s
|
|
Build Docker images (Drive, drive, drive-abci, SDK_TEST_DATA=true
) / Build Drive image
The operation was canceled.
|
|
JS dependency versions check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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/
|
|
Determine changed packages
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@v3. 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/
|
|
Build Docker images (RS-DAPI, rs-dapi, rs-dapi) / Build RS-DAPI image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/github-script@v6, aws-actions/configure-aws-credentials@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, reproducible-containers/buildkit-cache-dance@v3.1.2. 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/
|
|
Build Docker images (RS-DAPI, rs-dapi, rs-dapi) / Build RS-DAPI image
Input 'install' has been deprecated with message: "docker buildx install" command is deprecated and will be removed in a future release, use BUILDX_BUILDER environment variable instead
|
|
Sensitive data should not be used in the ARG or ENV commands:
Dockerfile#L210
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SCCACHE_S3_KEY_PREFIX")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Build Docker images (RS-DAPI, rs-dapi, rs-dapi) / Build RS-DAPI image
Input 'install' has been deprecated with message: "docker buildx install" command is deprecated and will be removed in a future release, use BUILDX_BUILDER environment variable instead
|
|
Build Docker images (Dashmate helper, dashmate-helper, dashmate-helper) / Build Dashmate helper image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/github-script@v6, aws-actions/configure-aws-credentials@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, reproducible-containers/buildkit-cache-dance@v3.1.2. 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/
|
|
Build Docker images (Dashmate helper, dashmate-helper, dashmate-helper) / Build Dashmate helper image
Input 'install' has been deprecated with message: "docker buildx install" command is deprecated and will be removed in a future release, use BUILDX_BUILDER environment variable instead
|
|
Sensitive data should not be used in the ARG or ENV commands:
Dockerfile#L210
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SCCACHE_S3_KEY_PREFIX")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Build Docker images (Dashmate helper, dashmate-helper, dashmate-helper) / Build Dashmate helper image
Input 'install' has been deprecated with message: "docker buildx install" command is deprecated and will be removed in a future release, use BUILDX_BUILDER environment variable instead
|
|
Build JS packages / Build JS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, docker/login-action@v3, mozilla-actions/sccache-action@v0.0.6. 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/
|
|
JS packages (@dashevo/wallet-lib) / Linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4. 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/
|
|
|
|
|
|
JS packages (@dashevo/wallet-lib) / Linting:
packages/wallet-lib/src/transport/DAPIClientTransport/methods/sendTransaction.js#L6
Expected { after 'if' condition
|
|
JS packages (@dashevo/wallet-lib) / Linting:
packages/wallet-lib/src/test/mocks/dashcore/block.js#L33
Unexpected console statement
|
|
JS packages (@dashevo/wallet-lib) / Linting:
packages/wallet-lib/src/plugins/Workers/TransactionsSyncWorker/utils.js#L90
'e' is defined but never used
|
|
JS packages (@dashevo/wallet-lib) / Linting:
packages/wallet-lib/src/plugins/Worker.js#L139
Expected { after 'if' condition
|
|
JS packages (@dashevo/wallet-lib) / Linting:
packages/wallet-lib/src/plugins/Worker.js#L53
Expected { after 'if' condition
|
|
JS packages (@dashevo/wallet-lib) / Linting:
packages/wallet-lib/src/errors/InvalidTransactionObject.js#L9
Expected { after 'if' condition
|
|
JS packages (@dashevo/wallet-lib) / Linting:
packages/wallet-lib/src/errors/InvalidOutput.js#L9
Expected { after 'if' condition
|
|
JS packages (@dashevo/wallet-lib) / Linting:
packages/wallet-lib/src/errors/InvalidAddressObject.js#L7
Expected { after 'if' condition
|
|
JS packages (@dashevo/dapi-client) / Linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4. 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/
|
|
JS packages (@dashevo/dapi-client) / Linting:
packages/js-dapi-client/lib/utils/bytes.js#L73
Expected { after 'if' condition
|
|
JS packages (@dashevo/dapi-client) / Linting:
packages/js-dapi-client/lib/utils/bytes.js#L60
Expected { after 'for-of'
|
|
JS packages (@dashevo/dapi-client) / Linting:
packages/js-dapi-client/lib/methods/platform/getIdentitiesContractKeys/getIdentitiesContractKeysFactory.js#L7
'IdentityPublicKey' is assigned a value but never used
|
|
JS packages (@dashevo/dapi-client) / Linting:
packages/js-dapi-client/lib/logger/index.js#L29
Unexpected console statement
|
|
JS packages (@dashevo/dapi-client) / Linting:
packages/js-dapi-client/lib/logger/index.js#L28
Unexpected console statement
|
|
JS packages (@dashevo/dapi-client) / Linting:
packages/js-dapi-client/lib/logger/index.js#L27
Unexpected console statement
|
|
JS packages (@dashevo/dapi-client) / Linting:
packages/js-dapi-client/lib/logger/index.js#L26
Unexpected console statement
|
|
JS packages (@dashevo/dapi-client) / Linting:
packages/js-dapi-client/lib/logger/index.js#L25
Unexpected console statement
|
|
JS packages (@dashevo/dapi-client) / Linting:
packages/js-dapi-client/lib/logger/index.js#L24
Unexpected console statement
|
|
JS packages (@dashevo/dapi-client) / Linting:
packages/js-dapi-client/lib/logger/index.js#L17
Expected { after 'if' condition
|
|
JS packages (dashmate) / Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4. 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/
|
|
JS packages (@dashevo/wasm-dpp2) / Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4. 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/
|
|
JS packages (@dashevo/dapi) / Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4. 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/
|
|
JS packages (dash) / Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4. 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/
|
|
JS packages (@dashevo/dapi-client) / Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4. 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/
|
|
JS packages (@dashevo/wallet-lib) / Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4. 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/
|
|
Build Docker images (Drive, drive, drive-abci, SDK_TEST_DATA=true
) / Build Drive image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/github-script@v6, aws-actions/configure-aws-credentials@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, reproducible-containers/buildkit-cache-dance@v3.1.2. 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/
|
|
Build Docker images (Drive, drive, drive-abci, SDK_TEST_DATA=true
) / Build Drive image
Input 'install' has been deprecated with message: "docker buildx install" command is deprecated and will be removed in a future release, use BUILDX_BUILDER environment variable instead
|
|
Build Docker images (Drive, drive, drive-abci, SDK_TEST_DATA=true
) / Build Drive image
Input 'install' has been deprecated with message: "docker buildx install" command is deprecated and will be removed in a future release, use BUILDX_BUILDER environment variable instead
|
|
sccache stats
100% - 1624 hits, 5 misses, 0 errors
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
dashpay~platform~AWHWSI.dockerbuild
|
132 KB |
sha256:9a1f0a1df1858d14225117487828b72bf0e59115a13e7fca8e158a888e61baef
|
|
|
dashpay~platform~JJD3MT.dockerbuild
|
147 KB |
sha256:7ab23719925d20f0d2fc495fd7b570f149584097d4f40f533fdbae3f54debda0
|
|
|
js-build-ceae51d036be859cd53f8a719a8954d4e7c94074
Expired
|
82.7 MB |
sha256:6bd7af9131061d8db512b85d3e85e37c2167e12ce506abf4de14ce647eb13976
|
|