[sirreal]

Upgrades the 5.0 branch to Node.js 24.x and npm 11.x. Also:

• Runs Grunt with --no-maglev --no-concurrent-sparkplug, as r63771 does on trunk, to avoid hangs at exit on Node.js 24.
• Runs Grunt with --openssl-legacy-provider, because webpack 4 hashes with md4, which OpenSSL 3 disables.
• Converts package-lock.json to lockfile version 3 with npm install --package-lock-only. No package path, version, resolved URL or integrity changes.

The build matches the 5.0.31 release except wp-includes/js/tinymce/wp-tinymce.js.gz, which compresses to different bytes with the same content.

Trac ticket: https://core.trac.wordpress.org/ticket/66636

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Applying the changes to each branch, building on Node.js 24 and comparing the output with the release, and drafting this description.

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props jonsurrell.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.