chore(kms-connector): remove check decryption already done (#2030) #252
mergify[bot]kms-connector-docker-build.yml
on: push
is-latest-commit
/
check
4s
Matrix: build-db-migration / build-and-push-docker
Waiting for pending jobs
Matrix: build-gw-listener / build-and-push-docker
Waiting for pending jobs
Matrix: build-kms-worker / build-and-push-docker
Matrix: build-tx-sender / build-and-push-docker
Waiting for pending jobs
Matrix: build-db-migration / create-manifest
Waiting for pending jobs
Matrix: build-gw-listener / create-manifest
Waiting for pending jobs
Matrix: build-kms-worker / create-manifest
Matrix: build-tx-sender / create-manifest
Waiting for pending jobs
Annotations
21 warnings
|
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, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/setup-docker-action@efe9e3891a4f7307e689f2100b33a155b900a608, 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/
|
|
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, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/setup-docker-action@efe9e3891a4f7307e689f2100b33a155b900a608, 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/
|
|
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, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/setup-docker-action@efe9e3891a4f7307e689f2100b33a155b900a608, 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/
|
|
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, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567, docker/setup-docker-action@efe9e3891a4f7307e689f2100b33a155b900a608, 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/
|
|
re-tag-db-migration-image / prepare-image-tags
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/
|
|
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. 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/
|
|
re-tag-tx-sender-image / prepare-image-tags
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/
|
|
re-tag-gw-listener-image / prepare-image-tags
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/
|
|
re-tag-tx-sender-image / re-tag-image
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, 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/
|
|
re-tag-gw-listener-image / re-tag-image
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, 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/
|
|
re-tag-db-migration-image / re-tag-image
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, 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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/
|
|
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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
zama-ai~fhevm~0UCI83.dockerbuild
|
51.7 KB |
sha256:e2edb183484c5a6266ec2baa7c9b842152f6a12acb8e4ebef80f69ef90bb43d9
|
|
|
zama-ai~fhevm~24KSBO.dockerbuild
|
53.5 KB |
sha256:9b7ccf11ea8e8d4931445ba5e131f362423ec8589cd449e93db8cc6f36a26790
|
|
|
zama-ai~fhevm~FF6T4J.dockerbuild
|
51.2 KB |
sha256:27bf2a372d362489183b06ade898510ec8ac2f8310eac3872ffff58f51c8937f
|
|
|
zama-ai~fhevm~IOZGUN.dockerbuild
|
54.6 KB |
sha256:d70683213bceacf7f9166787dd2ac801013328ac225f87901fd5c2b591d3f65d
|
|