Repair wp/5.7 branch Actions: Let the current Composer release install this branch's dependencies

[desrosj]

Part of #82936.

What?

Two composer.json changes, one commit each:

1. Declares config.allow-plugins for the two Composer plugins this repository uses.
2. Declares config.platform.php as 7.4 and require.php as >=5.6.20, and regenerates composer.lock to match.

The composer service in wp-env keeps the floating composer image, so it always runs the latest Composer.

Why?

allow-plugins: Composer 2.2+ requires plugins to be explicitly allowed. Older Composer only warned, but current Composer fails with composer/installers contains a Composer plugin which is blocked by your allow-plugins config. That breaks the Install a PHPUnit release this PHP version can load step from #84774 and the phpcs job's composer install from #84775. --no-plugins isn't a workaround, because dealerdirect/phpcodesniffer-composer-installer is the plugin that registers the PHPCS standards.

platform.php: The lock was resolved for PHP 7.4 but didn't record it, so Composer checked it against the container's PHP (8.5) and refused to install phpspec/prophecy 1.12.2 (requires php ^7.2 || ~8.0, <8.1). Declaring the platform makes the lock install the same way at any container PHP. 7.4 satisfies every locked package and matches the PHP version the phpcs job uses. require.php records WordPress's minimum PHP version as the project's floor.

The lock was regenerated with composer update --lock, so no package versions changed. The only differences are the platform fields, the content-hash, plugin-api-version, some empty [] written as {}, and the squizlabs/php_codesniffer URLs now pointing to PHPCSStandards (same release and commit).

Testing Instructions

In the composer image (Composer 2.10.3, PHP 8.5.10):

command	before	after
composer install	exit 2	exit 0
vendor/bin/phpcs -i	—	lists PHPCompatibility, VariableAnalysis and the WordPress standards

Use of AI Tools

This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: e0552caf-493d-460d-8831-c4be7adf0dce

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: desrosj <desrosj@git.wordpress.org>

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