Skip to content

merge queue: embarking main (6e65afc) and [#2154 + #2166] together #2702

merge queue: embarking main (6e65afc) and [#2154 + #2166] together

merge queue: embarking main (6e65afc) and [#2154 + #2166] together #2702

Triggered via pull request March 26, 2026 16:39
Status Success
Total duration 41m 10s
Artifacts 24
coprocessor-docker-build  /  ...  /  check-changes
15s
coprocessor-docker-build / check-changes-db-migration / check-changes
coprocessor-docker-build  /  ...  /  check-changes
10s
coprocessor-docker-build / check-changes-gw-listener / check-changes
coprocessor-docker-build  /  ...  /  check-changes
11s
coprocessor-docker-build / check-changes-host-listener / check-changes
coprocessor-docker-build  /  ...  /  check-changes
9s
coprocessor-docker-build / check-changes-sns-worker / check-changes
coprocessor-docker-build  /  ...  /  check-changes
15s
coprocessor-docker-build / check-changes-tfhe-worker / check-changes
coprocessor-docker-build  /  ...  /  check-changes
10s
coprocessor-docker-build / check-changes-tx-sender / check-changes
coprocessor-docker-build  /  ...  /  check-changes
9s
coprocessor-docker-build / check-changes-zkproof-worker / check-changes
gateway-contracts-docker-build  /  ...  /  check-changes
10s
gateway-contracts-docker-build / check-changes / check-changes
gateway-contracts-docker-build  /  ...  /  check
gateway-contracts-docker-build / is-latest-commit / check
host-contracts-docker-build  /  ...  /  check-changes
13s
host-contracts-docker-build / check-changes / check-changes
host-contracts-docker-build  /  ...  /  check
host-contracts-docker-build / is-latest-commit / check
kms-connector-docker-build  /  ...  /  check-changes
12s
kms-connector-docker-build / check-changes-db-migration / check-changes
kms-connector-docker-build  /  ...  /  check-changes
14s
kms-connector-docker-build / check-changes-gw-listener / check-changes
kms-connector-docker-build  /  ...  /  check-changes
10s
kms-connector-docker-build / check-changes-kms-worker / check-changes
kms-connector-docker-build  /  ...  /  check-changes
8s
kms-connector-docker-build / check-changes-tx-sender / check-changes
test-suite-docker-build  /  ...  /  check-changes
10s
test-suite-docker-build / check-changes / check-changes
test-suite-docker-build  /  ...  /  check
test-suite-docker-build / is-latest-commit / check
coprocessor-docker-build  /  ...  /  check
coprocessor-docker-build / is-latest-commit / check
kms-connector-docker-build  /  ...  /  check
kms-connector-docker-build / is-latest-commit / check
gateway-contracts-docker-build  /  ...  /  determine-tag
4s
gateway-contracts-docker-build / build / determine-tag
gateway-contracts-docker-build  /  ...  /  prepare-image-tags
gateway-contracts-docker-build / re-tag-image / prepare-image-tags
host-contracts-docker-build  /  ...  /  determine-tag
6s
host-contracts-docker-build / build / determine-tag
host-contracts-docker-build  /  ...  /  prepare-image-tags
host-contracts-docker-build / re-tag-image / prepare-image-tags
test-suite-docker-build  /  ...  /  determine-tag
5s
test-suite-docker-build / build / determine-tag
test-suite-docker-build  /  ...  /  prepare-image-tags
test-suite-docker-build / re-tag-image / prepare-image-tags
coprocessor-docker-build  /  build-decisions
4s
coprocessor-docker-build / build-decisions
kms-connector-docker-build  /  build-decisions
2s
kms-connector-docker-build / build-decisions
Matrix: gateway-contracts-docker-build / build / build-and-push-docker
gateway-contracts-docker-build  /  ...  /  re-tag-image
gateway-contracts-docker-build / re-tag-image / re-tag-image
Matrix: host-contracts-docker-build / build / build-and-push-docker
host-contracts-docker-build  /  ...  /  re-tag-image
host-contracts-docker-build / re-tag-image / re-tag-image
Matrix: test-suite-docker-build / build / build-and-push-docker
test-suite-docker-build  /  ...  /  re-tag-image
test-suite-docker-build / re-tag-image / re-tag-image
coprocessor-docker-build  /  ...  /  determine-tag
coprocessor-docker-build / build-db-migration / determine-tag
coprocessor-docker-build  /  ...  /  determine-tag
coprocessor-docker-build / build-gw-listener / determine-tag
coprocessor-docker-build  /  ...  /  determine-tag
coprocessor-docker-build / build-host-listener / determine-tag
coprocessor-docker-build  /  ...  /  determine-tag
coprocessor-docker-build / build-sns-worker / determine-tag
coprocessor-docker-build  /  ...  /  determine-tag
coprocessor-docker-build / build-tfhe-worker / determine-tag
coprocessor-docker-build  /  ...  /  determine-tag
coprocessor-docker-build / build-tx-sender / determine-tag
coprocessor-docker-build  /  ...  /  determine-tag
coprocessor-docker-build / build-zkproof-worker / determine-tag
coprocessor-docker-build  /  ...  /  prepare-image-tags
coprocessor-docker-build / re-tag-db-migration-image / prepare-image-tags
coprocessor-docker-build  /  ...  /  prepare-image-tags
coprocessor-docker-build / re-tag-gw-listener-image / prepare-image-tags
coprocessor-docker-build  /  ...  /  prepare-image-tags
coprocessor-docker-build / re-tag-host-listener-image / prepare-image-tags
coprocessor-docker-build  /  ...  /  prepare-image-tags
coprocessor-docker-build / re-tag-sns-worker-image / prepare-image-tags
coprocessor-docker-build  /  ...  /  prepare-image-tags
coprocessor-docker-build / re-tag-tfhe-worker-image / prepare-image-tags
coprocessor-docker-build  /  ...  /  prepare-image-tags
coprocessor-docker-build / re-tag-tx-sender-image / prepare-image-tags
coprocessor-docker-build  /  ...  /  prepare-image-tags
coprocessor-docker-build / re-tag-zkproof-worker-image / prepare-image-tags
kms-connector-docker-build  /  ...  /  determine-tag
kms-connector-docker-build / build-db-migration / determine-tag
kms-connector-docker-build  /  ...  /  determine-tag
5s
kms-connector-docker-build / build-gw-listener / determine-tag
kms-connector-docker-build  /  ...  /  determine-tag
5s
kms-connector-docker-build / build-kms-worker / determine-tag
kms-connector-docker-build  /  ...  /  determine-tag
5s
kms-connector-docker-build / build-tx-sender / determine-tag
kms-connector-docker-build  /  ...  /  prepare-image-tags
kms-connector-docker-build / re-tag-db-migration-image / prepare-image-tags
kms-connector-docker-build  /  ...  /  prepare-image-tags
kms-connector-docker-build / re-tag-gw-listener-image / prepare-image-tags
kms-connector-docker-build  /  ...  /  prepare-image-tags
kms-connector-docker-build / re-tag-kms-worker-image / prepare-image-tags
kms-connector-docker-build  /  ...  /  prepare-image-tags
kms-connector-docker-build / re-tag-tx-sender-image / 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
coprocessor-docker-build  /  ...  /  re-tag-image
coprocessor-docker-build / re-tag-db-migration-image / re-tag-image
coprocessor-docker-build  /  ...  /  re-tag-image
coprocessor-docker-build / re-tag-gw-listener-image / re-tag-image
coprocessor-docker-build  /  ...  /  re-tag-image
coprocessor-docker-build / re-tag-host-listener-image / re-tag-image
coprocessor-docker-build  /  ...  /  re-tag-image
coprocessor-docker-build / re-tag-sns-worker-image / re-tag-image
coprocessor-docker-build  /  ...  /  re-tag-image
coprocessor-docker-build / re-tag-tfhe-worker-image / re-tag-image
coprocessor-docker-build  /  ...  /  re-tag-image
coprocessor-docker-build / re-tag-tx-sender-image / re-tag-image
coprocessor-docker-build  /  ...  /  re-tag-image
coprocessor-docker-build / re-tag-zkproof-worker-image / re-tag-image
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
Matrix: kms-connector-docker-build / build-kms-worker / build-and-push-docker
Matrix: kms-connector-docker-build / build-tx-sender / build-and-push-docker
kms-connector-docker-build  /  ...  /  re-tag-image
kms-connector-docker-build / re-tag-db-migration-image / re-tag-image
kms-connector-docker-build  /  ...  /  re-tag-image
kms-connector-docker-build / re-tag-gw-listener-image / re-tag-image
kms-connector-docker-build  /  ...  /  re-tag-image
kms-connector-docker-build / re-tag-kms-worker-image / re-tag-image
kms-connector-docker-build  /  ...  /  re-tag-image
kms-connector-docker-build / re-tag-tx-sender-image / re-tag-image
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
Matrix: kms-connector-docker-build / build-kms-worker / create-manifest
Matrix: kms-connector-docker-build / build-tx-sender / create-manifest
create-e2e-tests-input
7s
create-e2e-tests-input
run-e2e-tests  /  fhevm-e2e-test
28m 58s
run-e2e-tests / fhevm-e2e-test
Fit to window
Zoom out
Zoom in

Annotations

70 warnings
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. 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-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. 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. 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-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. 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 / 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-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. 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 / 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-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/
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. 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. 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/
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. 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. 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/
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. 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. 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 / build-kms-worker / 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/
kms-connector-docker-build / build-gw-listener / 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. 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 / build-tx-sender / 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. 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. 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/
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. 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. 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. 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. 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. 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/
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/
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 / 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. 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/
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/
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. 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/
kms-connector-docker-build / build-gw-listener / 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/
Default value for global ARG results in an empty or invalid base image name: kms-connector/crates/gw-listener/Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ghcr.io/zama-ai/fhevm/gci/rust-glibc:${RUST_IMAGE_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
kms-connector-docker-build / build-gw-listener / 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/
Default value for global ARG results in an empty or invalid base image name: kms-connector/crates/gw-listener/Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ghcr.io/zama-ai/fhevm/gci/rust-glibc:${RUST_IMAGE_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
kms-connector-docker-build / build-kms-worker / 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/
Default value for global ARG results in an empty or invalid base image name: kms-connector/crates/kms-worker/Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ghcr.io/zama-ai/fhevm/gci/rust-glibc:${RUST_IMAGE_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
kms-connector-docker-build / build-tx-sender / 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/
Default value for global ARG results in an empty or invalid base image name: kms-connector/crates/tx-sender/Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ghcr.io/zama-ai/fhevm/gci/rust-glibc:${RUST_IMAGE_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
kms-connector-docker-build / build-kms-worker / 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/
Default value for global ARG results in an empty or invalid base image name: kms-connector/crates/kms-worker/Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ghcr.io/zama-ai/fhevm/gci/rust-glibc:${RUST_IMAGE_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
kms-connector-docker-build / build-tx-sender / 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/
Default value for global ARG results in an empty or invalid base image name: kms-connector/crates/tx-sender/Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ghcr.io/zama-ai/fhevm/gci/rust-glibc:${RUST_IMAGE_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
kms-connector-docker-build / build-gw-listener / 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/
Default value for global ARG results in an empty or invalid base image name: kms-connector/crates/gw-listener/Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ghcr.io/zama-ai/fhevm/gci/rust-glibc:${RUST_IMAGE_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
kms-connector-docker-build / build-gw-listener / 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/
Default value for global ARG results in an empty or invalid base image name: kms-connector/crates/gw-listener/Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ghcr.io/zama-ai/fhevm/gci/rust-glibc:${RUST_IMAGE_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
kms-connector-docker-build / build-kms-worker / 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/
Default value for global ARG results in an empty or invalid base image name: kms-connector/crates/kms-worker/Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ghcr.io/zama-ai/fhevm/gci/rust-glibc:${RUST_IMAGE_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
kms-connector-docker-build / build-kms-worker / 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/
Default value for global ARG results in an empty or invalid base image name: kms-connector/crates/kms-worker/Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ghcr.io/zama-ai/fhevm/gci/rust-glibc:${RUST_IMAGE_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
kms-connector-docker-build / build-tx-sender / 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/
Default value for global ARG results in an empty or invalid base image name: kms-connector/crates/tx-sender/Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ghcr.io/zama-ai/fhevm/gci/rust-glibc:${RUST_IMAGE_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
kms-connector-docker-build / build-kms-worker / 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/
kms-connector-docker-build / build-gw-listener / 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/
kms-connector-docker-build / build-gw-listener / 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/
kms-connector-docker-build / build-kms-worker / 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/
kms-connector-docker-build / build-tx-sender / 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/
Default value for global ARG results in an empty or invalid base image name: kms-connector/crates/tx-sender/Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ghcr.io/zama-ai/fhevm/gci/rust-glibc:${RUST_IMAGE_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
kms-connector-docker-build / build-tx-sender / 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/
kms-connector-docker-build / build-tx-sender / 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/
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~1MHEAF.dockerbuild
22.9 KB
sha256:2e8c9963655b7d6e2327c562d48f843d6c17b2cfa5a3b36974623887bc5f9037
zama-ai~fhevm~22HA6K.dockerbuild
26.8 KB
sha256:961b57592bc948aa3884f7f670ed3d21fd6913ba408223f66f53756e72426b92
zama-ai~fhevm~7HBH72.dockerbuild
52.2 KB
sha256:cce75b2c1a9098fc1d15865620ca9427dd3e869748227d126194862280efa0d4
zama-ai~fhevm~B541WB.dockerbuild
23 KB
sha256:5fbd1230ee96b8fe8a4387cae19b80ef7bbdb7eeb7b1403d6607896da0b26ae7
zama-ai~fhevm~C220C3.dockerbuild
26.1 KB
sha256:2403165e0c5ebb07f0ccdc87ad54d19c5da84e4767be4452507cee56b3283537
zama-ai~fhevm~D0PHP6.dockerbuild
55.8 KB
sha256:d9f06012a3e66e5b3aa841b5cfe9cf53e4162c21ec85b3b1a6856247bc53cf3c
zama-ai~fhevm~DG8NOC.dockerbuild
25.7 KB
sha256:d0772705b2162e28095767306be16160b9cdb12658ef9f28e4e0c6fbcfdeb351
zama-ai~fhevm~EYTYDU.dockerbuild
53.2 KB
sha256:b08aff17b1bdefac91a46c8e94eed2fd017fedf64e8a20e38f4238e681de516f
zama-ai~fhevm~FX11J8.dockerbuild
55.2 KB
sha256:76a11749ea1793f24535dc5d3487524bdd5bc843fee3841e39dbc3dd40c1e884
zama-ai~fhevm~I54UGQ.dockerbuild
23.4 KB
sha256:87366f0935c1bfb42893c2292b108c781edfd86dca9affdffe7f30681a317143
zama-ai~fhevm~IJJZXP.dockerbuild
25.8 KB
sha256:8782bc579448aa23c45a3c71b77349b62f4e6fba5b189752a6282f87f295e3ba
zama-ai~fhevm~NBQIV6.dockerbuild
24.6 KB
sha256:3f927683ea70fbb75071281923b1d7924000e6383a63937179e57c018ec39704
zama-ai~fhevm~OT8KH8.dockerbuild
56.3 KB
sha256:5ceeaf8f86c6993fceffaa230f14fe2f6bacb458a6fc6a38116faa38be4c4f1d
zama-ai~fhevm~R1MO1S.dockerbuild
55.1 KB
sha256:f6ec14a6afc415244dbde0be835132a95717007b3377fd410eec7f4af6343ba9
zama-ai~fhevm~UM1O2C.dockerbuild
24.9 KB
sha256:0465fad84a714308ccee87ebe41b27556e65c9f8986a7d9bfcb95656499e7764
zama-ai~fhevm~VFKOB7.dockerbuild
25.1 KB
sha256:1f82efe94d1c6f239e5f2a777976dc994aef6edc09fc2d7f957c173401f8e03a
zama-ai~fhevm~W2Y2JU.dockerbuild
51.6 KB
sha256:1581f4ef65cb5b26953096fb268e6889f63e061a36c8602cb051db1510af21d2
zama-ai~fhevm~W4ZOY5.dockerbuild
51.4 KB
sha256:cef28f68047049c2f55987e74fdb4f293b3af7d6636027a96186797933c4a336
zama-ai~fhevm~XF3HHX.dockerbuild
24.1 KB
sha256:be313235c56c2c9c6a39ffbc67369b82916619bc5b0203b8c0323d49da70e981
zama-ai~fhevm~YPNZ23.dockerbuild
52.2 KB
sha256:d83510790276c045572bb3209b62c2c03130be7b3ac7f97a12eaf12107fa3e7d
zama-ai~fhevm~YX9U17.dockerbuild
25.7 KB
sha256:1ba665c7e921212874caff5d1140ac2e3aaa11bba208cee92d2a0852d2dc677c
zama-ai~fhevm~ZBCNQL.dockerbuild
55.3 KB
sha256:3a63e1fac46f17dc876b2d68cbf01afd130e7687775775432f44ea377c60ed28
zama-ai~fhevm~ZD4O9N.dockerbuild
51.6 KB
sha256:1543f74923d154b128510aed278c8f14ed24a7d32bf45a8f7cdd72695374612c
zama-ai~fhevm~ZRICI3.dockerbuild
55.2 KB
sha256:27da5bb2e11fbcc38eab42e264cbe7122d5ea434ddaf8fd79afeac847c1b89ef