Fix audit-trail Move security audit findings #1261
chrisgitiotabuild-and-test.yml
on: pull_request
check-for-run-condition
2s
Matrix: build-wasm-audit-trail / build-wasm
Matrix: build-wasm-notarization / build-wasm
test-wasm-audit-trail
10m 41s
Matrix: test-wasm-browser-audit-trail
Matrix: test-wasm-browser-notarization
Matrix: test-wasm-notarization
Matrix: build-and-test
Annotations
20 errors, 17 warnings, and 1 notice
|
test-wasm-browser-notarization (chrome)
Cannot find name 'TransactionEffects'. Did you mean 'AnimationEffect'?
|
|
test-wasm-browser-notarization (chrome)
Cannot find name 'IotaEvent'.
|
|
test-wasm-browser-notarization (chrome)
Cannot find name 'TransactionEffects'. Did you mean 'AnimationEffect'?
|
|
test-wasm-browser-notarization (chrome)
Cannot find name 'IotaEvent'.
|
|
test-wasm-browser-notarization (chrome)
Cannot find name 'TransactionEffects'. Did you mean 'AnimationEffect'?
|
|
test-wasm-browser-notarization (chrome)
Cannot find module '@iota/iota_interaction_ts/http_client' or its corresponding type declarations.
|
|
test-wasm-browser-notarization (chrome)
Module '"./index"' has no exported member 'CoreClientReadOnly'.
|
|
test-wasm-browser-notarization (chrome)
Module '"./index"' has no exported member 'CoreClient'.
|
|
test-wasm-browser-notarization (chrome)
Cannot find module './iota_client_helpers' or its corresponding type declarations.
|
|
test-wasm-browser-notarization (chrome)
Cannot find module './iota_interaction_ts.js' or its corresponding type declarations.
|
|
test-wasm-browser-notarization (firefox)
Cannot find name 'TransactionEffects'. Did you mean 'AnimationEffect'?
|
|
test-wasm-browser-notarization (firefox)
Cannot find name 'IotaEvent'.
|
|
test-wasm-browser-notarization (firefox)
Cannot find name 'TransactionEffects'. Did you mean 'AnimationEffect'?
|
|
test-wasm-browser-notarization (firefox)
Cannot find name 'IotaEvent'.
|
|
test-wasm-browser-notarization (firefox)
Cannot find name 'TransactionEffects'. Did you mean 'AnimationEffect'?
|
|
test-wasm-browser-notarization (firefox)
Cannot find module '@iota/iota_interaction_ts/http_client' or its corresponding type declarations.
|
|
test-wasm-browser-notarization (firefox)
Module '"./index"' has no exported member 'CoreClientReadOnly'.
|
|
test-wasm-browser-notarization (firefox)
Module '"./index"' has no exported member 'CoreClient'.
|
|
test-wasm-browser-notarization (firefox)
Cannot find module './iota_client_helpers' or its corresponding type declarations.
|
|
test-wasm-browser-notarization (firefox)
Cannot find module './iota_interaction_ts.js' or its corresponding type declarations.
|
|
check-for-modification
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. 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/
|
|
build-wasm-notarization / build-wasm (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/setup-node@v1, actions/upload-artifact@v4, jetli/wasm-bindgen-action@24ba6f9fff570246106ac3f80f35185600c3f6c9. 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/
|
|
build-wasm-notarization / build-wasm (ubuntu-latest)
Unexpected input(s) 'target-cache-key-suffix', valid inputs are ['target', 'toolchain', 'components', 'os', 'job', 'cargo-cache-enabled', 'target-cache-enabled', 'target-cache-path', 'sccache-enabled', 'sccache-path']
|
|
build-wasm-notarization / build-wasm (ubuntu-latest)
Unexpected input(s) 'target-cache-key-suffix', valid inputs are ['target', 'toolchain', 'components', 'os', 'job', 'cargo-cache-enabled', 'target-cache-enabled', 'target-cache-path', 'sccache-enabled', 'sccache-path']
|
|
build-wasm-audit-trail / build-wasm (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/setup-node@v1, actions/upload-artifact@v4, jetli/wasm-bindgen-action@24ba6f9fff570246106ac3f80f35185600c3f6c9. 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/
|
|
build-wasm-audit-trail / build-wasm (ubuntu-latest)
Unexpected input(s) 'target-cache-key-suffix', valid inputs are ['target', 'toolchain', 'components', 'os', 'job', 'cargo-cache-enabled', 'target-cache-enabled', 'target-cache-path', 'sccache-enabled', 'sccache-path']
|
|
build-wasm-audit-trail / build-wasm (ubuntu-latest)
Unexpected input(s) 'target-cache-key-suffix', valid inputs are ['target', 'toolchain', 'components', 'os', 'job', 'cargo-cache-enabled', 'target-cache-enabled', 'target-cache-path', 'sccache-enabled', 'sccache-path']
|
|
test-wasm-notarization (ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/download-artifact@v4, actions/setup-node@v1. 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/
|
|
test-wasm-browser-notarization (chrome)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/download-artifact@v4, actions/setup-node@v1, docker/build-push-action@v6.2.0. 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/
|
|
test-wasm-browser-notarization (firefox)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/download-artifact@v4, actions/setup-node@v1, docker/build-push-action@v6.2.0. 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/
|
|
test-wasm-audit-trail
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/download-artifact@v4, actions/setup-node@v1. 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/
|
|
test-wasm-browser-audit-trail (chrome)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/download-artifact@v4, actions/setup-node@v1, docker/build-push-action@v6.2.0. 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/
|
|
test-wasm-browser-audit-trail (firefox)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/download-artifact@v4, actions/setup-node@v1, docker/build-push-action@v6.2.0. 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/
|
|
build-and-test (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3. 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/
|
|
build-and-test (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4. 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/
|
|
build-and-test (macos-latest)
postgresql@14 has been deprecated because it is not supported upstream! It will be disabled on 2026-11-12.
|
|
build-and-test (ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4. 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/
|
|
build-and-test (windows-latest)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
audit-trail-wasm-bindings-build
Expired
|
3.7 MB |
sha256:fdbf4378b4ab42bcff917c3a46de3d1cf78092072ba1201cddcbcb287a1a4173
|
|
|
iota-server-logs-build-and-test-linux-26214139144-1261-1.log
Expired
|
1.09 MB |
sha256:42a1e787cf43b183a6af01c8fef4f5db07a44cb8ecc2528799f70497eda4f950
|
|
|
iota-server-logs-build-and-test-macos-26214139144-1261-1.log
Expired
|
1.03 MB |
sha256:9e7307cfb05b090a829b815895443af106cd4f3aaafffd4e33a2890b34df6f33
|
|
|
iotaledger~notarization~5FY6QV.dockerbuild
|
21.4 KB |
sha256:90d454b2b13cf81945197c606570ddde00203aef93660483fbb4b35cf52762e0
|
|
|
iotaledger~notarization~IO47MW.dockerbuild
|
21.2 KB |
sha256:fd13db701824d3b45b862885feaf9976a1f8d5ae0fd950074ddb1d0bac94e7a2
|
|
|
iotaledger~notarization~OZNOZP.dockerbuild
|
22 KB |
sha256:b004b50c9ebe27e3cfac4cb812480d8efd3d701d770d11fd112f722035abe22b
|
|
|
iotaledger~notarization~Y8W08I.dockerbuild
|
21.3 KB |
sha256:3b9c33e22821b39f682aeec7c4b5b8cb41310189d036abefa2f134935b687a88
|
|
|
notarization-wasm-bindings-build
Expired
|
3.37 MB |
sha256:0e18650e1c6d39a98c0ca5a8254f3b7bcd6f9002c9a428a3bff2a79f8a7979d3
|
|