Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires laravel/framework 11.* -> satisfiable by laravel/framework[11.x-dev]. - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest]. - roave/security-advisories dev-latest conflicts with illuminate/mail >=9,<12.60|>=13,<13.10 (laravel/framework 11.x-dev replaces illuminate/mail self.version). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^11.0 -> satisfiable by orchestra/testbench[v11.0.0, v11.1.0, v11.2.0, 11.x-dev]. - Root composer.json requires spatie/phpunit-snapshot-assertions ^4.2 -> satisfiable by spatie/phpunit-snapshot-assertions[4.2.0, ..., v4.x-dev]. - orchestra/testbench v11.0.0 requires orchestra/workbench ^11.0.0 -> satisfiable by orchestra/workbench[v11.0.0, ..., 11.x-dev]. - orchestra/testbench v11.1.0 requires orchestra/workbench ^11.0.1 -> satisfiable by orchestra/workbench[v11.0.1, v11.1.0, v11.2.0, 11.x-dev]. - orchestra/testbench[v11.2.0, ..., 11.x-dev] require orchestra/workbench ^11.2.0 -> satisfiable by orchestra/workbench[v11.2.0, 11.x-dev]. - orchestra/workbench[v11.0.0, ..., 11.x-dev] require nunomaduro/collision ^8.9 -> satisfiable by nunomaduro/collision[v8.9.0, ..., v8.x-dev]. - Conclusion: don't install nunomaduro/collision v8.x-dev (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.0 (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.1 (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.3 (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.4 (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.5 (conflict analysis result) Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^11.0 -> satisfiable by orchestra/testbench[v11.0.0, v11.1.0, v11.2.0, 11.x-dev]. - Root composer.json requires spatie/phpunit-snapshot-assertions ^4.2 -> satisfiable by spatie/phpunit-snapshot-assertions[4.2.0, ..., v4.x-dev]. - orchestra/testbench v11.0.0 requires orchestra/workbench ^11.0.0 -> satisfiable by orchestra/workbench[v11.0.0, ..., 11.x-dev]. - orchestra/testbench v11.1.0 requires orchestra/workbench ^11.0.1 -> satisfiable by orchestra/workbench[v11.0.1, v11.1.0, v11.2.0, 11.x-dev]. - orchestra/testbench[v11.2.0, ..., 11.x-dev] require orchestra/workbench ^11.2.0 -> satisfiable by orchestra/workbench[v11.2.0, 11.x-dev]. - orchestra/workbench[v11.0.0, ..., 11.x-dev] require nunomaduro/collision ^8.9 -> satisfiable by nunomaduro/collision[v8.9.0, ..., v8.x-dev]. - Conclusion: don't install nunomaduro/collision v8.x-dev (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.0 (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.1 (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.2 (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.4 (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.5 (conflict analysis result) Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires laravel/framework 12.* -> satisfiable by laravel/framework[v12.61.1, ..., 12.x-dev]. - Root composer.json requires nunomaduro/collision ^6.0 || ^7.0 || ^8.0 -> satisfiable by nunomaduro/collision[v6.0.0, ..., v6.x-dev, v7.0.0, ..., v7.x-dev, v8.0.0, ..., v8.x-dev]. - Root composer.json requires orchestra/testbench ^10.0 -> satisfiable by orchestra/testbench[v10.0.0, ..., 10.x-dev]. - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest]. - Root composer.json requires spatie/phpunit-snapshot-assertions ^4.2 -> satisfiable by spatie/phpunit-snapshot-assertions[4.2.0, ..., v4.x-dev]. - laravel/framework 12.x-dev requires symfony/routing ^7.2.0 -> satisfiable by symfony/routing[7.2.x-dev, ..., 7.4.x-dev]. - nunomaduro/collision[v7.10.0, ..., v7.x-dev, v8.0.0, ..., v8.5.0] conflict with laravel/framework 12.x-dev. - nunomaduro/collision v8.x-dev conflicts with phpunit/phpunit <11.5.50 || >=14.0.0. - orchestra/testbench[v10.11.0, ..., 10.x-dev] require symfony/yaml ^7.2 -> satisfiable by symfony/yaml[7.2.x-dev, ..., 7.4.x-dev]. - roave/security-advisories dev-latest conflicts with symfony/routing 7.2.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 7.2.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 6.3.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 6.1.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 6.0.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 5.1.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 5.0.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 4.4.x-dev. - spatie/phpunit-snapshot-assertions[4.2.0, ..., 4.2.2] require php ^7.4 -> your php version (8.2.33) does not satisfy that requirement. - spatie/phpunit-snapshot-assertions[4.2.8, ..., 4.2.16] require symfony/yaml ^4.0|^5.0|^6.0 -> satisfiable by symfony/yaml[4.0.x-dev, ..., 4.4.x-dev, 5.0.x-dev, ..., 5.4.x-dev, 6.0.x-dev, ..., 6.4.x-dev]. - spatie/phpunit-snapshot-assertions[4.2.17, ..., v4.x-dev] require phpunit/phpunit ^8.3|^9.0 -> satisfiable by phpunit/phpunit[9.6.33, ..., 9.6.x-dev]. - spatie/phpunit-snapshot-assertions[4.2.3, ..., 4.2.7] require symfony/yaml ^4.0|^5.0 -> satisfiable by symfony/yaml[4.0.x-dev, ..., 4.4.x-dev, 5.0.x-dev, ..., 5.4.x-dev]. - symfony/routing[v7.4.13, ..., 7.4.x-dev] conflict with symfony/yaml v5.4.52. - symfony/yaml[4.0.x-dev, ..., 4.3.x-dev] require php ^7.1.3 -> your php version (8.2.33) does not satisfy that requirement. - Conclusion: don't install laravel/framework v12.61.1 (conflict analysis result) - Conclusion: don't install laravel/framework v12.62.0 (conflict analysis result) - Conclusion: don't install laravel/framework v12.63.0 (conflict analysis result) - Conclusion: don't install laravel/framework v12.64.0 (conflict analysis result) - Conclusion: don't install laravel/framework v12.65.0 (conflict analysis result) - Conclusion: don't install laravel/framework v12.66.0 (conflict analysis result) - Conclusion: don't install orchestra/testbench[v10.10.0] | install one of nunomaduro/collision[v7.10.0, v7.11.0, v7.12.0, v8.0.0, ..., v8.5.0], spatie/phpunit-snapshot-assertions[4.2.3, 4.2.5], symfony/yaml[v5.4.52], orchestra/testbench-core[10.x-dev] (conflict analysis result) - Conclusion: don't install orchestra/testbench[v10.9.0] | install one of nunomaduro/collision[v7.10.0, v7.11.0, v7.12.0, v8.0.0, ..., v8.5.0], spatie/phpunit-snapshot-assertions[4.2.3, 4.2.5], symfony/yaml[v5.4.52], orchestra/testbench-core[10.x-dev] (conflict analysis result) - Conclusion: don't install orchestra/testbench[v10.8.0] | install one of nunomaduro/collision[v7.10.0, v7.11.0, v7.12.0, v8.0.0, ..., v8.5.0], spatie/phpunit-snapshot-assertions[4.2.3, 4.2.5],

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires ergebnis/php-cs-fixer-config ^5.0 -> satisfiable by ergebnis/php-cs-fixer-config[5.0.0, ..., 5.16.0]. - Root composer.json requires orchestra/testbench ^10.0 -> satisfiable by orchestra/testbench[v10.0.0, ..., 10.x-dev]. - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest]. - orchestra/testbench[v10.0.0, ..., 10.x-dev] require symfony/process ^7.2 -> satisfiable by symfony/process[v7.2.0-BETA1, ..., 7.4.x-dev]. - Conclusion: don't install symfony/process v7.4.13 (conflict analysis result) Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires laravel/framework 11.* -> satisfiable by laravel/framework[11.x-dev]. - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest]. - roave/security-advisories dev-latest conflicts with illuminate/mail >=9,<12.60|>=13,<13.10 (laravel/framework 11.x-dev replaces illuminate/mail self.version). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires laravel/framework 11.* -> satisfiable by laravel/framework[11.x-dev]. - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest]. - roave/security-advisories dev-latest conflicts with illuminate/mail >=9,<12.60|>=13,<13.10 (laravel/framework 11.x-dev replaces illuminate/mail self.version). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires ergebnis/php-cs-fixer-config ^5.0 -> satisfiable by ergebnis/php-cs-fixer-config[5.0.0, ..., 5.16.0]. - Root composer.json requires orchestra/testbench ^10.0 -> satisfiable by orchestra/testbench[v10.0.0, ..., 10.x-dev]. - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest]. - orchestra/testbench[v10.0.0, ..., 10.x-dev] require symfony/process ^7.2 -> satisfiable by symfony/process[v7.2.0-BETA1, ..., 7.4.x-dev]. - Conclusion: don't install symfony/process v7.4.13 (conflict analysis result) Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires laravel/framework 11.* -> satisfiable by laravel/framework[11.x-dev]. - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest]. - roave/security-advisories dev-latest conflicts with illuminate/mail >=9,<12.60|>=13,<13.10 (laravel/framework 11.x-dev replaces illuminate/mail self.version). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires laravel/framework 11.* -> satisfiable by laravel/framework[11.x-dev]. - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest]. - roave/security-advisories dev-latest conflicts with illuminate/mail >=9,<12.60|>=13,<13.10 (laravel/framework 11.x-dev replaces illuminate/mail self.version). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^11.0 -> satisfiable by orchestra/testbench[v11.0.0, v11.1.0, v11.2.0, 11.x-dev]. - Root composer.json requires spatie/phpunit-snapshot-assertions ^4.2 -> satisfiable by spatie/phpunit-snapshot-assertions[4.2.0, ..., v4.x-dev]. - orchestra/testbench v11.0.0 requires orchestra/workbench ^11.0.0 -> satisfiable by orchestra/workbench[v11.0.0, ..., 11.x-dev]. - orchestra/testbench v11.1.0 requires orchestra/workbench ^11.0.1 -> satisfiable by orchestra/workbench[v11.0.1, v11.1.0, v11.2.0, 11.x-dev]. - orchestra/testbench[v11.2.0, ..., 11.x-dev] require orchestra/workbench ^11.2.0 -> satisfiable by orchestra/workbench[v11.2.0, 11.x-dev]. - orchestra/workbench[v11.0.0, ..., 11.x-dev] require nunomaduro/collision ^8.9 -> satisfiable by nunomaduro/collision[v8.9.0, ..., v8.x-dev]. - Conclusion: don't install nunomaduro/collision v8.x-dev (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.0 (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.1 (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.2 (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.4 (conflict analysis result) - Conclusion: don't install nunomaduro/collision v8.9.5 (conflict analysis result) Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires ergebnis/php-cs-fixer-config ^5.0 -> satisfiable by ergebnis/php-cs-fixer-config[5.0.0, ..., 5.16.0]. - Root composer.json requires laravel/framework 13.* -> satisfiable by laravel/framework[13.0.x-dev (alias of dev-master), ..., 13.x-dev]. - ergebnis/php-cs-fixer-config 5.0.0 requires friendsofphp/php-cs-fixer ~3.13.0 -> satisfiable by friendsofphp/php-cs-fixer[v3.13.0, v3.13.1, v3.13.2]. - ergebnis/php-cs-fixer-config[5.0.1, ..., 5.9.2] require php ~8.0.0 || ~8.1.0 || ~8.2.0 -> your php version (8.3.33) does not satisfy that requirement. - ergebnis/php-cs-fixer-config[5.10.0, ..., 5.16.0] require php ~8.1.0 || ~8.2.0 -> your php version (8.3.33) does not satisfy that requirement. - friendsofphp/php-cs-fixer[v3.13.0, ..., v3.13.2] require symfony/console ^5.4 || ^6.0 -> satisfiable by symfony/console[v5.4.0-BETA1, ..., 5.4.x-dev, v6.0.0-BETA1, ..., 6.4.x-dev]. - laravel/framework 13.x-dev requires symfony/console ^7.4.0 || ^8.0.0 -> satisfiable by symfony/console[v7.4.0-BETA1, ..., 7.4.x-dev, v8.0.0-BETA1, ..., 8.2.x-dev]. - laravel/framework 13.x-dev requires symfony/http-kernel ^7.4.0 || ^8.0.0 -> satisfiable by symfony/http-kernel[v7.4.12, ..., 7.4.x-dev, v8.0.12, ..., 8.2.x-dev]. - laravel/framework[dev-master, 13.0.x-dev] require php ^8.4 -> your php version (8.3.33) does not satisfy that requirement. - symfony/console[v8.0.0-BETA1, ..., 8.0.x-dev] require php >=8.4 -> your php version (8.3.33) does not satisfy that requirement. - symfony/http-kernel[v8.0.12, ..., 8.0.x-dev] require php >=8.4 -> your php version (8.3.33) does not satisfy that requirement. - symfony/console[v8.1.0-BETA1, ..., 8.2.x-dev] require php >=8.4.1 -> your php version (8.3.33) does not satisfy that requirement. - symfony/http-kernel[v8.1.0-BETA1, ..., 8.2.x-dev] require php >=8.4.1 -> your php version (8.3.33) does not satisfy that requirement. - symfony/http-kernel[v7.4.12, ..., 7.4.x-dev] conflict with symfony/console <6.4. - symfony/http-kernel[v7.4.12, ..., 7.4.x-dev] conflict with symfony/console v5.4.47. - symfony/http-kernel[v7.4.12, ..., 7.4.x-dev] conflict with symfony/console v5.4.3. - symfony/http-kernel[v7.4.12, ..., 7.4.x-dev] conflict with symfony/console v5.4.0. - symfony/http-kernel[v7.4.12, ..., 7.4.x-dev] conflict with symfony/console v5.4.0-BETA1. - Conclusion: don't install laravel/framework v13.12.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.13.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.14.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.15.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.16.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.16.1 (conflict analysis result) - Conclusion: don't install laravel/framework v13.17.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.18.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.18.1 (conflict analysis result) - Conclusion: don't install laravel/framework v13.19.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.20.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.21.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.21.1 (conflict analysis result) - Conclusion: don't install laravel/framework v13.22.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.23.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.24.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.25.0 (conflict analysis result) - laravel/framework 13.0.x-dev is an alias of laravel/framework dev-master and thus requires it to be installed too. - You can only install one versio

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires ergebnis/php-cs-fixer-config ^5.0 -> satisfiable by ergebnis/php-cs-fixer-config[5.0.0, ..., 5.16.0]. - Root composer.json requires orchestra/testbench ^10.0 -> satisfiable by orchestra/testbench[v10.0.0, ..., 10.x-dev]. - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest]. - orchestra/testbench[v10.0.0, ..., 10.x-dev] require symfony/process ^7.2 -> satisfiable by symfony/process[v7.2.0-BETA1, ..., 7.4.x-dev]. - Conclusion: don't install symfony/process v7.4.13 (conflict analysis result) Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires ergebnis/php-cs-fixer-config ^5.0 -> satisfiable by ergebnis/php-cs-fixer-config[5.0.0, ..., 5.16.0]. - Root composer.json requires laravel/framework 13.* -> satisfiable by laravel/framework[13.0.x-dev (alias of dev-master), ..., 13.x-dev]. - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest]. - laravel/framework[v13.12.0, ..., 13.x-dev] require symfony/process ^7.4.5 || ^8.0.5 -> satisfiable by symfony/process[v7.4.5, ..., 7.4.x-dev, v8.0.5, ..., 8.2.x-dev]. - laravel/framework[dev-master, 13.0.x-dev] require php ^8.4 -> your php version (8.3.33) does not satisfy that requirement. - symfony/process[v8.0.5, ..., 8.0.x-dev] require php >=8.4 -> your php version (8.3.33) does not satisfy that requirement. - symfony/process[v8.1.0-BETA1, ..., 8.2.x-dev] require php >=8.4.1 -> your php version (8.3.33) does not satisfy that requirement. - Conclusion: don't install symfony/process v7.4.5 (conflict analysis result) - laravel/framework 13.0.x-dev is an alias of laravel/framework dev-master and thus requires it to be installed too. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires laravel/framework 11.* -> satisfiable by laravel/framework[11.x-dev]. - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest]. - roave/security-advisories dev-latest conflicts with illuminate/mail >=9,<12.60|>=13,<13.10 (laravel/framework 11.x-dev replaces illuminate/mail self.version). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires laravel/framework 12.* -> satisfiable by laravel/framework[v12.61.1, ..., 12.x-dev]. - Root composer.json requires nunomaduro/collision ^6.0 || ^7.0 || ^8.0 -> satisfiable by nunomaduro/collision[v6.0.0, ..., v6.x-dev, v7.0.0, ..., v7.x-dev, v8.0.0, ..., v8.x-dev]. - Root composer.json requires orchestra/testbench ^10.0 -> satisfiable by orchestra/testbench[v10.0.0, ..., 10.x-dev]. - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest]. - Root composer.json requires spatie/phpunit-snapshot-assertions ^4.2 -> satisfiable by spatie/phpunit-snapshot-assertions[4.2.0, ..., v4.x-dev]. - laravel/framework 12.x-dev requires symfony/routing ^7.2.0 -> satisfiable by symfony/routing[7.2.x-dev, ..., 7.4.x-dev]. - nunomaduro/collision[v7.10.0, ..., v7.x-dev, v8.0.0, ..., v8.5.0] conflict with laravel/framework 12.x-dev. - nunomaduro/collision v8.x-dev conflicts with phpunit/phpunit <11.5.50 || >=14.0.0. - orchestra/testbench[v10.11.0, ..., 10.x-dev] require symfony/yaml ^7.2 -> satisfiable by symfony/yaml[7.2.x-dev, ..., 7.4.x-dev]. - roave/security-advisories dev-latest conflicts with symfony/routing 7.2.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 7.2.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 6.3.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 6.1.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 6.0.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 5.1.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 5.0.x-dev. - roave/security-advisories dev-latest conflicts with symfony/yaml 4.4.x-dev. - spatie/phpunit-snapshot-assertions[4.2.0, ..., 4.2.2] require php ^7.4 -> your php version (8.5.8) does not satisfy that requirement. - spatie/phpunit-snapshot-assertions[4.2.8, ..., 4.2.16] require symfony/yaml ^4.0|^5.0|^6.0 -> satisfiable by symfony/yaml[4.0.x-dev, ..., 4.4.x-dev, 5.0.x-dev, ..., 5.4.x-dev, 6.0.x-dev, ..., 6.4.x-dev]. - spatie/phpunit-snapshot-assertions[4.2.17, ..., v4.x-dev] require phpunit/phpunit ^8.3|^9.0 -> satisfiable by phpunit/phpunit[9.6.33, ..., 9.6.x-dev]. - spatie/phpunit-snapshot-assertions[4.2.3, ..., 4.2.7] require symfony/yaml ^4.0|^5.0 -> satisfiable by symfony/yaml[4.0.x-dev, ..., 4.4.x-dev, 5.0.x-dev, ..., 5.4.x-dev]. - symfony/routing[v7.4.13, ..., 7.4.x-dev] conflict with symfony/yaml v5.4.52. - symfony/yaml[4.0.x-dev, ..., 4.3.x-dev] require php ^7.1.3 -> your php version (8.5.8) does not satisfy that requirement. - Conclusion: don't install laravel/framework v12.61.1 (conflict analysis result) - Conclusion: don't install laravel/framework v12.62.0 (conflict analysis result) - Conclusion: don't install laravel/framework v12.63.0 (conflict analysis result) - Conclusion: don't install laravel/framework v12.64.0 (conflict analysis result) - Conclusion: don't install laravel/framework v12.65.0 (conflict analysis result) - Conclusion: don't install laravel/framework v12.66.0 (conflict analysis result) - Conclusion: don't install orchestra/testbench[v10.10.0] | install one of nunomaduro/collision[v7.10.0, v7.11.0, v7.12.0, v8.0.0, ..., v8.5.0], spatie/phpunit-snapshot-assertions[4.2.3, 4.2.5], symfony/yaml[v5.4.52], orchestra/testbench-core[10.x-dev] (conflict analysis result) - Conclusion: don't install orchestra/testbench[v10.9.0] | install one of nunomaduro/collision[v7.10.0, v7.11.0, v7.12.0, v8.0.0, ..., v8.5.0], spatie/phpunit-snapshot-assertions[4.2.3, 4.2.5], symfony/yaml[v5.4.52], orchestra/testbench-core[10.x-dev] (conflict analysis result) - Conclusion: don't install orchestra/testbench[v10.8.0] | install one of nunomaduro/collision[v7.10.0, v7.11.0, v7.12.0, v8.0.0, ..., v8.5.0], spatie/phpunit-snapshot-assertions[4.2.3, 4.2.5], sy

The strategy configuration was canceled because "test._8_4_11___prefer-stable_u" failed

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires laravel/framework 11.* -> satisfiable by laravel/framework[11.x-dev]. - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest]. - roave/security-advisories dev-latest conflicts with illuminate/mail >=9,<12.60|>=13,<13.10 (laravel/framework 11.x-dev replaces illuminate/mail self.version). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v3, actions/checkout@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/