feat: add ChipIngress batch emitter support #25993
docker-build.yml
on: pull_request
init
45s
Matrix: docker-ccip-plugins / build-publish
Matrix: docker-ccip / build-publish
Matrix: docker-core-plugins-testing / build-publish
Matrix: docker-core-plugins / build-publish
Matrix: docker-core / build-publish
docker-ccip-plugins
/
docker-manifest
22s
deploy-nightly-ccip
0s
call-cre-workflow-don-benchmark
/
workflow-don-benchmark
soak-cre-memory-leak
/
CRE PoR Memory Leak Soak
deploy-nightly-core
0s
call-cre-local-env-tests
/
Notify about local env startup failure
Annotations
26 warnings
|
init
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker-core-plugins-testing / init
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker-core-plugins / init
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker-ccip / init
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker-core / init
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker-ccip-plugins / init
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker-core-plugins / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/metadata-action@369eb591f429131d6889c46b94e711f089e6ca96, docker/setup-buildx-action@f7ce87c1d6bead3e36075b2ce75da1f6cc28aaca, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
|
|
docker-ccip-plugins / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/metadata-action@369eb591f429131d6889c46b94e711f089e6ca96, docker/setup-buildx-action@f7ce87c1d6bead3e36075b2ce75da1f6cc28aaca, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
|
|
docker-core / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/metadata-action@369eb591f429131d6889c46b94e711f089e6ca96, docker/setup-buildx-action@f7ce87c1d6bead3e36075b2ce75da1f6cc28aaca, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
|
|
docker-ccip / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/metadata-action@369eb591f429131d6889c46b94e711f089e6ca96, docker/setup-buildx-action@f7ce87c1d6bead3e36075b2ce75da1f6cc28aaca, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
|
|
docker-core-plugins-testing / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/metadata-action@369eb591f429131d6889c46b94e711f089e6ca96, docker/setup-buildx-action@f7ce87c1d6bead3e36075b2ce75da1f6cc28aaca, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
|
|
docker-core-plugins / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/metadata-action@369eb591f429131d6889c46b94e711f089e6ca96, docker/setup-buildx-action@f7ce87c1d6bead3e36075b2ce75da1f6cc28aaca, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
|
|
docker-ccip / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/metadata-action@369eb591f429131d6889c46b94e711f089e6ca96, docker/setup-buildx-action@f7ce87c1d6bead3e36075b2ce75da1f6cc28aaca, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
|
|
docker-core / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/metadata-action@369eb591f429131d6889c46b94e711f089e6ca96, docker/setup-buildx-action@f7ce87c1d6bead3e36075b2ce75da1f6cc28aaca, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
|
|
docker-ccip-plugins / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/metadata-action@369eb591f429131d6889c46b94e711f089e6ca96, docker/setup-buildx-action@f7ce87c1d6bead3e36075b2ce75da1f6cc28aaca, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
|
|
docker-core-plugins-testing / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502, docker/metadata-action@369eb591f429131d6889c46b94e711f089e6ca96, docker/setup-buildx-action@f7ce87c1d6bead3e36075b2ce75da1f6cc28aaca, smartcontractkit/chainlink-github-actions/github-app-token-issuer@main. 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/
|
|
docker-core-plugins / docker-manifest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
|
|
docker-core-plugins / docker-manifest
Skip output 'name' since it may contain secret.
|
|
docker-ccip / docker-manifest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
|
|
docker-ccip / docker-manifest
Skip output 'name' since it may contain secret.
|
|
docker-core-plugins-testing / docker-manifest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
|
|
docker-core-plugins-testing / docker-manifest
Skip output 'name' since it may contain secret.
|
|
docker-core / docker-manifest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
|
|
docker-core / docker-manifest
Skip output 'name' since it may contain secret.
|
|
docker-ccip-plugins / docker-manifest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
|
|
docker-ccip-plugins / docker-manifest
Skip output 'name' since it may contain secret.
|