Skip to content

[prod/HAFSv.2.2] Start HAFS v2.2 production branch #855

[prod/HAFSv.2.2] Start HAFS v2.2 production branch

[prod/HAFSv.2.2] Start HAFS v2.2 production branch #855

Triggered via pull request March 25, 2026 17:37
@dpsarmiedpsarmie
opened #3164
Status Success
Total duration 13s
Artifacts

update_project_labels.yaml

on: pull_request_target
Baseline labels
5s
Baseline labels
Input data
6s
Input data
Priority
8s
Priority
Subcomponents involved
5s
Subcomponents involved
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Baseline labels
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nipe0324/update-project-v2-item-field@v2.0.2. 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/
Subcomponents involved
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nipe0324/update-project-v2-item-field@v2.0.2. 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/
Input data
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nipe0324/update-project-v2-item-field@v2.0.2. 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/
Priority
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: EndBug/project-fields@v2.1.0, nipe0324/update-project-v2-item-field@v2.0.2. 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/