feat: add explicit audit trail capability selection #1079
itsyaasirbuild-and-test.yml
on: pull_request
check-for-run-condition
3s
Matrix: build-wasm-audit-trail / build-wasm
Matrix: build-wasm-notarization / build-wasm
test-wasm-audit-trail
6m 52s
Matrix: test-wasm-browser-audit-trail
Matrix: test-wasm-browser-notarization
Matrix: test-wasm-notarization
Matrix: build-and-test
Annotations
23 errors and 17 warnings
|
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.
|
|
test-wasm-audit-trail
Process completed with exit code 13.
|
|
test-wasm-browser-audit-trail (chrome)
Process completed with exit code 1.
|
|
test-wasm-browser-audit-trail (firefox)
Process completed with exit code 1.
|
|
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 (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 (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.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
audit-trail-wasm-bindings-build
Expired
|
3.67 MB |
sha256:32944ac461eeb6802ab0da9d939446e56f42d2e19e06f7de6e67a59374685ea8
|
|
|
iota-server-logs-build-and-test-linux-24236006563-1079-1.log
Expired
|
1.17 MB |
sha256:e8694ae4bbb18ab0a4428e7c106f5b0a39ae1f25c234561fb3c4e65c43bb45ba
|
|
|
iota-server-logs-build-and-test-macos-24236006563-1079-1.log
Expired
|
1.13 MB |
sha256:dafe2f158a3949faf8c5690980155b801b73cf01690845e6619f3c2ff43aa481
|
|
|
iotaledger~notarization~SY95O8.dockerbuild
|
23.7 KB |
sha256:327d2ed2af1779320932911b8f477060e778f937582fab00d23970ef69efbb65
|
|
|
iotaledger~notarization~TB9XZC.dockerbuild
|
22.6 KB |
sha256:762affe121a601f4518223cfc50f344788fcee9073d28203b357eb45b486de10
|
|
|
iotaledger~notarization~X6YM2Z.dockerbuild
|
21.3 KB |
sha256:67a28b9122910a4ce869bbfbcc57041cf844abe386a1ed940791eb654237f90f
|
|
|
iotaledger~notarization~YW77AJ.dockerbuild
|
22.8 KB |
sha256:bbaee6cf255bed975da1c9516ec0c7d973e43916f26cf6a2d528975c5fd392ab
|
|
|
notarization-wasm-bindings-build
Expired
|
3.4 MB |
sha256:cfd55cc62ba7f83d33109f1bef8712dae372fdb41c37e67961ce00c4b673d399
|
|