Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest ^2.0 || ^3.0 || ^4.0 -> satisfiable by pestphp/pest[v2.0.1, ..., 2.x-dev, v3.0.0, ..., 3.x-dev, v4.0.0, ..., 4.x-dev]. - brianium/paratest[v7.9.0, ..., v7.11.2] require php ~8.3.0 || ~8.4.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.12.0, ..., v7.20.0] require php ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.21.0, ..., 7.x-dev] require php ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.4.0, ..., v7.5.7] require php ~8.2.0 || ~8.3.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.4.8, ..., v7.8.4] require php ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.8.5, ..., 7.8.x-dev] require php ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement. - pestphp/pest v2.33.3 requires brianium/paratest ^7.4.0 -> satisfiable by brianium/paratest[v7.4.0, ..., 7.x-dev]. - pestphp/pest v2.33.5 requires brianium/paratest ^7.4.1 -> satisfiable by brianium/paratest[v7.4.1, ..., 7.x-dev]. - pestphp/pest v2.34.3 requires brianium/paratest ^7.4.3 -> satisfiable by brianium/paratest[v7.4.3, ..., 7.x-dev]. - pestphp/pest v2.36.0 conflicts with phpunit/phpunit 10.5.64. - pestphp/pest v2.36.0 conflicts with phpunit/phpunit 10.5.63. - pestphp/pest v2.36.0 conflicts with phpunit/phpunit 10.5.62. - pestphp/pest v2.36.0 requires phpunit/phpunit ^10.5.36 -> satisfiable by phpunit/phpunit[10.5.62, 10.5.63, 10.5.64, 10.5.x-dev]. - pestphp/pest[v2.36.1, ..., 2.x-dev, v3.0.0, ..., 3.x-dev] require php ^8.2.0 -> your php version (8.1.34) does not satisfy that requirement. - pestphp/pest[v4.0.0, ..., 4.x-dev] require php ^8.3.0 -> your php version (8.1.34) does not satisfy that requirement. - Conclusion: don't install pestphp/pest v2.0.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.0.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.1.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.3.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.4.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.7.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.9.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.9.5 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.12.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.12.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.12.2 (conflict analysis result) - Conclusion: don

Process completed with exit code 1.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest ^2.0 || ^3.0 || ^4.0 -> satisfiable by pestphp/pest[v2.0.1, ..., 2.x-dev, v3.0.0, ..., 3.x-dev, v4.0.0, ..., 4.x-dev]. - brianium/paratest[v7.9.0, ..., v7.11.2] require php ~8.3.0 || ~8.4.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.12.0, ..., v7.20.0] require php ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.21.0, ..., 7.x-dev] require php ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.4.0, ..., v7.5.7] require php ~8.2.0 || ~8.3.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.4.8, ..., v7.8.4] require php ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.8.5, ..., 7.8.x-dev] require php ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement. - pestphp/pest v2.33.3 requires brianium/paratest ^7.4.0 -> satisfiable by brianium/paratest[v7.4.0, ..., 7.x-dev]. - pestphp/pest v2.33.5 requires brianium/paratest ^7.4.1 -> satisfiable by brianium/paratest[v7.4.1, ..., 7.x-dev]. - pestphp/pest v2.34.3 requires brianium/paratest ^7.4.3 -> satisfiable by brianium/paratest[v7.4.3, ..., 7.x-dev]. - pestphp/pest v2.36.0 conflicts with phpunit/phpunit >10.5.36. - pestphp/pest v2.36.0 requires phpunit/phpunit ^10.5.36 -> satisfiable by phpunit/phpunit[10.5.62, 10.5.63, 10.5.64, 10.5.x-dev]. - pestphp/pest[v2.36.1, ..., 2.x-dev, v3.0.0, ..., 3.x-dev] require php ^8.2.0 -> your php version (8.1.34) does not satisfy that requirement. - pestphp/pest[v4.0.0, ..., 4.x-dev] require php ^8.3.0 -> your php version (8.1.34) does not satisfy that requirement. - Conclusion: don't install pestphp/pest v2.0.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.0.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.1.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.3.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.4.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.7.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.9.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.9.5 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.12.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.12.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.12.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.13.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.14.1 (conflict analysis re

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest ^2.0 || ^3.0 || ^4.0 -> satisfiable by pestphp/pest[v2.0.1, ..., 2.x-dev, v3.0.0, ..., 3.x-dev, v4.0.0, ..., 4.x-dev]. - brianium/paratest[v7.9.0, ..., v7.11.2] require php ~8.3.0 || ~8.4.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.12.0, ..., v7.20.0] require php ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.21.0, ..., 7.x-dev] require php ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.4.0, ..., v7.5.7] require php ~8.2.0 || ~8.3.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.4.8, ..., v7.8.4] require php ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.8.5, ..., 7.8.x-dev] require php ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement. - pestphp/pest v2.33.3 requires brianium/paratest ^7.4.0 -> satisfiable by brianium/paratest[v7.4.0, ..., 7.x-dev]. - pestphp/pest v2.33.5 requires brianium/paratest ^7.4.1 -> satisfiable by brianium/paratest[v7.4.1, ..., 7.x-dev]. - pestphp/pest v2.34.3 requires brianium/paratest ^7.4.3 -> satisfiable by brianium/paratest[v7.4.3, ..., 7.x-dev]. - pestphp/pest v2.36.0 conflicts with phpunit/phpunit >10.5.36. - pestphp/pest v2.36.0 requires phpunit/phpunit ^10.5.36 -> satisfiable by phpunit/phpunit[10.5.62, 10.5.63, 10.5.64, 10.5.x-dev]. - pestphp/pest[v2.36.1, ..., 2.x-dev, v3.0.0, ..., 3.x-dev] require php ^8.2.0 -> your php version (8.1.34) does not satisfy that requirement. - pestphp/pest[v4.0.0, ..., 4.x-dev] require php ^8.3.0 -> your php version (8.1.34) does not satisfy that requirement. - Conclusion: don't install pestphp/pest v2.0.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.0.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.1.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.3.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.4.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.7.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.9.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.9.5 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.12.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.12.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.12.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.13.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.14.1 (conflict analysis re

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. 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@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. 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@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. 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@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. 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@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. 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@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. 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@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. 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@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. 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@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. 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@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. 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@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. 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@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. 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@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. 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@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/