Skip to content

Bump Node.js to 24 and upgrade actions to Node.js 24 runtimes#64021

Merged
potiuk merged 1 commit intoapache:mainfrom
astronomer:bump-node24-ci
Mar 21, 2026
Merged

Bump Node.js to 24 and upgrade actions to Node.js 24 runtimes#64021
potiuk merged 1 commit intoapache:mainfrom
astronomer:bump-node24-ci

Conversation

@kaxil
Copy link
Member

@kaxil kaxil commented Mar 21, 2026

Bump Node.js from 20/21 to 24 across all CI workflows and upgrade actions that were still running on the Node.js 20 runtime. GitHub will force Node.js 24 starting June 2026.

Workflow node-version changes:

  • basic-tests.yml: 21 → 24
  • ui-e2e-tests.yml: 21 → 24
  • registry-build.yml: 20 → 24
  • registry-backfill.yml: 20 → 24

Action runtime upgrades (Node.js 20 → 24):

  • actions/setup-python: v5.6.0 → v6.2.0 (in .github/actions/breeze/action.yml)
  • pnpm/action-setup: already at v5.0.0 on main

Automated upgrade script:

  • upgrade_important_versions.py: LTS prefix v22v24

All package.json engine fields already require >=22, so Node 24 satisfies them.

Copy link
Member

@jason810496 jason810496 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I double checked the setup-python commit hash, LGTM, thanks!

Copy link
Contributor

@amoghrajesh amoghrajesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@potiuk potiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh.. You beat me to it :)

@potiuk
Copy link
Member

potiuk commented Mar 21, 2026

Compat tests fixed separately in #64020

@potiuk potiuk merged commit 39e01a2 into apache:main Mar 21, 2026
142 of 146 checks passed
@github-project-automation github-project-automation bot moved this from Backlog to Done in Airflow Registry Mar 21, 2026
@github-actions
Copy link

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-1-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 39e01a2 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

fat-catTW pushed a commit to fat-catTW/airflow that referenced this pull request Mar 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools area:registry backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants