Update dependency wp-coding-standards/wpcs to v2#1814
Closed
renovate-bot wants to merge 1 commit intoampproject:developfrom
Closed
Update dependency wp-coding-standards/wpcs to v2#1814renovate-bot wants to merge 1 commit intoampproject:developfrom
renovate-bot wants to merge 1 commit intoampproject:developfrom
Conversation
1cbc52d to
2dfbbb9
Compare
Member
|
WPCS 2.0 has been released. The PR here passes Travis CI checks because wp-dev-lib is currently configured to skip running PHPCS when there are no PHP files in the PR diff. This is blocked by #1822. |
010d245 to
5511968
Compare
5511968 to
bc82d76
Compare
bc82d76 to
77aaea9
Compare
Collaborator
|
Closing in favor of #1868. |
Renovate Ignore NotificationAs this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 2.x releases. However, if you upgrade to 2.x manually then Renovate will then reenable updates for minor and patch updates automatically. If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened. |
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
4 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.
This PR contains the following updates:
1.2.1->2.0.0Release Notes
WordPress-Coding-Standards/WordPress-Coding-Standards
v2.0.0Compare Source
Important information about this release:
WordPressCS 2.0.0 contains breaking changes, both for people using custom rulesets as well as for sniff developers who maintain a custom PHPCS standard based on WordPressCS.
Support for
PHP_CodeSniffer2.x has been dropped, the new minimumPHP_CodeSnifferversion is 3.3.1.Also, all previously deprecated sniffs, properties and methods have been removed.
Please read the complete changelog carefully before you upgrade.
If you are a maintainer of an external standard based on WordPressCS and any of your custom sniffs are based on or extend WPCS sniffs, please read the Developers Upgrade Guide to WordPressCS 2.0.0.
Changes since 2.0.0-RC1
Fixed
WordPress-Extra: Reverted back to including theSquiz.WhiteSpace.LanguageConstructSpacingsniff instead of the newGeneric.WhiteSpace.LanguageConstructSpacingsniff as the new sniff is not (yet) available when the PEAR install of PHPCS is used.Changes since 1.2.1
For a full list of changes from the 1.2.1 version, please review the following changelog:
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "
rebase!".🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot. View repository job log here.