Skip to content

Composer Dev(deps-dev): Bump newfold-labs/wp-php-standards from 1.2.6 to 2.0.0 - #307

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/composer/main/newfold-labs/wp-php-standards-2.0.0
Open

Composer Dev(deps-dev): Bump newfold-labs/wp-php-standards from 1.2.6 to 2.0.0#307
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/composer/main/newfold-labs/wp-php-standards-2.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 21, 2026

Copy link
Copy Markdown
Contributor

Bumps newfold-labs/wp-php-standards from 1.2.6 to 2.0.0.

Release notes

Sourced from newfold-labs/wp-php-standards's releases.

2.0.0

What's Changed

New Contributors

Full Changelog: newfold-labs/wp-php-standards@1.2.6...2.0.0

Changelog

Sourced from newfold-labs/wp-php-standards's changelog.

Changelog

All notable changes to this project are documented here. The format follows Keep a Changelog, and the project follows semantic versioning.

Unreleased

Fixed

  • Newfold.PHP.ForbiddenDoubleColonClass now reports chained ::class:: fetches it used to walk past: Thing::CLASS::FOO, since PHP accepts any casing of the keyword; Thing::class ::FOO, since whitespace between the operators is legal; and Thing::class::$prop and Thing::class::{$name}, which the sniff skipped because it insisted on a plain name after the second operator. All four parse only on PHP 8.3 and up.

    This is a breaking change. Code that passed before can fail now.

  • Newfold.PHP.ForbiddenUnionType now reports union types it used to walk past. It only visited pipes reachable from a parameter list or a return type, and its list of type tokens had no entry for self, static or parent. Property types, relative type names, disjunctive normal form types such as (A&B)|null, and unions on typed class constants all went unreported. Every one of them is a parse error on PHP 7, so the file would fatal rather than fail at the call site.

    This is a breaking change. Code that passed before can fail now.

Changed

  • testVersion raised from 7.3- to 7.4-, and minimum_supported_wp_version from 5.8 to 6.6. 7.4 is the floor in the support matrix, the minimum WordPress itself supports, and the floor this repository already tests against. 6.6 is what every brand plugin declares in its Requires at least header.

    In practice this changes nothing for any current consumer. Every repository in the Satis index that lints with this standard sets both values in its own ruleset, so the defaults here are the documented position rather than an enforcement point.

  • WordPress.NamingConventions.ValidHookName is excluded from the standard. It expects lowercase underscore-separated hook names, so it reported every hook named to our own convention.

  • Pinned every dependency to an explicit range. All four were @stable, which accepts any future major. A new PHP_CodeSniffer, WPCS or PHPCompatibility major would have landed in every consumer's CI on the next composer update with no deprecation window. The pins resolve to the same versions as before, so this is no change in behaviour today.

... (truncated)

Commits
  • 0303e24 Merge pull request #17 from newfold-labs/update/PRESS0-4793-pin-dependencies
  • 130cf10 Merge pull request #18 from newfold-labs/add/PRESS0-4793-sniff-tests
  • 978368d Merge pull request #19 from newfold-labs/fix/PRESS0-4793-forbidden-union-type
  • 363376b Merge pull request #20 from newfold-labs/fix/PRESS0-4793-forbidden-double-col...
  • 66ac7d2 Merge pull request #21 from newfold-labs/add/PRESS0-4793-valid-hook-name-sniff
  • 533b1d3 Merge pull request #22 from newfold-labs/add/PRESS0-4793-namespace-declaratio...
  • d83d8f0 Merge pull request #23 from newfold-labs/enhance/PRESS0-4793-ruleset-config
  • ca4390d fix(PRESS0-4793): report the prefix convention as a warning
  • 1b0855f Merge branch 'add/PRESS0-4793-namespace-declaration-sniff' into enhance/PRESS...
  • ba9f62f fix(PRESS0-4793): match the namespace convention to the vendor we ship
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [newfold-labs/wp-php-standards](https://github.com/newfold-labs/wp-php-standards) from 1.2.6 to 2.0.0.
- [Release notes](https://github.com/newfold-labs/wp-php-standards/releases)
- [Changelog](https://github.com/newfold-labs/wp-php-standards/blob/main/CHANGELOG.md)
- [Commits](newfold-labs/wp-php-standards@1.2.6...2.0.0)

---
updated-dependencies:
- dependency-name: newfold-labs/wp-php-standards
  dependency-version: 2.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@github-actions

Copy link
Copy Markdown
Contributor

Coverage: Base 33.46% → PR 33.46% (must not decrease).
✅ No decrease.

Code Coverage

project coverage report 33.46% @ 438c5cf

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants