ECC-2241: MTG2Switch rules extension required for IFS cycle CY50R1 #3693
ci.yml
on: pull_request
downstream-ci
/
setup
5s
downstream-ci-hpc
/
setup
10s
Matrix: downstream-ci-hpc / ecbuild
Matrix: downstream-ci-hpc / earthkit-utils
Matrix: downstream-ci-hpc / findlibs
Matrix: downstream-ci-hpc / anemoi-utils
Matrix: downstream-ci-hpc / earthkit-geo
Matrix: downstream-ci-hpc / multiurl
Matrix: downstream-ci-hpc / covjsonkit
Matrix: downstream-ci-hpc / danu
Matrix: downstream-ci-hpc / earthkit-time
Matrix: downstream-ci-hpc / hyve
Matrix: downstream-ci-hpc / plume-plugin-axe
Matrix: downstream-ci-hpc / plume-plugin-extreme-events
Matrix: downstream-ci-hpc / plume-plugin-wind-farm
Matrix: downstream-ci-hpc / qubed
Matrix: downstream-ci-hpc / skinnywms
Matrix: downstream-ci-hpc / thermofeel
Matrix: downstream-ci-hpc / troika
Matrix: downstream-ci-hpc / conflator
Matrix: downstream-ci / earthkit-utils
Matrix: downstream-ci / findlibs
Matrix: downstream-ci / anemoi-utils
Matrix: downstream-ci / earthkit-geo
Matrix: downstream-ci / multiurl
Matrix: downstream-ci / covjsonkit
Matrix: downstream-ci / danu
Matrix: downstream-ci / earthkit-time
Matrix: downstream-ci / hyve
Matrix: downstream-ci / qubed
Matrix: downstream-ci / skinnywms
Matrix: downstream-ci / thermofeel
Matrix: downstream-ci / troika
Matrix: downstream-ci / conflator
Matrix: downstream-ci / ecbuild
Matrix: downstream-ci / plume-plugin-axe
Matrix: downstream-ci / plume-plugin-extreme-events
Matrix: downstream-ci / plume-plugin-wind-farm
Matrix: downstream-ci-hpc / eckit
Matrix: downstream-ci-hpc / eccodes
Matrix: downstream-ci-hpc / ecflow
Matrix: downstream-ci-hpc / kronos
Matrix: downstream-ci-hpc / earthkit-meteo
Matrix: downstream-ci-hpc / anemoi-plugins
Matrix: downstream-ci-hpc / anemoi-models
Matrix: downstream-ci / earthkit-meteo
Matrix: downstream-ci / anemoi-plugins
Matrix: downstream-ci / anemoi-models
Matrix: downstream-ci / eckit
Matrix: downstream-ci / eccodes
Matrix: downstream-ci / ecflow
Matrix: downstream-ci / kronos
Matrix: downstream-ci-hpc / odc
Matrix: downstream-ci-hpc / fckit
Matrix: downstream-ci-hpc / ecflow-light
Matrix: downstream-ci-hpc / eccodes-python
Matrix: downstream-ci / odc
Matrix: downstream-ci / fckit
Matrix: downstream-ci / ecflow-light
Matrix: downstream-ci / eccodes-python
Matrix: downstream-ci-hpc / metkit
Matrix: downstream-ci-hpc / pyodc
Matrix: downstream-ci-hpc / atlas
Matrix: downstream-ci-hpc / infero
Matrix: downstream-ci-hpc / cfgrib
Matrix: downstream-ci-hpc / pdbufr
Matrix: downstream-ci / metkit
Matrix: downstream-ci / pyodc
Matrix: downstream-ci / atlas
Matrix: downstream-ci / infero
Matrix: downstream-ci / cfgrib
Matrix: downstream-ci / pdbufr
Matrix: downstream-ci-hpc / fdb
Matrix: downstream-ci-hpc / mir
Matrix: downstream-ci-hpc / atlas-orca
Matrix: downstream-ci-hpc / plume
Matrix: downstream-ci / fdb
Matrix: downstream-ci / mir
Matrix: downstream-ci / atlas-orca
Matrix: downstream-ci / plume
Matrix: downstream-ci-hpc / pyfdb
Matrix: downstream-ci-hpc / gribjump
Matrix: downstream-ci-hpc / earthkit-regrid
Matrix: downstream-ci-hpc / multio
Matrix: downstream-ci / pyfdb
Matrix: downstream-ci / gribjump
Matrix: downstream-ci / earthkit-regrid
Matrix: downstream-ci / multio
Matrix: downstream-ci-hpc / earthkit-data
Matrix: downstream-ci-hpc / pygribjump
Matrix: downstream-ci-hpc / pymultio
Matrix: downstream-ci / earthkit-data
Matrix: downstream-ci / pygribjump
Matrix: downstream-ci / pymultio
Matrix: downstream-ci-hpc / anemoi-transform
Matrix: downstream-ci-hpc / earthkit-transforms
Matrix: downstream-ci-hpc / earthkit-workflows
Matrix: downstream-ci-hpc / earthkit-plots
Matrix: downstream-ci-hpc / earthkit-hydro
Matrix: downstream-ci-hpc / polytope
Matrix: downstream-ci / anemoi-transform
Matrix: downstream-ci / earthkit-transforms
Matrix: downstream-ci / earthkit-workflows
Matrix: downstream-ci / earthkit-plots
Matrix: downstream-ci / earthkit-hydro
Matrix: downstream-ci / polytope
Matrix: downstream-ci-hpc / anemoi-datasets
Matrix: downstream-ci-hpc / anemoi-inference
Matrix: downstream-ci-hpc / earthkit
Matrix: downstream-ci / anemoi-datasets
Matrix: downstream-ci / anemoi-inference
Matrix: downstream-ci / earthkit
Matrix: downstream-ci-hpc / anemoi-graphs
Matrix: downstream-ci / anemoi-graphs
Matrix: downstream-ci-hpc / anemoi-training
Matrix: downstream-ci / anemoi-training
notify
7s
Annotations
124 errors and 163 warnings
|
downstream-ci-hpc / eccodes (gnu-12.2.0)
Process completed with exit code 1.
|
|
downstream-ci-hpc / eccodes (gnu-12.2.0)
Tailing output failed with code: 1
|
|
downstream-ci-hpc / eccodes (gnu-8.5.0)
Process completed with exit code 1.
|
|
downstream-ci-hpc / eccodes (gnu-8.5.0)
Tailing output failed with code: 1
|
|
downstream-ci-hpc / eccodes (intel-2021.4.0)
Process completed with exit code 1.
|
|
downstream-ci-hpc / eccodes (intel-2021.4.0)
Tailing output failed with code: 1
|
|
downstream-ci / eccodes (gnu@fedora-37)
Error building package
|
|
downstream-ci / eccodes (clang@rocky-8.6)
Error building package
|
|
downstream-ci / eccodes (gnu@rocky-8.6)
Error building package
|
|
downstream-ci-hpc / eccodes (nvidia-22.11)
Process completed with exit code 1.
|
|
downstream-ci-hpc / eccodes (nvidia-22.11)
Tailing output failed with code: 1
|
|
downstream-ci-hpc / mir (gnu-12.2.0)
==> Build of upstream package eccodes failed on platform gnu-12.2.0, exiting.
|
|
downstream-ci-hpc / metkit (gnu-8.5.0)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci-hpc / mir (intel-2021.4.0)
==> Build of upstream package eccodes failed on platform intel-2021.4.0, exiting.
|
|
downstream-ci-hpc / metkit (gnu-12.2.0)
==> Build of upstream package eccodes failed on platform gnu-12.2.0, exiting.
|
|
downstream-ci-hpc / mir (gnu-8.5.0)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci-hpc / metkit (nvidia-22.11)
==> Build of upstream package eccodes failed on platform nvidia-22.11, exiting.
|
|
downstream-ci-hpc / eccodes-python (gnu-8.5.0, 3.11)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci-hpc / metkit (intel-2021.4.0)
==> Build of upstream package eccodes failed on platform intel-2021.4.0, exiting.
|
|
downstream-ci-hpc / mir (nvidia-22.11)
==> Build of upstream package eccodes failed on platform nvidia-22.11, exiting.
|
|
downstream-ci / mir (gnu@fedora-37)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci / metkit (gnu@rocky-8.6)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci / metkit (clang@rocky-8.6)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / eccodes-python (clang@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / mir (clang@rocky-8.6)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / eccodes-python (gnu@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci / mir (gnu@rocky-8.6)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci-hpc / fdb (gnu-12.2.0)
==> Build of upstream package eccodes failed on platform gnu-12.2.0, exiting.
|
|
downstream-ci-hpc / fdb (intel-2021.4.0)
==> Build of upstream package eccodes failed on platform intel-2021.4.0, exiting.
|
|
downstream-ci-hpc / fdb (gnu-8.5.0)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci-hpc / cfgrib (gnu-8.5.0, 3.11)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci-hpc / fdb (nvidia-22.11)
==> Build of upstream package eccodes failed on platform nvidia-22.11, exiting.
|
|
downstream-ci-hpc / pdbufr (gnu-8.5.0, 3.11)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci / metkit (gnu@fedora-37)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci-hpc / multio (gnu-12.2.0, openmpi)
==> Build of upstream package eccodes failed on platform gnu-12.2.0, exiting.
|
|
downstream-ci-hpc / multio (gnu-8.5.0, intel_mpi)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci-hpc / multio (nvidia-22.11, hpcx_openmpi)
==> Build of upstream package eccodes failed on platform nvidia-22.11, exiting.
|
|
downstream-ci-hpc / pyfdb (gnu-8.5.0, 3.11)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci-hpc / multio (gnu-12.2.0, mpi_off)
==> Build of upstream package eccodes failed on platform gnu-12.2.0, exiting.
|
|
downstream-ci-hpc / gribjump (gnu-12.2.0)
==> Build of upstream package eccodes failed on platform gnu-12.2.0, exiting.
|
|
downstream-ci-hpc / multio (gnu-12.2.0, hpcx_openmpi)
==> Build of upstream package eccodes failed on platform gnu-12.2.0, exiting.
|
|
downstream-ci-hpc / multio (intel-2021.4.0, intel_mpi)
==> Build of upstream package eccodes failed on platform intel-2021.4.0, exiting.
|
|
downstream-ci-hpc / multio (gnu-12.2.0, intel_mpi)
==> Build of upstream package eccodes failed on platform gnu-12.2.0, exiting.
|
|
downstream-ci-hpc / multio (gnu-8.5.0, hpcx_openmpi)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci-hpc / gribjump (nvidia-22.11)
==> Build of upstream package eccodes failed on platform nvidia-22.11, exiting.
|
|
downstream-ci-hpc / multio (nvidia-22.11, mpi_off)
==> Build of upstream package eccodes failed on platform nvidia-22.11, exiting.
|
|
downstream-ci-hpc / gribjump (gnu-8.5.0)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci-hpc / multio (nvidia-22.11, openmpi)
==> Build of upstream package eccodes failed on platform nvidia-22.11, exiting.
|
|
downstream-ci-hpc / gribjump (intel-2021.4.0)
==> Build of upstream package eccodes failed on platform intel-2021.4.0, exiting.
|
|
downstream-ci-hpc / multio (intel-2021.4.0, hpcx_openmpi)
==> Build of upstream package eccodes failed on platform intel-2021.4.0, exiting.
|
|
downstream-ci-hpc / multio (intel-2021.4.0, openmpi)
==> Build of upstream package eccodes failed on platform intel-2021.4.0, exiting.
|
|
downstream-ci-hpc / multio (gnu-8.5.0, openmpi)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci-hpc / multio (nvidia-22.11, intel_mpi)
==> Build of upstream package eccodes failed on platform nvidia-22.11, exiting.
|
|
downstream-ci-hpc / multio (gnu-8.5.0, mpi_off)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci-hpc / multio (intel-2021.4.0, mpi_off)
==> Build of upstream package eccodes failed on platform intel-2021.4.0, exiting.
|
|
downstream-ci-hpc / pygribjump (gnu-8.5.0, 3.11)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci-hpc / earthkit-data (gnu-8.5.0, 3.11)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci / eccodes-python (gnu@fedora-37, 3.11)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci-hpc / pymultio (gnu-8.5.0, 3.11)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci / metkit (gnu@debian-11)
Error building package
|
|
downstream-ci-hpc / earthkit-plots (gnu-8.5.0, 3.11)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci-hpc / earthkit (gnu-8.5.0, 3.11)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci / metkit (gnu@ubuntu-22.04)
Error building package
|
|
downstream-ci / pdbufr (clang@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / cfgrib (gnu@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci / cfgrib (clang@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / pdbufr (gnu@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci / fdb (clang@rocky-8.6)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / fdb (gnu@rocky-8.6)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci-hpc / polytope (gnu-8.5.0, 3.11)
==> Build of upstream package eccodes failed on platform gnu-8.5.0, exiting.
|
|
downstream-ci / fdb (gnu@ubuntu-22.04)
==> Build of upstream package metkit failed on platform gnu@ubuntu-22.04, exiting.
|
|
downstream-ci / fdb (gnu@debian-11)
==> Build of upstream package metkit failed on platform gnu@debian-11, exiting.
|
|
downstream-ci / cfgrib (gnu@fedora-37, 3.11)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci / pdbufr (gnu@fedora-37, 3.11)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci / fdb (gnu@fedora-37)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci / multio (gnu@rocky-8.6)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci / gribjump (clang@rocky-8.6)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / pyfdb (gnu@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci / pyfdb (clang@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / gribjump (gnu@rocky-8.6)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci / pyfdb (gnu@debian-11, 3.11)
==> Build of upstream package metkit failed on platform gnu@debian-11, exiting.
|
|
downstream-ci / gribjump (gnu@ubuntu-22.04)
==> Build of upstream package metkit failed on platform gnu@ubuntu-22.04, exiting.
|
|
downstream-ci / multio (clang@rocky-8.6)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / multio (gnu@debian-11)
==> Build of upstream package metkit failed on platform gnu@debian-11, exiting.
|
|
downstream-ci / gribjump (gnu@debian-11)
==> Build of upstream package metkit failed on platform gnu@debian-11, exiting.
|
|
downstream-ci / pyfdb (gnu@fedora-37, 3.11)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci / pyfdb (gnu@ubuntu-22.04, 3.11)
==> Build of upstream package metkit failed on platform gnu@ubuntu-22.04, exiting.
|
|
private-downstream-ci-hpc
Process completed with exit code 1.
|
|
private-downstream-ci-hpc
Workflow FAILED!
|
|
downstream-ci / multio (gnu@fedora-37)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci / multio (gnu@ubuntu-22.04)
==> Build of upstream package metkit failed on platform gnu@ubuntu-22.04, exiting.
|
|
downstream-ci / gribjump (gnu@fedora-37)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci / earthkit-data (gnu@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci / earthkit-data (clang@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / pymultio (gnu@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci / earthkit-data (gnu@ubuntu-22.04, 3.11)
==> Build of upstream package metkit failed on platform gnu@ubuntu-22.04, exiting.
|
|
downstream-ci / earthkit-data (gnu@debian-11, 3.11)
==> Build of upstream package metkit failed on platform gnu@debian-11, exiting.
|
|
downstream-ci / pygribjump (gnu@debian-11, 3.11)
==> Build of upstream package metkit failed on platform gnu@debian-11, exiting.
|
|
downstream-ci / pymultio (gnu@debian-11, 3.11)
==> Build of upstream package metkit failed on platform gnu@debian-11, exiting.
|
|
downstream-ci / pymultio (clang@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / pygribjump (gnu@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci / pymultio (gnu@ubuntu-22.04, 3.11)
==> Build of upstream package metkit failed on platform gnu@ubuntu-22.04, exiting.
|
|
downstream-ci / pygribjump (clang@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / earthkit-data (gnu@fedora-37, 3.11)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci / earthkit-plots (clang@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / earthkit (gnu@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci / earthkit-plots (gnu@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci / earthkit (clang@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / pygribjump (gnu@ubuntu-22.04, 3.11)
==> Build of upstream package metkit failed on platform gnu@ubuntu-22.04, exiting.
|
|
downstream-ci / earthkit (gnu@debian-11, 3.11)
==> Build of upstream package metkit failed on platform gnu@debian-11, exiting.
|
|
downstream-ci / pymultio (gnu@fedora-37, 3.11)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci / earthkit-plots (gnu@ubuntu-22.04, 3.11)
==> Build of upstream package metkit failed on platform gnu@ubuntu-22.04, exiting.
|
|
downstream-ci / earthkit-plots (gnu@debian-11, 3.11)
==> Build of upstream package metkit failed on platform gnu@debian-11, exiting.
|
|
downstream-ci / earthkit (gnu@ubuntu-22.04, 3.11)
==> Build of upstream package metkit failed on platform gnu@ubuntu-22.04, exiting.
|
|
downstream-ci / pygribjump (gnu@fedora-37, 3.11)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci / polytope (gnu@ubuntu-22.04, 3.11)
==> Build of upstream package metkit failed on platform gnu@ubuntu-22.04, exiting.
|
|
downstream-ci / polytope (clang@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform clang@rocky-8.6, exiting.
|
|
downstream-ci / polytope (gnu@rocky-8.6, 3.11)
==> Build of upstream package eccodes failed on platform gnu@rocky-8.6, exiting.
|
|
downstream-ci / polytope (gnu@debian-11, 3.11)
==> Build of upstream package metkit failed on platform gnu@debian-11, exiting.
|
|
downstream-ci / earthkit (gnu@fedora-37, 3.11)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci / earthkit-plots (gnu@fedora-37, 3.11)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
downstream-ci / polytope (gnu@fedora-37, 3.11)
==> Build of upstream package eccodes failed on platform gnu@fedora-37, exiting.
|
|
private-downstream-ci
Process completed with exit code 1.
|
|
private-downstream-ci
Workflow FAILED!
|
|
downstream-ci-hpc / eccodes (gnu-12.2.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci-hpc / eccodes (gnu-8.5.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci-hpc / eccodes (intel-2021.4.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / eccodes (gnu@fedora-37)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, ecmwf/build-package@v2. 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/
|
|
downstream-ci / eccodes (gnu@fedora-37)
Failed to POST performance data!
|
|
downstream-ci / eccodes (gnu@fedora-37)
The process '/usr/bin/env' failed with exit code 8
|
|
downstream-ci / eccodes (gnu@fedora-37)
Error getting repository HEAD for libaec: Not Found - https://docs.github.com/rest/git/refs#get-a-reference
|
|
downstream-ci / eccodes (clang@rocky-8.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, ecmwf/build-package@v2. 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/
|
|
downstream-ci / eccodes (clang@rocky-8.6)
The process '/usr/bin/env' failed with exit code 8
|
|
downstream-ci / eccodes (clang@rocky-8.6)
Error getting repository HEAD for libaec: Not Found - https://docs.github.com/rest/git/refs#get-a-reference
|
|
downstream-ci / eccodes (gnu@rocky-8.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, ecmwf/build-package@v2. 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/
|
|
downstream-ci / eccodes (gnu@rocky-8.6)
The process '/usr/bin/env' failed with exit code 8
|
|
downstream-ci / eccodes (gnu@rocky-8.6)
Error getting repository HEAD for libaec: Not Found - https://docs.github.com/rest/git/refs#get-a-reference
|
|
downstream-ci-hpc / eccodes (nvidia-22.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci-hpc / mir (gnu-12.2.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / metkit (gnu-8.5.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / mir (intel-2021.4.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / metkit (gnu-12.2.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / mir (gnu-8.5.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / metkit (nvidia-22.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / eccodes-python (gnu-8.5.0, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / metkit (intel-2021.4.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / mir (nvidia-22.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci / mir (gnu@fedora-37)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / mir (gnu@fedora-37)
Failed to POST performance data!
|
|
downstream-ci / metkit (gnu@rocky-8.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / metkit (clang@rocky-8.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / eccodes-python (clang@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / mir (clang@rocky-8.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / eccodes-python (gnu@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / mir (gnu@rocky-8.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci-hpc / fdb (gnu-12.2.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / fdb (intel-2021.4.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / fdb (gnu-8.5.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / cfgrib (gnu-8.5.0, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / fdb (nvidia-22.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / pdbufr (gnu-8.5.0, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci / metkit (gnu@fedora-37)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / metkit (gnu@fedora-37)
Failed to POST performance data!
|
|
downstream-ci-hpc / multio (gnu-12.2.0, openmpi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (gnu-8.5.0, intel_mpi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (nvidia-22.11, hpcx_openmpi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / pyfdb (gnu-8.5.0, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (gnu-12.2.0, mpi_off)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / gribjump (gnu-12.2.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (gnu-12.2.0, hpcx_openmpi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (intel-2021.4.0, intel_mpi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (gnu-12.2.0, intel_mpi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (gnu-8.5.0, hpcx_openmpi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / gribjump (nvidia-22.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (nvidia-22.11, mpi_off)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / gribjump (gnu-8.5.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (nvidia-22.11, openmpi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / gribjump (intel-2021.4.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (intel-2021.4.0, hpcx_openmpi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (intel-2021.4.0, openmpi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci / eccodes-python (gnu@debian-11, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, ecmwf/build-package@v2. 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/
|
|
downstream-ci / eccodes-python (gnu@debian-11, 3.11)
Error getting repository HEAD for libaec: Not Found - https://docs.github.com/rest/git/refs#get-a-reference
|
|
downstream-ci / mir (gnu@ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, ecmwf/build-package@v2. 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/
|
|
downstream-ci / mir (gnu@ubuntu-22.04)
No workflow artifacts found for atlas
|
|
downstream-ci / mir (gnu@ubuntu-22.04)
Error getting repository HEAD for libaec: Not Found - https://docs.github.com/rest/git/refs#get-a-reference
|
|
downstream-ci / eccodes-python (gnu@ubuntu-22.04, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, ecmwf/build-package@v2. 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/
|
|
downstream-ci / eccodes-python (gnu@ubuntu-22.04, 3.11)
Error getting repository HEAD for libaec: Not Found - https://docs.github.com/rest/git/refs#get-a-reference
|
|
downstream-ci-hpc / multio (gnu-8.5.0, openmpi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (nvidia-22.11, intel_mpi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (gnu-8.5.0, mpi_off)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / multio (intel-2021.4.0, mpi_off)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / pygribjump (gnu-8.5.0, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / earthkit-data (gnu-8.5.0, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci / eccodes-python (gnu@fedora-37, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / eccodes-python (gnu@fedora-37, 3.11)
Failed to POST performance data!
|
|
downstream-ci-hpc / pymultio (gnu-8.5.0, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci / metkit (gnu@debian-11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, ecmwf/build-package@v2. 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/
|
|
downstream-ci / metkit (gnu@debian-11)
The process '/usr/bin/env' failed with exit code 2
|
|
downstream-ci / metkit (gnu@debian-11)
Error getting repository HEAD for libaec: Not Found - https://docs.github.com/rest/git/refs#get-a-reference
|
|
downstream-ci / mir (gnu@debian-11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, ecmwf/build-package@v2. 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/
|
|
downstream-ci / mir (gnu@debian-11)
No workflow artifacts found for atlas
|
|
downstream-ci / mir (gnu@debian-11)
Error getting repository HEAD for libaec: Not Found - https://docs.github.com/rest/git/refs#get-a-reference
|
|
downstream-ci-hpc / earthkit-plots (gnu-8.5.0, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci-hpc / earthkit (gnu-8.5.0, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci / metkit (gnu@ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, ecmwf/build-package@v2. 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/
|
|
downstream-ci / metkit (gnu@ubuntu-22.04)
The process '/usr/bin/env' failed with exit code 2
|
|
downstream-ci / metkit (gnu@ubuntu-22.04)
Error getting repository HEAD for libaec: Not Found - https://docs.github.com/rest/git/refs#get-a-reference
|
|
downstream-ci / pdbufr (clang@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / cfgrib (gnu@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / cfgrib (clang@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pdbufr (gnu@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / fdb (clang@rocky-8.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / fdb (gnu@rocky-8.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci-hpc / polytope (gnu-8.5.0, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/
|
|
downstream-ci / cfgrib (gnu@debian-11, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, ecmwf/build-package@v2. 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/
|
|
downstream-ci / cfgrib (gnu@debian-11, 3.11)
Error getting repository HEAD for libaec: Not Found - https://docs.github.com/rest/git/refs#get-a-reference
|
|
downstream-ci / fdb (gnu@ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / fdb (gnu@debian-11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / cfgrib (gnu@ubuntu-22.04, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, ecmwf/build-package@v2. 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/
|
|
downstream-ci / cfgrib (gnu@ubuntu-22.04, 3.11)
Error getting repository HEAD for libaec: Not Found - https://docs.github.com/rest/git/refs#get-a-reference
|
|
downstream-ci / cfgrib (gnu@fedora-37, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / cfgrib (gnu@fedora-37, 3.11)
Failed to POST performance data!
|
|
downstream-ci / pdbufr (gnu@fedora-37, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pdbufr (gnu@fedora-37, 3.11)
Failed to POST performance data!
|
|
downstream-ci / fdb (gnu@fedora-37)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / fdb (gnu@fedora-37)
Failed to POST performance data!
|
|
downstream-ci / multio (gnu@rocky-8.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / gribjump (clang@rocky-8.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pyfdb (gnu@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pyfdb (clang@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / gribjump (gnu@rocky-8.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pyfdb (gnu@debian-11, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / gribjump (gnu@ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / multio (clang@rocky-8.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pdbufr (gnu@ubuntu-22.04, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, ecmwf/build-package@v2. 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/
|
|
downstream-ci / pdbufr (gnu@ubuntu-22.04, 3.11)
Error getting repository HEAD for libaec: Not Found - https://docs.github.com/rest/git/refs#get-a-reference
|
|
downstream-ci / pdbufr (gnu@debian-11, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6, ecmwf/build-package@v2. 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/
|
|
downstream-ci / pdbufr (gnu@debian-11, 3.11)
Error getting repository HEAD for libaec: Not Found - https://docs.github.com/rest/git/refs#get-a-reference
|
|
downstream-ci / multio (gnu@debian-11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / gribjump (gnu@debian-11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pyfdb (gnu@fedora-37, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pyfdb (gnu@fedora-37, 3.11)
Failed to POST performance data!
|
|
downstream-ci / pyfdb (gnu@ubuntu-22.04, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
private-downstream-ci-hpc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@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/
|
|
downstream-ci / multio (gnu@fedora-37)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / multio (gnu@fedora-37)
Failed to POST performance data!
|
|
downstream-ci / multio (gnu@ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / gribjump (gnu@fedora-37)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / gribjump (gnu@fedora-37)
Failed to POST performance data!
|
|
downstream-ci / earthkit-data (gnu@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit-data (clang@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pymultio (gnu@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit-data (gnu@ubuntu-22.04, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit-data (gnu@debian-11, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pygribjump (gnu@debian-11, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pymultio (gnu@debian-11, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pymultio (clang@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pygribjump (gnu@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pymultio (gnu@ubuntu-22.04, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pygribjump (clang@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit-data (gnu@fedora-37, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit-data (gnu@fedora-37, 3.11)
Failed to POST performance data!
|
|
downstream-ci / earthkit-plots (clang@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit (gnu@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit-plots (gnu@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit (clang@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pygribjump (gnu@ubuntu-22.04, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit (gnu@debian-11, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pymultio (gnu@fedora-37, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pymultio (gnu@fedora-37, 3.11)
Failed to POST performance data!
|
|
downstream-ci / earthkit-plots (gnu@ubuntu-22.04, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit-plots (gnu@debian-11, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit (gnu@ubuntu-22.04, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pygribjump (gnu@fedora-37, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / pygribjump (gnu@fedora-37, 3.11)
Failed to POST performance data!
|
|
downstream-ci / polytope (gnu@ubuntu-22.04, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / polytope (clang@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / polytope (gnu@rocky-8.6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / polytope (gnu@debian-11, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit (gnu@fedora-37, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit (gnu@fedora-37, 3.11)
Failed to POST performance data!
|
|
downstream-ci / earthkit-plots (gnu@fedora-37, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / earthkit-plots (gnu@fedora-37, 3.11)
Failed to POST performance data!
|
|
downstream-ci / polytope (gnu@fedora-37, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/github-script@v6. 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/
|
|
downstream-ci / polytope (gnu@fedora-37, 3.11)
Failed to POST performance data!
|
|
private-downstream-ci
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@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/
|
|
notify
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ecmwf/notify-teams@v1. 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/
|