Skip to content

Bump the composer group across 1 directory with 6 updates - #4407

Merged
felipeelia merged 1 commit into
developfrom
dependabot/composer/composer-f3fcfad3fb
Nov 9, 2026
Merged

felipeelia merged 1 commit into
developfrom
dependabot/composer/composer-f3fcfad3fb

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 9, 2026

Copy link
Copy Markdown
Contributor

Bumps the composer group with 6 updates in the / directory:

Package From To
phpunit/phpunit 9.6.22 9.6.33
composer/composer 2.10.1 2.11.1
league/flysystem 3.29.1 3.36.0
phpcsstandards/phpcsutils 1.1.3 1.2.3
squizlabs/php_codesniffer 3.13.5 3.13.6
wp-coding-standards/wpcs 3.1.0 3.4.1

Updates phpunit/phpunit from 9.6.22 to 9.6.33

Changelog

Sourced from phpunit/phpunit's changelog.

[9.6.33] - 2026-01-27

Changed

  • To prevent Poisoned Pipeline Execution (PPE) attacks using prepared .coverage files in pull requests, a PHPT test will no longer be run if the temporary file for writing code coverage information already exists before the test runs

[9.6.32] - 2026-01-24

Changed

  • PHPUnit\Framework\MockObject exceptions are now subtypes of PHPUnit\Exception

[9.6.31] - 2025-12-06

  • No changes; phpunit.phar rebuilt with PHP 8.4 to work around PHP-Scoper issue #1139

[9.6.30] - 2025-12-01

Changed

  • Updated list of deprecated PHP configuration settings for PHP 8.4, PHP 8.5, and PHP 8.6

[9.6.29] - 2025-09-24

  • No changes; phpunit.phar rebuilt with updated dependencies

[9.6.28] - 2025-09-23

  • No changes; phpunit.phar rebuilt with updated dependencies

[9.6.27] - 2025-09-14

Changed

  • #6366: Exclude __sleep() and __wakeup() from test double code generation on PHP >= 8.5

[9.6.26] - 2025-09-11

Changed

  • Implement __serialize() in addition to __sleep() (which will be deprecated in PHP 8.5)

[9.6.25] - 2025-08-20

Changed

  • Do not configure report_memleaks setting (which will be deprecated in PHP 8.5) for PHPT processes

[9.6.24] - 2025-08-10

... (truncated)

Commits
  • fea0625 Prepare release
  • 1a677f6 Merge branch '8.5' into 9.6
  • 1015741 Prepare release
  • 1cce5f3 Merge branch '8.5' into 9.6
  • 3141742 Do not run PHPT test when its temporary file for code coverage information ex...
  • 0b3170a We do not need to unserialize() objects here
  • 261086a Extract method
  • fdd6b86 Fix CS/WS issue
  • 492ee10 Prepare release
  • 81edce2 Merge branch '8.5' into 9.6
  • Additional commits viewable in compare view

Updates composer/composer from 2.10.1 to 2.11.1

Release notes

Sourced from composer/composer's releases.

2.11.1

  • Added a warning when the cache dir is on a Windows drive while running in WSL, as this makes filesystem operations very slow (#13175)
  • Fixed GitLab CI job tokens failing to authenticate against the GitLab Composer package registry, which requires HTTP Basic auth rather than the JOB-TOKEN header (#13180)
  • Fixed every update aborting with a SecurityException when a PHP extension reports a name that is not a valid platform package name (#13184)
  • Fixed require and remove dropping empty require/require-dev/repositories keys from composer.json when the command had not emptied them itself (#13178)
  • Fixed a PHP 8.6 deprecation warning from composer/ca-bundle (8bf8c27)
  • Fixed invalid custom-headers auth entries being sent as-is, they are now ignored with a warning (#13181)

2.11.0

Read the Composer 2.11 Release Announcement for more details on the release highlights.

Full Changelog

  • BC Break: Removed the source-fallback config option which was added in 2.10 as a temporary measure, dist installs no longer fall back to source (#13050)
  • Security: Fixed package names in vendor/composer/installed.json being able to escape the vendor directory during install and reinstall (GHSA-c968-33g3-wh7p)
  • Security: Fixed inline repository HTTP headers, such as API tokens, being written into composer.lock (GHSA-fm2w-xgf2-f9fh)
  • Security: Fixed additional arguments passed to @composer scripts not being escaped (#13169)
  • Security: Fixed svn passwords not being redacted from debug output (#13171)
  • Security: Sanitize URL-embedded credentials in hg and fossil error output (#13172)
  • Security: Reject TLS connections presenting distrusted intermediate certificates (the compromised eMudhra ones) even if the system CA store trusts their roots (#13146)
  • Security: Fixed bin proxies embedding package-controlled bin paths and shebangs unescaped, and bin paths containing shell metacharacters are now rejected (#13056)
  • Security: Fixed secure-http not catching insecure URLs that are not strictly valid or use git's <transport>::<address> syntax (#13144)
  • Security: Fixed repository options like custom http headers being sent along to dist URLs on other hosts whose name starts with the repository host (#13142)
  • Bumped composer-plugin-api to 2.11.0
  • Added a cooldown policy to withhold newly released package versions for a configurable period, reducing exposure to compromised releases (#12692, #13098, #13099, #13100, #13102, #13153)
  • Added block-scope option to custom policies so they can also block during install (#12990)
  • Added terminal progress/status reporting via OSC 7501 and OSC 9 escape sequences, which can be configured with COMPOSER_TERMINAL_STATUS (#13117)
  • Added --direct (-D) option to audit to only audit direct dependencies (#13121)
  • Added support for Bitbucket Cloud's new ssh.bitbucket.org SSH hostname, which is also used for the SSH fallback now (#13152)
  • Added strict-psr-autoloader config option, the equivalent of the --strict-psr-autoloader flag (#12893)
  • Added a warning when an optimized autoload dump contains paths only differing in casing (#13085)
  • Added only-branches option to VCS repositories to restrict which branches are loaded (#13086)
  • Added installed versions of sub-dependencies in show --tree --format=json output (#13049)
  • Added batching of security advisory API queries for projects with a very large number of dependencies (#13051)
  • Added support for 429 responses and Retry-After headers, Composer now waits and retries when a repository asks for it (#13082)
  • Added AI coding agent to the User-Agent (#13073, #13087)
  • Added a prompt in init to add composer.lock to .gitattributes with export-ignore when creating a library (#13127)
  • Improved dependency resolution performance and memory usage (#13071, #13072, #13103, #13123, #13124, #13132, #13174)
  • Improved performance by not requesting HTTP/3 anymore, which added a delay on every new connection with recent curl versions (#13096)
  • Improved performance of outdated and show --latest by loading package metadata in parallel (#13113)
  • Improved explanations for versions blocked by security advisories in dependency conflict errors (#13108, #13075)
  • Fixed the lock file not being flagged as outdated when the policy config changes - this will trigger a lock file change warning if you have a policy config defined (#13149)
  • Fixed install to fail when composer.lock has a content-hash merge conflict (#13105)
  • Fixed truncated zip downloads failing at extraction, they are now retried and never cached (#13094)
  • Fixed generated files (autoloader, composer.json, ...) being rewritten in place, which affected hardlinked copies and concurrent readers (#13069)
  • Fixed SSH URLs losing their user in git commands, causing auth failures since 2.10.3 (#13081)
  • Fixed GitLab CI job token authentication (#12916)
  • Fixed custom-headers from a project auth.json or COMPOSER_AUTH replacing the global ones instead of being merged (#13141)
  • Fixed parallel requests failing with "Invalid credentials" instead of retrying with credentials obtained by another request (#13135)
  • Fixed the GitHub API rate limit not being reported when the clone fallback fails (#13059)

... (truncated)

Changelog

Sourced from composer/composer's changelog.

[2.11.1] 2026-10-30

  • Added a warning when the cache dir is on a Windows drive while running in WSL, as this makes filesystem operations very slow (#13175)
  • Fixed GitLab CI job tokens failing to authenticate against the GitLab Composer package registry, which requires HTTP Basic auth rather than the JOB-TOKEN header (#13180)
  • Fixed every update aborting with a SecurityException when a PHP extension reports a name that is not a valid platform package name (#13184)
  • Fixed require and remove dropping empty require/require-dev/repositories keys from composer.json when the command had not emptied them itself (#13178)
  • Fixed a PHP 8.6 deprecation warning from composer/ca-bundle (8bf8c27)
  • Fixed invalid custom-headers auth entries being sent as-is, they are now ignored with a warning (#13181)

[2.11.0] 2026-10-29

  • Security: Fixed package names in vendor/composer/installed.json being able to escape the vendor directory during install and reinstall (GHSA-c968-33g3-wh7p)
  • Security: Fixed inline repository HTTP headers, such as API tokens, being written into composer.lock (GHSA-fm2w-xgf2-f9fh)
  • Security: Fixed additional arguments passed to @composer scripts not being escaped (#13169)
  • Security: Fixed svn passwords not being redacted from debug output (#13171)
  • Security: Sanitize URL-embedded credentials in hg and fossil error output (#13172)
  • Improved dependency resolution performance and memory usage (#13174)
  • Fixed config corrupting composer.json when modifying extra or scripts entries which are JSON arrays (#13167)
  • Fixed archives not being unwrapped correctly when OS/editor metadata entries like __MACOSX or Thumbs.db sit next to the package's top-level dir (#13168)
  • Fixed @script references with quoted arguments being split on spaces when passed to @composer scripts (#13169)

[2.11.0-RC1] 2026-10-22

  • BC Break: Removed the source-fallback config option which was added in 2.10 as a temporary measure, dist installs no longer fall back to source (#13050)
  • Security: Reject TLS connections presenting distrusted intermediate certificates (the compromised eMudhra ones) even if the system CA store trusts their roots (#13146)
  • Security: Fixed bin proxies embedding package-controlled bin paths and shebangs unescaped, and bin paths containing shell metacharacters are now rejected (#13056)
  • Security: Fixed secure-http not catching insecure URLs that are not strictly valid or use git's <transport>::<address> syntax (#13144)
  • Security: Fixed repository options like custom http headers being sent along to dist URLs on other hosts whose name starts with the repository host (#13142)
  • Bumped composer-plugin-api to 2.11.0
  • Added a cooldown policy to withhold newly released package versions for a configurable period, reducing exposure to compromised releases (#12692, #13098, #13099, #13100, #13102, #13153)
  • Added block-scope option to custom policies so they can also block during install (#12990)
  • Added terminal progress/status reporting via OSC 7501 and OSC 9 escape sequences, which can be configured with COMPOSER_TERMINAL_STATUS (#13117)
  • Added --direct (-D) option to audit to only audit direct dependencies (#13121)
  • Added support for Bitbucket Cloud's new ssh.bitbucket.org SSH hostname, which is also used for the SSH fallback now (#13152)
  • Added strict-psr-autoloader config option, the equivalent of the --strict-psr-autoloader flag (#12893)
  • Added a warning when an optimized autoload dump contains paths only differing in casing (#13085)
  • Added only-branches option to VCS repositories to restrict which branches are loaded (#13086)
  • Added installed versions of sub-dependencies in show --tree --format=json output (#13049)
  • Added batching of security advisory API queries for projects with a very large number of dependencies (#13051)
  • Added support for 429 responses and Retry-After headers, Composer now waits and retries when a repository asks for it (#13082)
  • Added AI coding agent to the User-Agent (#13073, #13087)
  • Added a prompt in init to add composer.lock to .gitattributes with export-ignore when creating a library (#13127)
  • Improved dependency resolution performance and memory usage (#13071, #13072, #13103, #13123, #13124, #13132)
  • Improved performance by not requesting HTTP/3 anymore, which added a delay on every new connection with recent curl versions (#13096)
  • Improved performance of outdated and show --latest by loading package metadata in parallel (#13113)
  • Improved explanations for versions blocked by security advisories in dependency conflict errors (#13108, #13075)
  • Fixed the lock file not being flagged as outdated when the policy config changes - this will trigger a lock file change warning if you have a policy config defined (#13149)
  • Fixed install to fail when composer.lock has a content-hash merge conflict (#13105)
  • Fixed truncated zip downloads failing at extraction, they are now retried and never cached (#13094)
  • Fixed generated files (autoloader, composer.json, ...) being rewritten in place, which affected hardlinked copies and concurrent readers (#13069)

... (truncated)

Commits
  • 472b418 Release 2.11.1
  • 6970633 Update changelog
  • 717168c Update deps
  • 8bf8c27 Update ca-bundle to fix a php 8.6 deprecation
  • 4bdf0df Warn when the cache dir is on a Windows drive while running in WSL (#13175)
  • 77e5f1b Keep empty link and repositories keys unless a removal emptied them (#13178)
  • 58faf0d Skip package validation for platform packages from the PlatformRepository (#1...
  • ffd9bd7 Refactor AuthHelper::addAuthenticationOptions() (#13181)
  • 6ec7071 Revert back to HTTP Basic Auth for GitLab Package registry (#13180)
  • 24dfd2d Reverting release version changes
  • Additional commits viewable in compare view

Updates league/flysystem from 3.29.1 to 3.36.0

Changelog

Sourced from league/flysystem's changelog.

3.36.0 - 2026-09-02

  • [SFTP V3] Support multiple fingerprints for zero-downtime fingerprint changes.
  • [FTP] Unset connection when resolving the root failed.

3.35.3 - 2026-08-22

  • [Filesystem] Report broken utf-8 as corrupted path

3.35.2 - 2026-07-06

  • [AwsS3V3] Let ACL config take precedence over visibility during copy (#1905)

3.35.1 - 2026-06-25

  • [AwsS3V3] Remove lock file from artefact.

3.35.0 - 2026-06-22

  • [Filesystem] Guard against null mime-type return at Filesystem level (#1901)

3.34.0 - 2026-05-26

Added

  • [Filesystem] Add ability to disable relative path resolution inside the configured root path.

3.33.0 - 2026-03-25

Changes

  • [SFTP V3] Add support for multiple fingerprints (#1893)

3.32.0 - 2026-02-25

Changes

  • [AwsS3V3] Allow SSE-C options when fetching file metadata

3.31.0 - 2026-01-23

Changes

  • [AsyncAwsS3] Allow V3

3.30.2 - 2025-11-10

Fixes

  • [Local] Clear last error for rename and copy operations (#1883)

... (truncated)

Commits
  • f7fb152 Prep changelog
  • 7b51e82 Merge branch 'bdtripp-fix/ftp-root-null' into 3.x
  • aeda031 Fixed borked merge
  • d8cd3e2 Merge branch '3.x' into fix/ftp-root-null
  • c8fa31b Merge pull request #1908 from ghazalfaraj/3.x
  • f749c94 Add multiple fingerprint formats
  • 5fc8404 Corrected release date
  • 3f44b99 Prpe changelog for release
  • ef4a9a5 Report broken utf-8 as a corrupted path.
  • 7c4259b Update github actions managed by me.
  • Additional commits viewable in compare view

Updates phpcsstandards/phpcsutils from 1.1.3 to 1.2.3

Release notes

Sourced from phpcsstandards/phpcsutils's releases.

1.2.3 - 2026-07-27

This is a security release and all users are advised to update their install(s) as soon as possible.

Changed

Other

  • Various housekeeping.

Fixed

Abstract Sniffs

  • SECURITY FIX: Running a sniff which uses the AbstractArrayDeclarationSniff::getActualArrayKey() method over untrusted PHP code, for example, in a CI pipeline that lints pull requests, or on a developer machine reviewing third-party code, could lead to arbitrary command execution on the scanning host. #774 For more details, see the security advisory. Thanks go to @​rodrigoprimo for responsibly disclosing the vulnerability.
  • The AbstractArrayDeclarationSniff::getActualArrayKey() method now handles exceptions seen when evaluating array keys more gracefully. #775

Utils

  • The Arrays::getDoubleArrowPtr() method did not recognize that, while rare, an array key can contain a (nested) array. #771

1.2.2 - 2025-12-08

Added

PHPCS Backcompat

  • BCTokens::castTokens(): sync with PHPCS 4.0.2 - added the T_VOID_CAST token (when available). #742

Changed

Utils

  • FunctionDeclarations::getProperties(): more defensive coding against parse errors/live coding. #740

Other

  • Various housekeeping.

1.2.1 - 2025-11-17

Fixed

Abstract Sniffs

  • The AbstractArrayDeclarationSniff::getActualArrayKey() method could cause deprecation notices and even fatal errors, when a PHPCS scan would be run on a different PHP version than the "code under scan" is targeting and the "code under scan" contained deprecated/removed type casts. #733

1.2.0 - 2025-11-11

Added

... (truncated)

Changelog

Sourced from phpcsstandards/phpcsutils's changelog.

[1.2.3] - 2026-07-27

This is a security release and all users are advised to update their install(s) as soon as possible.

Changed

Other

  • Various housekeeping.

Fixed

Abstract Sniffs

  • SECURITY FIX: Running a sniff which uses the AbstractArrayDeclarationSniff::getActualArrayKey() method over untrusted PHP code, for example, in a CI pipeline that lints pull requests, or on a developer machine reviewing third-party code, could lead to arbitrary command execution on the scanning host. #774 For more details, see the security advisory. Thanks go to [@​rodrigoprimo] for responsibly disclosing the vulnerability.
  • The AbstractArrayDeclarationSniff::getActualArrayKey() method now handles exceptions seen when evaluating array keys more gracefully. #775

Utils

  • The Arrays::getDoubleArrowPtr() method did not recognize that, while rare, an array key can contain a (nested) array. #771

#771: PHPCSStandards/PHPCSUtils#771 #774: PHPCSStandards/PHPCSUtils#774 #775: PHPCSStandards/PHPCSUtils#775

[1.2.2] - 2025-12-08

Added

PHPCS Backcompat

  • BCTokens::castTokens(): sync with PHPCS 4.0.2 - added the T_VOID_CAST token (when available). #742

Changed

Utils

  • FunctionDeclarations::getProperties(): more defensive coding against parse errors/live coding. #740

Other

  • Various housekeeping.

#740: PHPCSStandards/PHPCSUtils#740 #742: PHPCSStandards/PHPCSUtils#742

... (truncated)

Commits
  • 5f35d94 Merge pull request #778 from PHPCSStandards/develop
  • 6a72cf8 Merge pull request #777 from PHPCSStandards/feature/changelog-1.2.3
  • d3ef062 Changelog for PHPCSUtils 1.2.3
  • f1bb4ee Merge pull request #776 from PHPCSStandards/feature/remark-config-update
  • 33328b4 Remark: selectively skip URL patterns [update]
  • 533d077 Merge pull request #775 from PHPCSStandards/feature/abstractarraydeclarations...
  • 9f596b5 AbstractArrayDeclarationSniff::getActualArrayKey(): catch catchable exceptions
  • 90dab1d Merge pull request #774 from PHPCSStandards/security/CVE-2026-65954-getactual...
  • e864863 AbstractArrayDeclarationSniff::getActualArrayKey(): prevent executing arbitra...
  • 85990cb Merge pull request #773 from PHPCSStandards/feature/ghactions-setup-php-fail-...
  • Additional commits viewable in compare view

Updates squizlabs/php_codesniffer from 3.13.5 to 3.13.6

Release notes

Sourced from squizlabs/php_codesniffer's releases.

3.13.6 - 2026-08-06

This is a security release and all users are advised to update their install(s) as soon as possible.

Changed

Fixed

  • SECURITY FIX: Running PHP_CodeSniffer over untrusted files, for example, in a CI pipeline that scans pull requests, or on a developer machine reviewing third-party code, could result in attacker-controlled shell commands being executed when the Gitblame, Hgblame or Svnblame report(s) would process a file whose name contains shell metacharacters. #1473

Other

  • The GPG signature for the PHAR files has been rotated. The new fingerprint is: 5CB4F778BF9BC4FB67AE511D96E91A992CF22FF4.

Statistics

Closed: 0 issues Merged: 46 pull requests

Follow @​phpcs on Mastodon or @​PHP_CodeSniffer on X to stay informed.

Please consider funding the PHP_CodeSniffer project. If you already do so: thank you!

Changelog

Sourced from squizlabs/php_codesniffer's changelog.

[3.13.6] - 2026-08-06

This is a security release and all users are advised to update their install(s) as soon as possible.

Changed

  • Various housekeeping, including improvements to the tests and documentation.
    • Thanks to [Sergei Morozov][@​morozov] and [Juliette Reinders Folmer][@​jrfnl] for their contributions.

Fixed

  • SECURITY FIX: Running PHP_CodeSniffer over untrusted files, for example, in a CI pipeline that scans pull requests, or on a developer machine reviewing third-party code, could result in attacker-controlled shell commands being executed when the Gitblame, Hgblame or Svnblame report(s) would process a file whose name contains shell metacharacters. #1473
    • Users using the default Full report, or any of the other non-*blame reports, are not affected.
    • For more details, see the security advisory.
    • Thanks go to [Faze-up][@​Faze-up] and [Volker Dusch][@​edorian] for responsibly disclosing the vulnerability.
    • Additionally, thanks go to [Volker Dusch][@​edorian], [Rodrigo Primo][@​rodrigoprimo], [Dan Wallis][@​fredden] and [Juliette Reinders Folmer][@​jrfnl] for creating and testing the fix.

Other

  • The GPG signature for the PHAR files has been rotated. The new fingerprint is: 5CB4F778BF9BC4FB67AE511D96E91A992CF22FF4.

#1473: PHPCSStandards/PHP_CodeSniffer#1473

Commits
  • 4c378e1 Merge pull request #1474 from PHPCSStandards/feature/changelog-3.13.6
  • ddbf849 Merge pull request #1473 from PHPCSStandards/security/cve-2026-67434
  • 742a068 Changelog for the 3.13.6 release
  • 7a3a6bb Reports/*blame: properly escape file name
  • b5ce04f Merge pull request #1470 from PHPCSStandards/dependabot/github_actions/3.x/ac...
  • 5f72703 GH Actions: Bump the action-runners group with 2 updates
  • 20d0f55 Merge pull request #1466 from PHPCSStandards/dependabot/github_actions/3.x/ac...
  • 2a2ac29 Merge pull request #1469 from PHPCSStandards/feature/ghactions-setup-php-fail...
  • 6df695f Merge pull request #1467 from PHPCSStandards/dependabot/github_actions/3.x/ac...
  • 4da0184 GH Actions: fail "setup-php" if requested tooling could not be installed
  • Additional commits viewable in compare view

Updates wp-coding-standards/wpcs from 3.1.0 to 3.4.1

Release notes

Sourced from wp-coding-standards/wpcs's releases.

3.4.1 - 2026-07-27

This is a security release and all users are advised to update their WordPressCS install as soon as possible.

Changed

  • The minimum required PHPCSUtils version to 1.2.3 (was 1.2.2). #2770
  • The minimum required PHPCSExtra version to 1.5.1 (was 1.5.0). #2770
  • Various housekeeping, including documentation improvements.

Fixed

  • SECURITY FIX: Running the WordPress.WP.EnqueuedResourceParameters sniff over untrusted PHP code, for example, in a CI pipeline that lints pull requests, or on a developer machine reviewing third-party code, could lead to arbitrary command execution on the scanning host. #2771 This affects users of the WordPress and WordPress-Extra rulesets. The WordPress-Core ruleset and the WordPress-Docs ruleset are not affected. For more details, see the security advisory Thanks to @​FORIMOC for responsibly disclosing the vulnerability.

3.4.0

We're happy to welcome @​rodrigoprimo as co-maintainer of WordPressCS as of this release.

Added

Changed

  • The minimum required PHP_CodeSniffer version to 3.13.5 (was 3.13.4). #2761
  • The minimum required PHPCSUtils version to 1.2.2 (was 1.1.0). #2761
  • The default value for minimum_wp_version, as used by a number of sniffs detecting usage of deprecated WP features, has been updated to 6.7. #2757
  • WordPress.NamingConventions.PrefixAllGlobals has been updated to recognize pluggable functions introduced in WP up to WP 7.0.0. #2747
  • WordPress.WP.ClassNameCase has been updated to recognize classes introduced in WP up to WP 7.0.0. #2747
  • WordPress.WP.DeprecatedFunctions now detects functions deprecated in WordPress up to WP 7.0.0. #2747
  • The ConstantsHelper::is_use_of_global_constant() method will no longer flag a constant alias created via an import use statement as it were the use of a global constant. #2579
  • The ConstantsHelper::is_in_function_call() method will now act fully case-agnostic for the function names being checked. #2706 Previously, the $valid_functions parameter would need to be passed with the function names as keys in lowercase.
  • WordPress.PHP.NoSilencedErrors: error silencing is no longer accepted for the parse_url() function. #2701
  • Improved the wording of the error message for WordPress.Arrays.ArrayDeclarationSpacing.AssociativeArrayFound. #2688
  • Improved the wording of the error message for WordPress.PHP.RestrictedPHPFunctions. #2702
  • Various housekeeping, including documentation and test improvements. Includes a contribution by @​dd32.

Deprecated

  • WordPress.Arrays.ArrayDeclarationSpacing: the allow_single_item_single_line_associative_arrays property has been deprecated in favor of the new allow_single_item_single_line_explicit_key_arrays property. #2696 This is a name change only. The functionality of these properties is the same.

Fixed

  • WordPress.DB.PreparedSQL and WordPress.DB.PreparedSQLPlaceholders: false positive for static method calls to a non-global class named wpdb. #2753
  • WordPress.Security.EscapeOutput: false positive for get_search_query() when the $escaped parameter was passed as fully qualified or non-lowercase true. #2618
  • WordPress.Security.EscapeOutput: false negative for _deprecated_file() calls when the basename( __FILE__ ) pattern used non-standard casing for either basename() and/or __FILE__. #2729
  • WordPress.WP.AlternativeFunctions: false negative when class functions/constants/properties use the same name as select global WP constants/functions. #2617
  • WordPress.WP.AlternativeFunctions: false positive for fully qualified references to the global PHP stream constants \STDIN, \STDOUT, and \STDERR. #2617
  • WordPress.WP.CronInterval: false positive when the callback function reference used a different case than the function declaration, even though they are in the same file. #2730

3.3.0

... (truncated)

Changelog

Sourced from wp-coding-standards/wpcs's changelog.

[3.4.1] - 2026-07-27

This is a security release and all users are advised to update their WordPressCS install as soon as possible.

Changed

  • The minimum required PHPCSUtils version to 1.2.3 (was 1.2.2). #2770
  • The minimum required PHPCSExtra version to 1.5.1 (was 1.5.0). #2770
  • Various housekeeping, including documentation improvements.

Fixed

  • SECURITY FIX: Running the WordPress.WP.EnqueuedResourceParameters sniff over untrusted PHP code, for example, in a CI pipeline that lints pull requests, or on a developer machine reviewing third-party code, could lead to arbitrary command execution on the scanning host. #2771 This affects users of the WordPress and WordPress-Extra rulesets. The WordPress-Core ruleset and the WordPress-Docs ruleset are not affected. For more details, see the security advisory. Thanks to [@​FORIMOC] for responsibly disclosing the vulnerability.

#2770: WordPress/WordPress-Coding-Standards#2770 #2771: WordPress/WordPress-Coding-Standards#2771

[3.4.0] - 2026-07-16

We're happy to welcome [@​rodrigoprimo] as co-maintainer of WordPressCS as of this release.

Added

Bumps the composer group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit) | `9.6.22` | `9.6.33` |
| [composer/composer](https://github.com/composer/composer) | `2.10.1` | `2.11.1` |
| [league/flysystem](https://github.com/thephpleague/flysystem) | `3.29.1` | `3.36.0` |
| [phpcsstandards/phpcsutils](https://github.com/PHPCSStandards/PHPCSUtils) | `1.1.3` | `1.2.3` |
| [squizlabs/php_codesniffer](https://github.com/PHPCSStandards/PHP_CodeSniffer) | `3.13.5` | `3.13.6` |
| [wp-coding-standards/wpcs](https://github.com/WordPress/WordPress-Coding-Standards) | `3.1.0` | `3.4.1` |



Updates `phpunit/phpunit` from 9.6.22 to 9.6.33
- [Release notes](https://github.com/sebastianbergmann/phpunit/releases)
- [Changelog](https://github.com/sebastianbergmann/phpunit/blob/9.6.33/ChangeLog-9.6.md)
- [Commits](sebastianbergmann/phpunit@9.6.22...9.6.33)

Updates `composer/composer` from 2.10.1 to 2.11.1
- [Release notes](https://github.com/composer/composer/releases)
- [Changelog](https://github.com/composer/composer/blob/main/CHANGELOG.md)
- [Commits](composer/composer@2.10.1...2.11.1)

Updates `league/flysystem` from 3.29.1 to 3.36.0
- [Release notes](https://github.com/thephpleague/flysystem/releases)
- [Changelog](https://github.com/thephpleague/flysystem/blob/3.x/CHANGELOG.md)
- [Commits](thephpleague/flysystem@3.29.1...3.36.0)

Updates `phpcsstandards/phpcsutils` from 1.1.3 to 1.2.3
- [Release notes](https://github.com/PHPCSStandards/PHPCSUtils/releases)
- [Changelog](https://github.com/PHPCSStandards/PHPCSUtils/blob/develop/CHANGELOG.md)
- [Commits](PHPCSStandards/PHPCSUtils@1.1.3...1.2.3)

Updates `squizlabs/php_codesniffer` from 3.13.5 to 3.13.6
- [Release notes](https://github.com/PHPCSStandards/PHP_CodeSniffer/releases)
- [Changelog](https://github.com/PHPCSStandards/PHP_CodeSniffer/blob/4.x/CHANGELOG-3.x.md)
- [Commits](PHPCSStandards/PHP_CodeSniffer@3.13.5...3.13.6)

Updates `wp-coding-standards/wpcs` from 3.1.0 to 3.4.1
- [Release notes](https://github.com/WordPress/WordPress-Coding-Standards/releases)
- [Changelog](https://github.com/WordPress/WordPress-Coding-Standards/blob/develop/CHANGELOG.md)
- [Commits](WordPress/WordPress-Coding-Standards@3.1.0...3.4.1)

---
updated-dependencies:
- dependency-name: phpunit/phpunit
  dependency-version: 9.6.33
  dependency-type: direct:development
  dependency-group: composer
- dependency-name: composer/composer
  dependency-version: 2.11.1
  dependency-type: indirect
  dependency-group: composer
- dependency-name: league/flysystem
  dependency-version: 3.36.0
  dependency-type: indirect
  dependency-group: composer
- dependency-name: phpcsstandards/phpcsutils
  dependency-version: 1.2.3
  dependency-type: indirect
  dependency-group: composer
- dependency-name: squizlabs/php_codesniffer
  dependency-version: 3.13.6
  dependency-type: indirect
  dependency-group: composer
- dependency-name: wp-coding-standards/wpcs
  dependency-version: 3.4.1
  dependency-type: indirect
  dependency-group: composer
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file php Pull requests that update Php code labels Nov 9, 2026
@felipeelia felipeelia added this to the 5.3.6 milestone Nov 9, 2026
@felipeelia
felipeelia merged commit 590c16e into develop Nov 9, 2026
31 of 43 checks passed
@felipeelia
felipeelia deleted the dependabot/composer/composer-f3fcfad3fb branch November 9, 2026 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file php Pull requests that update Php code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant