merge queue: embarking main (884690e), #2184, #2180, #2182, #2156 and #2154 together #2701
test-suite-orchestrate-e2e-tests.yml
on: pull_request
coprocessor-docker-build
/
...
/
check
kms-connector-docker-build
/
...
/
check
gateway-contracts-docker-build
/
...
/
determine-tag
7s
gateway-contracts-docker-build
/
...
/
prepare-image-tags
host-contracts-docker-build
/
...
/
determine-tag
7s
host-contracts-docker-build
/
...
/
prepare-image-tags
test-suite-docker-build
/
...
/
prepare-image-tags
Matrix: gateway-contracts-docker-build / build / build-and-push-docker
Matrix: host-contracts-docker-build / build / build-and-push-docker
Matrix: test-suite-docker-build / build / build-and-push-docker
coprocessor-docker-build
/
...
/
determine-tag
coprocessor-docker-build
/
...
/
determine-tag
coprocessor-docker-build
/
...
/
determine-tag
coprocessor-docker-build
/
...
/
determine-tag
coprocessor-docker-build
/
...
/
determine-tag
coprocessor-docker-build
/
...
/
determine-tag
coprocessor-docker-build
/
...
/
determine-tag
coprocessor-docker-build
/
...
/
prepare-image-tags
coprocessor-docker-build
/
...
/
prepare-image-tags
coprocessor-docker-build
/
...
/
prepare-image-tags
coprocessor-docker-build
/
...
/
prepare-image-tags
coprocessor-docker-build
/
...
/
prepare-image-tags
coprocessor-docker-build
/
...
/
prepare-image-tags
coprocessor-docker-build
/
...
/
prepare-image-tags
kms-connector-docker-build
/
...
/
determine-tag
kms-connector-docker-build
/
...
/
determine-tag
kms-connector-docker-build
/
...
/
determine-tag
kms-connector-docker-build
/
...
/
determine-tag
kms-connector-docker-build
/
...
/
prepare-image-tags
kms-connector-docker-build
/
...
/
prepare-image-tags
kms-connector-docker-build
/
...
/
prepare-image-tags
kms-connector-docker-build
/
...
/
prepare-image-tags
Matrix: gateway-contracts-docker-build / build / create-manifest
Matrix: host-contracts-docker-build / build / create-manifest
Matrix: test-suite-docker-build / build / create-manifest
Matrix: coprocessor-docker-build / build-db-migration / build-and-push-docker
Waiting for pending jobs
Matrix: coprocessor-docker-build / build-gw-listener / build-and-push-docker
Waiting for pending jobs
Matrix: coprocessor-docker-build / build-host-listener / build-and-push-docker
Waiting for pending jobs
Matrix: coprocessor-docker-build / build-sns-worker / build-and-push-docker
Waiting for pending jobs
Matrix: coprocessor-docker-build / build-tfhe-worker / build-and-push-docker
Waiting for pending jobs
Matrix: coprocessor-docker-build / build-tx-sender / build-and-push-docker
Waiting for pending jobs
Matrix: coprocessor-docker-build / build-zkproof-worker / build-and-push-docker
Waiting for pending jobs
Matrix: kms-connector-docker-build / build-db-migration / build-and-push-docker
Waiting for pending jobs
Matrix: kms-connector-docker-build / build-gw-listener / build-and-push-docker
Waiting for pending jobs
Matrix: kms-connector-docker-build / build-kms-worker / build-and-push-docker
Waiting for pending jobs
Matrix: kms-connector-docker-build / build-tx-sender / build-and-push-docker
Waiting for pending jobs
Matrix: coprocessor-docker-build / build-db-migration / create-manifest
Waiting for pending jobs
Matrix: coprocessor-docker-build / build-gw-listener / create-manifest
Waiting for pending jobs
Matrix: coprocessor-docker-build / build-host-listener / create-manifest
Waiting for pending jobs
Matrix: coprocessor-docker-build / build-sns-worker / create-manifest
Waiting for pending jobs
Matrix: coprocessor-docker-build / build-tfhe-worker / create-manifest
Waiting for pending jobs
Matrix: coprocessor-docker-build / build-tx-sender / create-manifest
Waiting for pending jobs
Matrix: coprocessor-docker-build / build-zkproof-worker / create-manifest
Waiting for pending jobs
Matrix: kms-connector-docker-build / build-db-migration / create-manifest
Waiting for pending jobs
Matrix: kms-connector-docker-build / build-gw-listener / create-manifest
Waiting for pending jobs
Matrix: kms-connector-docker-build / build-kms-worker / create-manifest
Waiting for pending jobs
Matrix: kms-connector-docker-build / build-tx-sender / create-manifest
Waiting for pending jobs
run-e2e-tests
/
fhevm-e2e-test
5m 7s
Annotations
2 errors and 37 warnings
|
run-e2e-tests / fhevm-e2e-test
Process completed with exit code 1.
|
|
run-e2e-tests / fhevm-e2e-test
Process completed with exit code 1.
|
|
coprocessor-docker-build / check-changes-zkproof-worker / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
coprocessor-docker-build / check-changes-db-migration / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
coprocessor-docker-build / check-changes-sns-worker / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
kms-connector-docker-build / check-changes-kms-worker / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
coprocessor-docker-build / check-changes-tx-sender / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
gateway-contracts-docker-build / check-changes / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
kms-connector-docker-build / check-changes-tx-sender / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
kms-connector-docker-build / check-changes-gw-listener / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
coprocessor-docker-build / check-changes-tfhe-worker / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
host-contracts-docker-build / check-changes / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
coprocessor-docker-build / check-changes-gw-listener / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
kms-connector-docker-build / check-changes-db-migration / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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-suite-docker-build / check-changes / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
coprocessor-docker-build / check-changes-host-listener / check-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
gateway-contracts-docker-build / build / determine-tag
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683. 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/
|
|
host-contracts-docker-build / build / determine-tag
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683. 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-suite-docker-build / build / determine-tag
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683. 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/
|
|
gateway-contracts-docker-build / build / build-and-push-docker (linux/amd64, ubuntu-latest, amd64, dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/build-push-action@5cd11c3a4ced054e52742c5fd54dca954e0edd85, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804, docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb. 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/
|
|
host-contracts-docker-build / build / build-and-push-docker (linux/amd64, ubuntu-latest, amd64, prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/build-push-action@5cd11c3a4ced054e52742c5fd54dca954e0edd85, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804, docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb. 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-suite-docker-build / build / build-and-push-docker (linux/amd64, ubuntu-latest, amd64, dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/build-push-action@5cd11c3a4ced054e52742c5fd54dca954e0edd85, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804, docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb. 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-suite-docker-build / build / build-and-push-docker (linux/amd64, ubuntu-latest, amd64, prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/build-push-action@5cd11c3a4ced054e52742c5fd54dca954e0edd85, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804, docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb. 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/
|
|
gateway-contracts-docker-build / build / build-and-push-docker (linux/amd64, ubuntu-latest, amd64, prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/build-push-action@5cd11c3a4ced054e52742c5fd54dca954e0edd85, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804, docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb. 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/
|
|
host-contracts-docker-build / build / build-and-push-docker (linux/amd64, ubuntu-latest, amd64, dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/build-push-action@5cd11c3a4ced054e52742c5fd54dca954e0edd85, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804, docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb. 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/
|
|
gateway-contracts-docker-build / build / build-and-push-docker (linux/arm64, large_ubuntu_16_arm, arm64, prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/build-push-action@5cd11c3a4ced054e52742c5fd54dca954e0edd85, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804, docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb. 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/
|
|
gateway-contracts-docker-build / build / build-and-push-docker (linux/arm64, large_ubuntu_16_arm, arm64, dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/build-push-action@5cd11c3a4ced054e52742c5fd54dca954e0edd85, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804, docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb. 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-suite-docker-build / build / build-and-push-docker (linux/arm64, large_ubuntu_16_arm, arm64, dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/build-push-action@5cd11c3a4ced054e52742c5fd54dca954e0edd85, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804, docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb. 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/
|
|
host-contracts-docker-build / build / build-and-push-docker (linux/arm64, large_ubuntu_16_arm, arm64, prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/build-push-action@5cd11c3a4ced054e52742c5fd54dca954e0edd85, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804, docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb. 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/
|
|
host-contracts-docker-build / build / build-and-push-docker (linux/arm64, large_ubuntu_16_arm, arm64, dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/build-push-action@5cd11c3a4ced054e52742c5fd54dca954e0edd85, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804, docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb. 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-suite-docker-build / build / build-and-push-docker (linux/arm64, large_ubuntu_16_arm, arm64, prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/build-push-action@5cd11c3a4ced054e52742c5fd54dca954e0edd85, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804, docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb. 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/
|
|
gateway-contracts-docker-build / build / create-manifest (dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567. 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/
|
|
gateway-contracts-docker-build / build / create-manifest (prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567. 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/
|
|
host-contracts-docker-build / build / create-manifest (dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567. 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/
|
|
host-contracts-docker-build / build / create-manifest (prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567. 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-suite-docker-build / build / create-manifest (dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567. 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-suite-docker-build / build / create-manifest (prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567. 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/
|
|
create-e2e-tests-input
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683. 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/
|
|
run-e2e-tests / fhevm-e2e-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/setup-buildx-action@d70bba72b1f3fd22344832f00baa16ece964efeb, foundry-rs/foundry-toolchain@82dee4ba654bd2146511f85f0d013af94670c4de. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
zama-ai~fhevm~4BWX64.dockerbuild
|
19.2 KB |
sha256:705c348283dd7e60d6a5f6ebde92121cdd17b8c4cbccb8cb636d872b7b8b9dce
|
|
|
zama-ai~fhevm~4UJJII.dockerbuild
|
19.3 KB |
sha256:241127d698b2a90047a5d5e723ca44ab510484c7238283eeea54d70be6ac7730
|
|
|
zama-ai~fhevm~8W3K33.dockerbuild
|
19.1 KB |
sha256:9fb10fd531f65c9a7828c47327c9df3cde8eeab3bc3d1185b297c137f6594033
|
|
|
zama-ai~fhevm~BL0FEQ.dockerbuild
|
18.4 KB |
sha256:cfe218da98729a3e0ead84e962b85ac6e98fd4a4cbb360cef8fc125fb40f3d8f
|
|
|
zama-ai~fhevm~JXZC52.dockerbuild
|
20.5 KB |
sha256:fb6a1675279ed0ebd6ea3a95da0352249432a04a1e2fbf4e614ebaff064a951b
|
|
|
zama-ai~fhevm~LM4S2X.dockerbuild
|
18.6 KB |
sha256:f06a591fdf1160c9053537010bd6bbe82787e2860c545c996d9839e5d0e91148
|
|
|
zama-ai~fhevm~MPY72D.dockerbuild
|
20.3 KB |
sha256:6dec06bad4eb890a94ef647fc437b382df90e251c3221effa5b3deb6e70e9fbf
|
|
|
zama-ai~fhevm~NSFSQ2.dockerbuild
|
19.7 KB |
sha256:2ff577d858ad93370bb01f4fda2f22ae70fd22879bb248b6437f5bd267d204ff
|
|
|
zama-ai~fhevm~ONVQW2.dockerbuild
|
18.1 KB |
sha256:1cd28bf374de966de21a3a330d24fa56bac80b0e91962c56cc0be7a3655ea1ad
|
|
|
zama-ai~fhevm~RFWYEK.dockerbuild
|
20.2 KB |
sha256:c853b4bd893b0ff410e452b1e18281f026d84998ec5314a3d518dc9d09783948
|
|
|
zama-ai~fhevm~UA399F.dockerbuild
|
20 KB |
sha256:b3dcc0ca61ac3274837e5248038de7a63df2257d20757e1246ce23f831670b11
|
|
|
zama-ai~fhevm~XCG1TL.dockerbuild
|
18.4 KB |
sha256:007d8c6f460da902d71c953582615a683ab20ef979c312468930dcf96e5c7e42
|
|