Skip to content

Update wp-coding-standards/wpcs to 3.4.1 - #2601

Merged
westonruter merged 1 commit into
WordPress:trunkfrom
obenland:update/wpcs-3.4.1
Jul 27, 2026
Merged

Update wp-coding-standards/wpcs to 3.4.1#2601
westonruter merged 1 commit into
WordPress:trunkfrom
obenland:update/wpcs-3.4.1

Conversation

@obenland

Copy link
Copy Markdown
Member

Updates the locked version of wp-coding-standards/wpcs to 3.4.1, including any transitive PHPCS/PHPCSUtils/PHPCSExtra bumps required by it.

The composer.json constraint already allows 3.4.1, so only composer.lock changes.

Verified locally: phpcs output is identical before and after the update. [. phpcs unchanged: CLEAN(rc=0)]

Part of an org-wide sweep to get all repos onto WPCS 3.4.1.

🤖 Generated with Claude Code

Regenerates composer.lock. The version constraint already allows 3.4.1,
so no composer.json change is needed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 27, 2026 16:45

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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

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: obenland <obenland@git.wordpress.org>

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

@obenland

Copy link
Copy Markdown
Member Author

@mukeshpanchal27 @msranjana Could I ask for your review/merge? Thank you! It looks like I can't assign labels or milestones.

@codecov

codecov Bot commented Jul 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.35%. Comparing base (0a51c32) to head (8e414ac).
⚠️ Report is 12 commits behind head on trunk.

Additional details and impacted files
@@           Coverage Diff           @@
##            trunk    #2601   +/-   ##
=======================================
  Coverage   70.35%   70.35%           
=======================================
  Files          91       91           
  Lines        7867     7867           
=======================================
  Hits         5535     5535           
  Misses       2332     2332           
Flag Coverage Δ
multisite 70.35% <ø> (ø)
single 35.17% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@obenland

Copy link
Copy Markdown
Member Author

The two failing checks are repo policy (missing [Type] label and milestone) — I don't have triage rights here, so a maintainer would need to add them. Suggest [Type] Enhancement + Infrastructure and the performance-lab n.e.x.t milestone. All functional checks pass.

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

Labels

no milestone PRs that do not have a defined milestone for release [Type] Enhancement A suggestion for improvement of an existing feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants