Make WordPress Core

Opened 2 days ago

Last modified 2 days ago

#65451 new task (blessed)

Update Node.js to 24.x

Reported by: desrosj's profile desrosj Owned by:
Milestone: 7.1 Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords:
Focuses: Cc:

Description

This is a tracking ticket for the work required to upgrade Core to using Node.js 24.x, which is the version with Active LTS status at the time of creating this ticket.

For reference, the Core Handbook has a page documenting the related considerations and changes required when updating Node.js for WordPress and includes a checklist to follow.

Some key dates:

  • 20.x reached end-of-life on April 30, 2026.
  • 22.x reaches EOL on April 30, 2027
  • 24.x transitions to maintenance LTS on April 30, 2027.
  • 26.x is Current and transitions to Active LTS in October 2026.
  • Starting with version 27, the Node.js project is transitioning from an even/odd versioning practice (even releases only reach LTS status, odd releases are not meant for production use and supported only for 6 months) to an annual one (every release reaches LTS status after a 6 month Current phase).

Previously:

  • #59663 - Node.js 20.x (18.x was skipped)
  • #56658 - Node.js 16.x (#59187 for bundled themes)
  • #52341 - Node.js 14.x (all older branches receiving security updates)
  • #45241 - Node.js 10.x

Change History (5)

#1 @desrosj
2 days ago

Related #65432.

This ticket was mentioned in PR #11776 on WordPress/wordpress-develop by @desrosj.


2 days ago
#2

  • Keywords has-patch added

This makes the necessary changes to update the versions of Node.js and npm used by WordPress Core.

Trac ticket: Core-65451.

AI assistance: None

@desrosj commented on PR #11776:


2 days ago
#3

This PR resolve Core-65432.

I don't know that this resolves Core-65432. This PR is specifically targeting Core itself and does not make any changes to the respective GitHub Actions workflow files. While the changes required to make sure actions continue to run within the GHA environment are related, they do not necessarily impact each other (the actions/setup-node action installs and configures any version of Node.js the project is using).

Also, do you have plans to wrap this up soon?

I have created Core-65451 to track this effort in Trac/wordpress-develop SVN. There has also been a significant amount of legwork around this already in https://github.com/WordPress/gutenberg/issues/72973.

As far as the current status. Upgrading Node.js is currently blocked on the Systems Team side.

#4 @desrosj
2 days ago

  • Keywords has-patch removed

To link related discussions, there has been significant effort on the Gutenberg side of things in Gutneberg-72973, which included the creation of the new handbook page mentioned in this ticket's description.

There is also a project board in GitHub.

#5 @desrosj
2 days ago

This is also blocked by #63013.

Note: See TracTickets for help on using tickets.