Build/Test Tools: Add a scoped Composer exception for the WPCS security advisory to unblock CI on the 6.9 branch. - #12742
Conversation
…ty advisory to unblock CI on the 6.9 branch.
|
This and #12741 are a draft because I don't know the core philosophy (yet) around dependencies with security advisories, when the action to update would trigger a whole range of new issues to fix (code sniffs). |
Test using WordPress PlaygroundThe 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
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
|
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 Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Trac ticket: https://core.trac.wordpress.org/ticket/65739
This adds a scoped Composer audit exception for
GHSA-3pwp-g2mj-5p3vto unblock dependency installation on the 6.9 branch.It keeps WPCS at 3.2.0 and avoids introducing a broad coding-standards delta on the release branch.
Testing
composer validatepassed, with the existing version-field warning.composer installresolved WPCS 3.2.0.composer lint:errorscould not complete under PHP 8.4.20 because PHPCS 3.13.2 raised aValueErrorbefore producing results.