Test with OpenZeppelin Contracts

Add compiler error when reserved type names are used as contract types #814

Triggered via pull request March 25, 2026 19:10

mootz12

synchronize #1788

protected-type-mapping

Status Success

Total duration 3m 48s

Artifacts 92

test-with-openzeppelin-stellar-contracts.yml

on: pull_request

collect-crates

Matrix: test-crate

Annotations

96 warnings

test-crate (packages/macros, true)

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 will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (packages/macros, false)

test-crate (packages/test-utils/event-assertion, true)

test-crate (packages/test-utils/event-assertion, false)

test-crate (packages/governance, true)

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/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/

test-crate (examples/ownable, true)

test-crate (examples/multisig-smart-account/threshold-policy, true)

test-crate (examples/pausable, false)

test-crate (examples/sac-admin-generic, false)

test-crate (examples/fungible-governor/governor, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/ownable, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/upgradeable/lazy-v1, true)

test-crate (packages/fee-abstraction, false)

test-crate (examples/rwa/compliance, true)

test-crate (packages/zk-email, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/merkle-voting, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/upgradeable/lazy-v2, true)

test-crate (examples/rwa/identity, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/rwa/compliance, false)

test-crate (packages/governance, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/timelock-controller, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (packages/zk-email, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/nft-royalties, true)

test-crate (examples/pausable, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/upgradeable/v1, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/multisig-smart-account/account, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-governor/token, true)

test-crate (examples/upgradeable/upgrader, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-allowlist, true)

test-crate (examples/rwa/token, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/multisig-smart-account/webauthn-verifier, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-votes, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/multisig-smart-account/account, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-blocklist, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/multisig-smart-account/threshold-policy, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/upgradeable/upgrader, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fee-forwarder-permissionless, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/rwa/identity-registry, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/timelock-controller, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (packages/access, true)

test-crate (examples/fungible-merkle-airdrop, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-pausable, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/nft-access-control, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-capped, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/upgradeable/lazy-v1, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/sac-admin-generic, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/sac-admin-wrapper, true)

test-crate (examples/nft-consecutive, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/upgradeable/v2, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-merkle-airdrop, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-allowlist, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/multisig-smart-account/ed25519-verifier, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/upgradeable/v1, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/rwa/identity, false)

test-crate (examples/fungible-capped, true)

test-crate (examples/rwa/claim-issuer, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-blocklist, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (packages/accounts, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/sac-admin-wrapper, false)

test-crate (examples/rwa/token, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/nft-consecutive, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/nft-enumerable, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-vault, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/rwa/claim-topics-and-issuers, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (packages/tokens, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (packages/tokens, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-vault, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-governor/governor, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/nft-sequential-minting, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/multisig-smart-account/spending-limit-policy, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-governor/token, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/nft-enumerable, true)

test-crate (examples/rwa/claim-issuer, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (packages/accounts, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/multisig-smart-account/spending-limit-policy, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fee-forwarder-permissionless, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fee-forwarder-permissioned, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/rwa/identity-verifier, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/nft-sequential-minting, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (packages/contract-utils, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (packages/fee-abstraction, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/upgradeable/lazy-v2, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/multisig-smart-account/webauthn-verifier, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/nft-access-control, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/merkle-voting, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/upgradeable/v2, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/rwa/identity-verifier, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/rwa/claim-topics-and-issuers, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (packages/contract-utils, true)

test-crate (examples/fee-forwarder-permissioned, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (packages/access, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-pausable, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/nft-royalties, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/fungible-votes, false)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/multisig-smart-account/ed25519-verifier, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-crate (examples/rwa/identity-registry, true)

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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
wasm-examples-fee-forwarder-permissioned Expired	8.63 KB	`sha256:3a4373c88093538a3a3e98876ccc92f4136b93d5ab53f32bbe137bb35e11718a`
wasm-examples-fee-forwarder-permissioned-spec-shaking-v2 Expired	8.63 KB	`sha256:538ddd88fd41d73922b5f72286d1d324d709bcf18d1e2ff62854ccae6783bf9a`
wasm-examples-fee-forwarder-permissionless Expired	2.66 KB	`sha256:9180b75fdd3c637d1748f1fae9dcbbf61c2b011695f0ddd851d7280838af451c`
wasm-examples-fee-forwarder-permissionless-spec-shaking-v2 Expired	2.66 KB	`sha256:0359f82dee1d39f97f2d9d32fe241fe08699327ca295df09c7bf7e150484d061`
wasm-examples-fungible-allowlist Expired	21.3 KB	`sha256:4a87bccbd4aafb7739f2d637d7a06b89895696da6c2112ca00186b5fd543ea0c`
wasm-examples-fungible-allowlist-spec-shaking-v2 Expired	21.3 KB	`sha256:7f512220364a5604a8df930ac2402ec1bfce1152023fca7eb3ff2d6dbafaa3a2`
wasm-examples-fungible-blocklist Expired	21.3 KB	`sha256:3d5a39846fea72fb3080da807f92baafc6a5ad6cecf34cf3763527173b30f229`
wasm-examples-fungible-blocklist-spec-shaking-v2 Expired	21.3 KB	`sha256:d438764dd1b71346fdfe4cc7bf459abf719fcca01c40b4f391780dc8bb2f886d`
wasm-examples-fungible-capped Expired	16.2 KB	`sha256:2903b31127a2676c8edb5981a50b12ac0808b99ea0a363c50630ced6f20a9996`
wasm-examples-fungible-capped-spec-shaking-v2 Expired	16.2 KB	`sha256:44ce68e16fcf939650e832b6502e3e1eb76e2cf6fd4bee70e197ac7c899b4642`
wasm-examples-fungible-governor-governor Expired	14.8 KB	`sha256:36a9030a0bc554f6a22cfe24fa5cf1e8cb98f0db737aaa898cda2b84cfa18867`
wasm-examples-fungible-governor-governor-spec-shaking-v2 Expired	14.8 KB	`sha256:514a65c7464c0aaaa764b10fdd2777c38224a381fdca7fca1abce42e5bae75e2`
wasm-examples-fungible-governor-token Expired	20.1 KB	`sha256:93e4e73d16ad19ab2f7d8b3d5a3f399e819fba53d14c54a147e9a968e9cfa137`
wasm-examples-fungible-governor-token-spec-shaking-v2 Expired	20.1 KB	`sha256:3f76d2d64c8787182cdccd28a5db2597c3acdb0de1f4e7191d6bed5127c9a9b4`
wasm-examples-fungible-merkle-airdrop Expired	2.89 KB	`sha256:0121799b3f3347547e33b41eea454faac485eea6e275bfba4a78c01c58ab77ac`
wasm-examples-fungible-merkle-airdrop-spec-shaking-v2 Expired	2.89 KB	`sha256:84a520fb5f5e121922365712f73cccd3958be06969eb74893438632029b7fba1`
wasm-examples-fungible-pausable Expired	16 KB	`sha256:fdafaa5f41126b8e8ae7c335312c03d7612d956d5824e0df097c0aa7be8bd0e7`
wasm-examples-fungible-pausable-spec-shaking-v2 Expired	16 KB	`sha256:6d5304efe66be82b0ca1a628aa99866220e2f77134fb79b50f8445340d9cc798`
wasm-examples-fungible-vault Expired	20.7 KB	`sha256:b2f8eee46b7da6310ba33dd4ae4d68b62edbbf1baccea4adffe08edb0725945c`
wasm-examples-fungible-vault-spec-shaking-v2 Expired	20.7 KB	`sha256:3ec14f866f04df686cc9e67e96a88d1ca324dbe7409c464f0b5e2d005fa92a05`
wasm-examples-fungible-votes Expired	20.4 KB	`sha256:1ee9c4b9867ad0166788b8968a1f4b8ac2000b7618779a0d9d6571ec29263a87`
wasm-examples-fungible-votes-spec-shaking-v2 Expired	20.4 KB	`sha256:7fc17be47af2f2c1330e427661691edf7033e5dd077eecfcac48a5cb235ab254`
wasm-examples-merkle-voting Expired	3.09 KB	`sha256:1e9ba722390fdc8151ee618813ca2ef3c53e63c778ea8c0196446bc1030cef16`
wasm-examples-merkle-voting-spec-shaking-v2 Expired	3.09 KB	`sha256:68243e89d9db38b234a2118820a9615e1858344c04a135b7e1413ca6f0065d73`
wasm-examples-multisig-smart-account-account Expired	17.4 KB	`sha256:5859fa3c1d05c3c220480bdd2e90600d5a1fd26f9f47bb9842f5cf1e6f59c296`
wasm-examples-multisig-smart-account-account-spec-shaking-v2 Expired	17.4 KB	`sha256:80966ab093d5f7853733cbb33f3c66c89e73689b956cf195705ea5fd2273a8e6`
wasm-examples-multisig-smart-account-ed25519-verifier Expired	5.62 KB	`sha256:60b6944180647c41a594657458b671c090ab4b55d91700e76769f35d3b87fdac`
wasm-examples-multisig-smart-account-ed25519-verifier-spec-shaking-v2 Expired	5.62 KB	`sha256:a1a80a7cf597766d248081aaa02dc5a2fcf36d6b203cf7f7972a598eb5ebf6a8`
wasm-examples-multisig-smart-account-spending-limit-policy Expired	8.75 KB	`sha256:7a889e1c88d99339a1f7540f894e777fab2e1e49e3245204d6c894f256b1aafc`
wasm-examples-multisig-smart-account-spending-limit-policy-spec-shaking-v2 Expired	8.75 KB	`sha256:6727d700d74bb8337fbc7f6c836f5bd62e63e8770dffe5effa86c9aa24822f94`
wasm-examples-multisig-smart-account-threshold-policy Expired	7.69 KB	`sha256:224fccceb90d6a85f9188fe3df4040e3b1360572741dc4a5e8688e6832770a06`
wasm-examples-multisig-smart-account-threshold-policy-spec-shaking-v2 Expired	7.69 KB	`sha256:a90321b066dfb4863ba28a584a933e34c0bd7780b78c5d28787eabbb55edab76`
wasm-examples-multisig-smart-account-webauthn-verifier Expired	10.5 KB	`sha256:ecb37059302fa563ebf944d0cd61580e2671af457d3177882b498a52aa479803`
wasm-examples-multisig-smart-account-webauthn-verifier-spec-shaking-v2 Expired	10.5 KB	`sha256:b48d100d338d29bada40ed159eb1d67ef5fa30324fca4fe87b9006e1ebff5efc`
wasm-examples-nft-access-control Expired	21.6 KB	`sha256:a8f0ce70a69e7f67a4c62114aef628beddbf4c5f2cacec8ba26206a5e0f90cf6`
wasm-examples-nft-access-control-spec-shaking-v2 Expired	21.6 KB	`sha256:a8f0ce70a69e7f67a4c62114aef628beddbf4c5f2cacec8ba26206a5e0f90cf6`
wasm-examples-nft-consecutive Expired	17.3 KB	`sha256:90c466a46e78a3efe3c8ecbebe0e5f09e0490d712ce0b6d7475c194f09da2286`
wasm-examples-nft-consecutive-spec-shaking-v2 Expired	17.3 KB	`sha256:90c466a46e78a3efe3c8ecbebe0e5f09e0490d712ce0b6d7475c194f09da2286`
wasm-examples-nft-enumerable Expired	18.2 KB	`sha256:6a41b88d916ebd7241a45613b72a02e0b356a0433417fe23c1d8b6d4cde81af8`
wasm-examples-nft-enumerable-spec-shaking-v2 Expired	18.2 KB	`sha256:168c70822a1331518527584a722d492270fa3eef0b27c63d82cbc671715510a2`
wasm-examples-nft-royalties Expired	23.4 KB	`sha256:1ec174399ea8d08ffe5e1f091d0a9a6d27c91234c8799cec46b951b67fe92c7d`
wasm-examples-nft-royalties-spec-shaking-v2 Expired	23.4 KB	`sha256:7c0db4481756e604b7a00ab6e71c2010f92c67976661cd6d2018b471d4ebc516`
wasm-examples-nft-sequential-minting Expired	17.2 KB	`sha256:ddf8339c2d4725971cd3db08ab7c6207af6dbcd8e0216e8c388d9d3260d47ec9`
wasm-examples-nft-sequential-minting-spec-shaking-v2 Expired	17.2 KB	`sha256:1312c68ca5afcee93ce6cc57522b911a5469dedbf7d9c41e18c1a155051d6d11`
wasm-examples-ownable Expired	3.32 KB	`sha256:2be31c26d8ff2102ad168cb1d1d3f76a16eacef5f871232a84c4c69bd0c5ee82`
wasm-examples-ownable-spec-shaking-v2 Expired	3.32 KB	`sha256:35359fddc84de48350ebfc1b7ce534e6d0d76f3c893fbb0fb4f20dfa531e38ab`
wasm-examples-pausable Expired	2.2 KB	`sha256:ab43ae2a428f3c05573c80c49c06a55b4fd7076209a5e7060f7049314745555a`
wasm-examples-pausable-spec-shaking-v2 Expired	2.2 KB	`sha256:e2d03e1fd54b9dcd68272682d8d4148fc9ab5bcb91132c985ac5307ec343c7c4`
wasm-examples-rwa-claim-issuer Expired	18.4 KB	`sha256:9dc59598475b68463d6e654648d80dbd424cc9a098e294ee17a9e1394b0892f6`
wasm-examples-rwa-claim-issuer-spec-shaking-v2 Expired	18.4 KB	`sha256:a5698e7f6c48e4ab5428e0b1e8b9412c59e5af6746f273adb5ed09905515245e`
wasm-examples-rwa-claim-topics-and-issuers Expired	20.5 KB	`sha256:53414a4aa543ace93c95496519aca5300466ce4ee67a39547843705d13908a37`
wasm-examples-rwa-claim-topics-and-issuers-spec-shaking-v2 Expired	20.5 KB	`sha256:ec557dd377aa2fe0ea334f8ee65af370ca6ac439611fbbe6614aa990bf8635c4`
wasm-examples-rwa-compliance Expired	21.6 KB	`sha256:55435259154c0afd3ee42cb05a8ed60d50ca4cf963321f96b8407e71df0e116c`
wasm-examples-rwa-compliance-spec-shaking-v2 Expired	21.6 KB	`sha256:55435259154c0afd3ee42cb05a8ed60d50ca4cf963321f96b8407e71df0e116c`
wasm-examples-rwa-identity Expired	17.2 KB	`sha256:5f8152f05f8a817fbd5bd18be820931675cb0e0b75ee7248b1714def8cfb49e9`
wasm-examples-rwa-identity-registry Expired	19.8 KB	`sha256:0efb94c73433c928d2b78ab1f534914ed5e62728555ca8d9203a987223dc52a7`
wasm-examples-rwa-identity-registry-spec-shaking-v2 Expired	19.8 KB	`sha256:cce8006ae80a01a1439b429e9584a8144ac8df0c4b32641bec7af5ff0a1646ef`
wasm-examples-rwa-identity-spec-shaking-v2 Expired	17.2 KB	`sha256:df4e0f2fc39aa3bc73bd9cd84171951b896ae1821947e17b29f3fc6c1a1cee23`
wasm-examples-rwa-identity-verifier Expired	19.4 KB	`sha256:b42ec5995d243901956c57750377a4c3e1ad0b2bd0c201ae7d20aaceec9e33da`
wasm-examples-rwa-identity-verifier-spec-shaking-v2 Expired	19.4 KB	`sha256:b42ec5995d243901956c57750377a4c3e1ad0b2bd0c201ae7d20aaceec9e33da`
wasm-examples-rwa-token Expired	23.3 KB	`sha256:479643141dfa9c381cecccd2974e30873afbe97464927d71dff2339910e70ab1`
wasm-examples-rwa-token-spec-shaking-v2 Expired	23.3 KB	`sha256:3236680b526a0396385e4599052e8dd71c930ec4ca4b6f91260d92a1511eb000`
wasm-examples-sac-admin-generic Expired	15.6 KB	`sha256:23a8087bdcfbc271538d0a7aab825599c3462a0f8148713d880d5245f07bdc90`
wasm-examples-sac-admin-generic-spec-shaking-v2 Expired	15.6 KB	`sha256:d94b42cd4230f7bcf787d482dea0de8733a2c18bfcbeab0feada634797223a74`
wasm-examples-sac-admin-wrapper Expired	18.8 KB	`sha256:9b2e7c2bbaed42859c61e7587ced5164b0f3d1f25f790ebf48f521bbc8ff1aca`
wasm-examples-sac-admin-wrapper-spec-shaking-v2 Expired	18.8 KB	`sha256:e40381384de8c073c368943295ea9ae52003098268fa87af9efc7bc4c42e68ca`
wasm-examples-timelock-controller Expired	14 KB	`sha256:03665e924e3e1c2da82281212a1d5bd33f6576e18f2a13032a1770a13c28191f`
wasm-examples-timelock-controller-spec-shaking-v2 Expired	14 KB	`sha256:56e3db819e6a9f6e2601090d3354994ee7a85c3f8eaf2938aa817a9652774163`
wasm-examples-upgradeable-lazy-v1 Expired	7.12 KB	`sha256:9122c1e5208280a645a65a0d82b412bfa21d621d08862903d7d5ef897d5e5cf1`
wasm-examples-upgradeable-lazy-v1-spec-shaking-v2 Expired	7.12 KB	`sha256:3662095d4a0afca674d0f2886b016fb05eb5fa54318ef9e511a63f0f736a1ca2`
wasm-examples-upgradeable-lazy-v2 Expired	7.44 KB	`sha256:494187989510651ead82391b18fe7655bb58433175ec18cb226f69039ef3b7ea`
wasm-examples-upgradeable-lazy-v2-spec-shaking-v2 Expired	7.44 KB	`sha256:54892981212683ff7ce012add70396baf9cd841f43077642aa3f598987db026b`
wasm-examples-upgradeable-upgrader Expired	2.69 KB	`sha256:f27e242bbdca8b85d28bbfe0ca5c1fe9b937735f94d6bc05873dff9ed06c7129`
wasm-examples-upgradeable-upgrader-spec-shaking-v2 Expired	2.69 KB	`sha256:39d03d82b6bd5a092ed2a9831cbf843c72c53f8ece7fd529d060b730666866c8`
wasm-examples-upgradeable-v1 Expired	7.05 KB	`sha256:50f6e98eea8c4b6066ec660840ef4ea1567f2d31027bfcd7f83ea45140a37449`
wasm-examples-upgradeable-v1-spec-shaking-v2 Expired	7.05 KB	`sha256:0d22eee278ead15e327151f1536fdf48e23383813c48ec004556aa79122bac98`
wasm-examples-upgradeable-v2 Expired	7.42 KB	`sha256:117bed273cd4ec796dd7409990c98c7959a189ea4b9e00362b4e1ca984f66ffb`
wasm-examples-upgradeable-v2-spec-shaking-v2 Expired	7.42 KB	`sha256:c68bd9c9ea13ec6cf39dfd9f6fec339df2ef4d20a99f4dc527c5de64f57a8701`
wasm-packages-access Expired	1.29 KB	`sha256:98e114797d3c1463c76a7f7498e4b22361fd46f8cee9cef17c5bf8c95317deea`
wasm-packages-access-spec-shaking-v2 Expired	1.29 KB	`sha256:197bd8d47b5ec44ca752aef49f6e449197c7b94c0b65fd527f350e97e48e99e3`
wasm-packages-accounts Expired	4.87 KB	`sha256:8beec2ff1a250d89baba5d218604b0f3c0f0b95f2238610e04b2203f788ba2ca`
wasm-packages-accounts-spec-shaking-v2 Expired	4.87 KB	`sha256:1b2e74b7b83280ac2aa653ae80078010bc622b3f50935168503a3d84865a85ba`
wasm-packages-contract-utils Expired	1.12 KB	`sha256:14796272efb42ff7aa7a00c57ab25a96e01f460beedf7beed5aab28b86735d01`
wasm-packages-contract-utils-spec-shaking-v2 Expired	1.12 KB	`sha256:6fdf72058c8f31840cd6e3af634f9edff18b37b3450e207cf16125c9006fb05a`
wasm-packages-fee-abstraction Expired	1.14 KB	`sha256:9a7ff4f2508dc2913f3e71eebe9937eaf5d02806c7e1a880f756f31755a960ce`
wasm-packages-fee-abstraction-spec-shaking-v2 Expired	1.14 KB	`sha256:97ea83b735010d4d11087cc8c420bee7809722f1a405f012e1fbfdf987b59a2b`
wasm-packages-governance Expired	4.23 KB	`sha256:b40ea91d6a339ea3dfd45134c6bc94757ab363f9f47ae1d520378c86f10bedda`
wasm-packages-governance-spec-shaking-v2 Expired	4.23 KB	`sha256:f78f45703614a068e01039a38cb6db7ca6097f873508375b0589b57a0fded0a5`
wasm-packages-tokens Expired	12.6 KB	`sha256:2fd61618a1c26ec46245da4b9b51038bbe484620c76ac4e213f3a2b2b7eb8e16`
wasm-packages-tokens-spec-shaking-v2 Expired	12.6 KB	`sha256:3ffcd1fff028a6153d7cfc38bc3f5a20cbe14d2b554d0f6b271e0311edd55564`
wasm-packages-zk-email Expired	803 Bytes	`sha256:69b77d928f34264101928c14da96674dff4510dd2cc4d87eff9781bfe271d7a0`
wasm-packages-zk-email-spec-shaking-v2 Expired	803 Bytes	`sha256:f33b82213b13a244837b84110be31d2b97b82f37c7abfd894ddb3ec366bf193f`

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add compiler error when reserved type names are used as contract types #814

Summary