[desrosj]

Updates the bundled sodium_compat library from 1.24.1 to 1.24.2, the latest release on the v1.x branch that WordPress uses.

This update is a hardening release.

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

WordPress only loads sodium_compat when the native Sodium extension isn't available (! function_exists( 'sodium_crypto_box' ) in wp-includes/compat.php). These fixes only take effect on those sites.

How this follows previous updates

• WordPress bundles the files under lib/, namespaced/ and src/, plus autoload.php, autoload-php7.php, composer.json and LICENSE. That's 108 files, and upstream's tests and build tooling are left out.
• 1.24.2 adds no new files. Upstream has no files in those directories that WordPress leaves out, so the missing files problem from the 1.21.1 update ([58753]) can't happen here.
• 9 files changed upstream, and all of them are updated.
• Before this change, 107 of the 108 files were identical to upstream v1.24.1. The exception is src/Core/Curve25519.php, which was missing its trailing newline in r63397. This PR restores the newline, so all 108 files now match upstream v1.24.2 byte for byte.
• The commit message follows r63397 (1.24.1), and adds that revision to the Follow-up to list.

Testing

• php -l passes on the changed files under PHP 8.6.0-dev.
• vendor/bin/phpcs --standard=phpcompat.xml.dist src/wp-includes/sodium_compat/ is clean.
• vendor/bin/phpcs src/wp-includes/sodium_compat/ is clean.
• All bundled files match upstream v1.24.2 byte for byte.

Use of AI Tools

• AI assistance: Yes
• Tool(s): Claude Code
• Model(s): Claude Opus 5.5
• Used for: reviewing past sodium_compat updates, comparing the bundled files with upstream, reading the 1.24.1 to 1.24.2 diff, running the checks above, and drafting this description. I reviewed the result.

🤖 Generated with Claude Code

---

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 desrosj.

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.

[github-actions]

A commit was made that fixes the Trac ticket referenced in the description of this pull request.

SVN changeset: 65398
GitHub commit: c455619

This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.