-
Bug
-
Resolution: Fixed
-
Major
-
3.3.16
-
None
The composer command used to update some components to work on PHP 8 test environments is now broken because of composer rejecting some dependencies for security issues.
Running composer update symfony/yaml misantron/dbunit phpunit/phpunit doctrine/instantiator --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires symfony/yaml ~4.4, found symfony/yaml[v4.4.0, ..., v4.4.45] but these were not loaded, because they are affected by security advisories ("PKSA-v5yj-8nmz-sk2q", "PKSA-ft77-7h5f-p3r6", "PKSA-b14r-zh1d-vdrc"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
Problem 2 - Root composer.json requires misantron/dbunit ~5.0 -> satisfiable by misantron/dbunit[5.0.0, ..., 5.4.0].
- misantron/dbunit 5.0.0 requires phpunit/phpunit ^8.2 -> found phpunit/phpunit[8.2.0, ..., 8.5.52] but it conflicts with your root composer.json require (^9.3).
- misantron/dbunit 5.1.0 requires symfony/yaml ^4.4|^5.0 -> found symfony/yaml[v4.4.0, ..., v4.4.45, v5.0.0, ..., v5.4.52] but these were not loaded, because they are affected by security advisories ("PKSA-v5yj-8nmz-sk2q", "PKSA-ft77-7h5f-p3r6", "PKSA-b14r-zh1d-vdrc"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
- misantron/dbunit 5.2.0 requires symfony/yaml ^4.4 || ^5.0 -> found symfony/yaml[v4.4.0, ..., v4.4.45, v5.0.0, ..., v5.4.52] but these were not loaded, because they are affected by security advisories ("PKSA-v5yj-8nmz-sk2q", "PKSA-ft77-7h5f-p3r6", "PKSA-b14r-zh1d-vdrc"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
- misantron/dbunit 5.2.1 requires symfony/yaml ^4.4 || ^5.0 || ^6.0 -> found symfony/yaml[v4.4.0, ..., v4.4.45, v5.0.0, ..., v5.4.52, v6.0.0, ..., v6.4.40] but these were not loaded, because they are affected by security advisories ("PKSA-v5yj-8nmz-sk2q", "PKSA-ft77-7h5f-p3r6", "PKSA-b14r-zh1d-vdrc"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
- misantron/dbunit 5.3.0 requires symfony/yaml ^5.4 || ^6.0 -> found symfony/yaml[v5.4.0, ..., v5.4.52, v6.0.0, ..., v6.4.40] but it conflicts with your root composer.json require (~4.4).
- misantron/dbunit 5.4.0 requires symfony/yaml ^5.4 || ^6.4 || ^7.0 -> found symfony/yaml[v5.4.0, ..., v5.4.52, v6.4.0, ..., v6.4.40, v7.0.0, ..., v7.4.12] but it conflicts with your root composer.json require (~4.4).

