Skip to content

Upgrade GitHub Actions for Node 24 compatibility - #1142

Closed
salmanmkc wants to merge 1 commit into
langflow-ai:mainfrom
salmanmkc:upgrade-github-actions-node24
Closed

Upgrade GitHub Actions for Node 24 compatibility#1142
salmanmkc wants to merge 1 commit into
langflow-ai:mainfrom
salmanmkc:upgrade-github-actions-node24

Conversation

@salmanmkc

@salmanmkc salmanmkc commented Mar 13, 2026 •
edited
Loading

Copy link
Copy Markdown

Warning

You may currently be seeing a warning like this in your workflow runs:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20
and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, actions/setup-node@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/

The exact actions listed will vary per workflow.

Upgrades GitHub Actions to versions that support Node 24, since Node 20 is reaching EOL in April 2026.

Changes

Action Old Version(s) New Version Compare Files
actions/checkout v4 v6 Diff build-multiarch.yml, dependency-audit.yml, deploy-docs-draft.yml, deploy-gh-pages.yml, lint-frontend.yml, publish-mcp.yml, publish-sdk-python.yml, publish-sdk-typescript.yml, test-e2e.yml, test-integration.yml, update-uv-lock.yml
actions/setup-node v4 v6 Diff dependency-audit.yml, deploy-docs-draft.yml, deploy-gh-pages.yml, lint-frontend.yml, publish-sdk-typescript.yml, test-e2e.yml, test-integration.yml
actions/upload-artifact v4 v7 Diff build-multiarch.yml, deploy-docs-draft.yml, test-e2e.yml

Context

Per GitHub's announcement, Node 20 is being deprecated and runners will default to Node 24 starting June 2nd, 2026.

  • Node 20 EOL: April 2026
  • Node 24 becomes default: June 2nd, 2026

Release Notes

Release notes for actions/checkout

v6.0.2

What's Changed

Full Changelog: actions/checkout@v6.0.1...v6.0.2

v6.0.1

What's Changed

Full Changelog: actions/checkout@v6...v6.0.1

v6.0.0

What's Changed

Full Changelog: https://github.com/actions/checkout/compare/v5.0.

...truncated

v5.0.1

What's Changed

Full Changelog: actions/checkout@v5...v5.0.1

v4.3.1

What's Changed

Full Changelog: actions/checkout@v4...v4.3.1

Release notes for actions/upload-artifact

v7.0.0

v7 What's new

Direct Uploads

Adds support for uploading single files directly (unzipped). Callers can set the new archive parameter to false to skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. The name parameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.

ESM

To support new versions of the @actions/* packag

...truncated

v6.0.0

v6 - What's new

[!IMPORTANT]
actions/upload-artifact@v6 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v5 had preliminary support for Node.js 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed

...truncated

v5.0.0

What's Changed

BREAKING CHANGE: this update supports Node v24.x. This is not a breaking change per-se but we're treating it as such.

...truncated

v4.6.2

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v4...v4.6.2

v4.6.1

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.6.1

Release notes for actions/setup-node

v6.3.0

What's Changed

Enhancements:

When using node-version-file: package.json, setup-node now prefers devEngines.runtime over engines.node.

Dependency updates:

...truncated

v6.2.0

What's Changed

Documentation

...truncated

v6.1.0

What's Changed

Enhancement:

Dependency updates:

...truncated

v6.0.0

What's Changed

Breaking Changes

Dependency Upgrades

  • Upgrade ts-jest from 29.1.2 to 29.4.1 and document breaking changes in v5 by @dependabot[bot] in #1336
  • Upgrade prettier from 2.8.8 to 3.6.2 by @dependabot[bot] in #1334
  • Upgrade

...truncated

v5.0.0

What's Changed

Breaking Changes

This update, introduces automatic caching when a valid packageManager field is present in your package.json. This aims to improve workflow performance and make dependency management more seamless.
To disable this automatic caching, set package-manager-cache: false

steps:
- uses: actions/chec

*...truncated*

</details>

## Notes

Worth running the workflows on a branch before merging to make sure everything still works.

@salmanmkc
Upgrade GitHub Actions for Node 24 compatibility
9d154da 
Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
@github-actions github-actions Bot added community ci ⬛ CI/CD, build, and infrastructure issues and removed community labels Mar 13, 2026
@MikeMcC399

MikeMcC399 commented Mar 13, 2026

Copy link
Copy Markdown

@salmanmkc

Could you possibly just link to the release notes instead of copying their contents?

Due to me having submitted a minor typo PR to actions/setup-node#1442 I am now getting notified on every single one of your related PRs in repos that I am not otherwise involved in, like this one.

@MikeMcC399

MikeMcC399 commented Sep 25, 2026

Copy link
Copy Markdown

@salmanmkc

It looks like this PR is now obsolete and can probably be closed.

@salmanmkc

salmanmkc commented Sep 25, 2026

Copy link
Copy Markdown
Author

Sorry about that @MikeMcC399, closed the PR. Migration is fully complete now to node 24, no longer making these prs.

@MikeMcC399

MikeMcC399 commented Sep 25, 2026

Copy link
Copy Markdown

Sorry about that @MikeMcC399, closed the PR. Migration is fully complete now to node 24, no longer making these prs.

I'm no longer getting messages. I was just going through some older issues though, so no worries!

Although you wrote "closed the PR", it is actually still open!

@salmanmkc salmanmkc closed this Sep 25, 2026
@salmanmkc

salmanmkc commented Sep 25, 2026

Copy link
Copy Markdown
Author

Sorry about that @MikeMcC399, closed the PR. Migration is fully complete now to node 24, no longer making these prs.

I'm no longer getting messages. I was just going through some older issues though, so no worries!

Although you wrote "closed the PR", it is actually still open!

Oh strange, I thought I clicked the button to close it, and was confused why it didn't show up, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

ci ⬛ CI/CD, build, and infrastructure issues

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@salmanmkc @MikeMcC399