Repository navigation
Conversation
Collaborator
|
@obenland could you fix the merge conflicts on this PR please? |
The lock already resolves 3.4.1; this raises the floor so a fresh resolve can't fall back to an older 3.x release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
obenland
force-pushed
the
update/wpcs-3.4.1
branch
from
October 23, 2026 16:36
c917a8b to
5ad9926
Compare
obenland
changed the title
Member
Author
|
Looks like this is no longer needed after #597. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Raises the
wp-coding-standards/wpcsconstraint from^3.1to^3.4.1.developalready moved to WPCS 3 in #559 and the lock already resolves 3.4.1, so this only raises the floor;composer.lockchanges by itscontent-hashonly.Part of an org-wide sweep to get all repos onto WPCS 3.4.1.
🤖 Generated with Claude Code