You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to migrate all Github Actions that use Node.js version 20 to newer versions that use Node.js 24 as this functionality will be deprecated from Github runners as of June 2nd, 2026: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/. You can defer it via an environment variable if necessary until September, but that is kicking the problem further down the line.
I previously made a PR (#29859) to address this, but the following issues still remain and should be addressed before that date:
The CI setup on earlgrey_1.0.0 has not been updated accordingly, and will probably run into issues.
Since merging that PR some CI changes to the FPGA jobs have caused the warning to creep back in. I suspect this was due to older versions being re-introduced by PRs changing CI like e.g. [ci] Rework FPGA scheduling #29811, which drops the download-artifact version from v8 back to v5 for example.
We should in general be more cautious of PRs to CI in this period and check the versions of the actions being introduced/changed.
Description
We need to migrate all Github Actions that use Node.js version 20 to newer versions that use Node.js 24 as this functionality will be deprecated from Github runners as of June 2nd, 2026: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/. You can defer it via an environment variable if necessary until September, but that is kicking the problem further down the line.
I previously made a PR (#29859) to address this, but the following issues still remain and should be addressed before that date:
earlgrey_1.0.0has not been updated accordingly, and will probably run into issues.download-artifactversion fromv8back tov5for example.