set psr2r version instead of dev-main for compatibility with php_code… #3
Conversation
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
2 participants
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.
Related Issue(s)
Updates will not run
there's an issue with our php code standards that will prevent updates from running successfully currently. Looks like the latest release of psr2r-sniffer here (which came out yesterday) requires php_codesniffer v4.0.0 - but our codeand-wp-coding-standards is dependent on v3.
I'm just gonna update the codeand-wp-coding-standards repo so we're not depending on dev-main for psr2r-sniffer and roll back to the last release of 3.7 , this seems liek the most sensible temporary approach until we upgrade it to 4.0 - i'll add an issue for it shortly.
Mentioned here:
https://teamcodeand.slack.com/archives/G8679PKDE/p1759230104771309
Description
Mobile & Desktop Screenshots/Recordings
Added to documentation?
Database available?
/db/123/[optional] Are there any post-deployment or post-merge tasks we need to perform?
We need to add a tag to the
mainbranch0.4.2