Repository navigation
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
a1ab6d1 to
4e4fa4f
Compare
|
Size Change: 0 B Total Size: 1.46 MB ℹ️ View Unchanged
|
4e4fa4f to
1629fd1
Compare
1629fd1 to
d271cd8
Compare
|
Size Change: 0 B Total Size: 1.46 MB ℹ️ View Unchanged
|
wp/6.3 branch Actions: Configure Composer policy to ignore irrelevant advisorieswp/6.3 branch Actions: Configure the Composer advisory policy
d271cd8 to
327ac53
Compare
327ac53 to
02960aa
Compare
Part of #82930.
What?
Adds a
config.policy.advisories.ignore-idblock tocomposer.json, configuring Composer's security-advisory policy to ignorePKSA-mh9b-91zm-m1gy(CVE-2026-45293) forwp-coding-standards/wpcs. No version constraint changes;wp-coding-standards/wpcsstays at^2.2.Why?
Composer's default advisory policy refuses to install any package release covered by a known advisory, whether or not the vulnerable code path is reachable from the consuming project. On this branch that blocks every
wp-coding-standards/wpcsrelease satisfying the existing^2.2requirement (2.2.0,2.2.1,2.3.0), so thePHP coding standardsjob fails at its "Install Composer dependencies" step:CVE-2026-45293 is an
eval()-injection bug in theWordPress.WP.EnqueuedResourceParameterssniff, which ships only in theWordPressandWordPress-Extrarulesets. This branch'sphpcs.xml.distpulls inWordPress-CoreandWordPress-Docsplus a set of individually-named sniffs, and references neither of those two rulesets — so the vulnerable sniff is never loaded and the advisory cannot apply to this repository at anywp-coding-standards/wpcsversion.Expressing the exclusion as an explicit policy entry keeps the suppression narrow and auditable: exactly one advisory ID is ignored, the reason sits next to the ID in the file, and Composer keeps enforcing its default policy for everything else. Since
wp/6.3is a frozen maintenance branch that cannot simply move to a patched major, this block is also the natural place to record any further advisory that is demonstrably unreachable here.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