update-actions-node-version

Fix GitHub Actions Node.js deprecation warnings by upgrading affected actions to newer releases supporting Node 24, pinning full commit SHAs, and applying the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 environment flag where necessary.

FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 is a global workflow environment flag that forces the runner to use Node 24 for lagging implicit actions and runner-injected steps that have not yet upgraded their runtime natively.

Safely upgrade GitHub Actions by identifying affected actions from deprecation warnings, verifying new Node 24-compatible releases, pinning full SHAs, and applying the environment flag to cover remaining implicit actions.

Yes, pinning full commit SHAs is required when upgrading GitHub Actions Node.js versions to ensure immutable, verified releases and prevent supply chain risks after resolving deprecation warnings.

GitHub Actions workflows fail with Node 20 deprecation warnings because the runtime is outdated; resolve this by upgrading actions to Node 24-compatible versions and forcing the runtime with a global environment flag.

Yes, you can apply changes across repository workflows by upgrading affected actions to Node 24-compatible releases and setting the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 flag at the workflow level to reduce deprecation failure risks.