Skip to content

Build/Test Tools: Add a scoped Composer exception for the WPCS security advisory to unblock CI on the 6.9 branch. - #12742

Open
lancewillett wants to merge 1 commit into
WordPress:6.9from
lancewillett:fix/wpcs-advisory-6.9
Open

Build/Test Tools: Add a scoped Composer exception for the WPCS security advisory to unblock CI on the 6.9 branch.#12742
lancewillett wants to merge 1 commit into
WordPress:6.9from
lancewillett:fix/wpcs-advisory-6.9

Conversation

@lancewillett

Copy link
Copy Markdown
Contributor

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

This adds a scoped Composer audit exception for GHSA-3pwp-g2mj-5p3v to 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 validate passed, with the existing version-field warning.
  • A fresh composer install resolved WPCS 3.2.0.
  • composer lint:errors could not complete under PHP 8.4.20 because PHPCS 3.13.2 raised a ValueError before producing results.

…ty advisory to unblock CI on the 6.9 branch.
@lancewillett

Copy link
Copy Markdown
Contributor Author

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

@github-actions

Copy link
Copy Markdown

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.

@lancewillett
lancewillett marked this pull request as ready for review July 28, 2026 18:57
@github-actions

Copy link
Copy Markdown

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.

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

Props lancewillett.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants