Refs:
* https://github.com/Yoast/yoastcs/releases/tag/3.2.0
* https://github.com/PHPCSStandards/PHP_CodeSniffer/releases
* https://github.com/PHPCSStandards/phpcsutils/releases
* https://github.com/PHPCompatibility/PHPCompatibilityWP/releases
* https://github.com/automattic/VIP-Coding-Standards/releases
* https://github.com/sirbrillig/phpcs-variable-analysis/releases

Composer: update to YoastCS 3.2.0

Bumps [DavidAnson/markdownlint-cli2-action](https://github.com/davidanson/markdownlint-cli2-action) from 19 to 20.
- [Release notes](https://github.com/davidanson/markdownlint-cli2-action/releases)
- [Commits](DavidAnson/markdownlint-cli2-action@v19...v20)

---
updated-dependencies:
- dependency-name: DavidAnson/markdownlint-cli2-action
  dependency-version: '20'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

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

…dAnson/markdownlint-cli2-action-20

GH Actions: Bump DavidAnson/markdownlint-cli2-action from 19 to 20

Support for the `reviewers` key in `dependabot.yml` files is being removed by GitHub on May 20th 2025.

The recommendation is to have a `CODEOWNERS` file to set reviewers instead.

For now, this commit removes the `reviewers` key from the `dependabot.yml` file without replacing it.
That should prevent comments being left in PRs by the dependabot bot account about the field no longer being supported.

Ref:
* https://github.blog/changelog/2025-04-29-dependabot-reviewers-configuration-option-being-replaced-by-code-owners/
* https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#codeowners-file-location

…ewers

Dependabot: remove reviewers

As of the release of `shivammathur/setup-php` v`2.35.0`, this should no longer be needed as the `setup-php` action runner will automatically use the `secrets.GITHUB_TOKEN` token.

Ref:
* https://github.com/shivammathur/setup-php/releases/tag/2.35.0
* shivammathur/setup-php@55463ff

…-php-2.35.0

GH Actions: remove GH Token set via `env`

> A warning is now emitted when a data provider provides data sets that have more values than the test method consumes using arguments

While not problematic for PHPUnit Polyfills 1.x - 3.x, this will fail tests for 4.x (without this change).

Ref: https://github.com/sebastianbergmann/phpunit/blob/12.2/ChangeLog-12.2.md#changed-1

XTestCaseTest: update for PHPUnit 12.2.0

…sible()

Since PHP 8.1, calling the `Reflection*::setAccessible()` methods is no longer necessary as reflected properties/methods/etc will always be accessible.
However, the method calls are still needed for PHP < 8.1.

As of PHP 8.5, calling the `Reflection*::setAccessible()` methods is now formally deprecated and will yield a deprecation notice, which will fail test runs.
As of PHP 9.0, the `setAccessible()` method(s) will be removed.

With the latter in mind, this commit prevents the deprecation notice by making the calls to `setAccessible()` conditional.

Silencing the deprecation would mean, this would need to be "fixed" again come PHP 9.0, while the current solution should be stable, including for PHP 9.0.

Ref: https://wiki.php.net/rfc/deprecations_php_8_5#extreflection_deprecations

…hp-8.5

PHP 8.5 | Tests: prevent deprecation notice for Reflection*::setAccessible()

Remove the condition containing a hard-coded repository name in favour of a more generic condition which should safeguard that the cron job doesn't run on forks just the same.

…-cronjobs-on-forks-condition

GH Actions: improve "don't run on forks" condition

Includes updating the `VERSION` constant in the `Autoload` class.

Changelog for the 1.1.5 release