Your requirements could not be resolved to an installable set of packages. Problem 1 - pestphp/pest-plugin-type-coverage[v2.0.0, ..., 2.x-dev] require php ^8.1 -> your php version (7.4.33) does not satisfy that requirement. - Root composer.json requires pestphp/pest-plugin-type-coverage ^1.0|^2.0 -> satisfiable by pestphp/pest-plugin-type-coverage[v2.0.0, ..., 2.x-dev].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - pestphp/pest-plugin-laravel[v1.3.0, ..., 1.x-dev] require pestphp/pest ^1.22.1 -> satisfiable by pestphp/pest[v1.22.1, ..., 1.x-dev]. - Conclusion: don't install pestphp/pest v1.22.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.22.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.22.4 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.22.5 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.22.6 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.23.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.23.1 (conflict analysis result) - pestphp/pest-plugin-laravel[v1.0.0, ..., v1.1.0] require laravel/framework ^7.0 || ^8.0 -> found laravel/framework[v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel v2.0.0 requires laravel/framework ^10.4.1 -> found laravel/framework[v10.4.1, ..., 10.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel v2.1.0 requires laravel/framework ^10.15.0 -> found laravel/framework[v10.15.0, ..., 10.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-type-coverage[v2.1.0, ..., 2.x-dev] require pestphp/pest-plugin ^2.1.1 -> satisfiable by pestphp/pest-plugin[v2.1.1, 2.x-dev]. - pestphp/pest-plugin-type-coverage v2.0.0 requires pestphp/pest-plugin ^2.0.1 -> satisfiable by pestphp/pest-plugin[v2.0.1, v2.1.0, v2.1.1, 2.x-dev]. - pestphp/pest-plugin[v2.0.1, ..., 2.x-dev] conflict with pestphp/pest <2.2.3. - pestphp/pest-plugin-laravel v1.2.0 requires pestphp/pest ^1.7 -> satisfiable by pestphp/pest[v1.7.0, ..., 1.x-dev]. - Conclusion: don't install pestphp/pest v1.11.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.12.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.17.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.21.1 (conflict analysis result) - Root composer.json requires pestphp/pest-plugin-laravel ^1.0|^2.0 -> satisfiable by pestphp/pest-plugin-laravel[v1.0.0, ..., 1.x-dev, v2.0.0, ..., 2.x-dev]. - Root composer.json requires pestphp/pest-plugin-type-coverage ^1.0|^2.0 -> satisfiable by pestphp/pest-plugin-type-coverage[v2.0.0, ..., 2.x-dev]. 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 - pestphp/pest-plugin-laravel[v1.3.0, ..., 1.x-dev] require pestphp/pest ^1.22.1 -> satisfiable by pestphp/pest[v1.22.1, ..., 1.x-dev]. - Conclusion: don't install pestphp/pest v1.22.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.22.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.22.4 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.22.5 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.22.6 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.23.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.23.1 (conflict analysis result) - pestphp/pest-plugin-laravel[v1.0.0, ..., v1.1.0] require laravel/framework ^7.0 || ^8.0 -> found laravel/framework[v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel v2.0.0 requires laravel/framework ^10.4.1 -> found laravel/framework[v10.4.1, ..., 10.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel v2.1.0 requires laravel/framework ^10.15.0 -> found laravel/framework[v10.15.0, ..., 10.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-type-coverage[v2.1.0, ..., 2.x-dev] require pestphp/pest-plugin ^2.1.1 -> satisfiable by pestphp/pest-plugin[v2.1.1, 2.x-dev]. - pestphp/pest-plugin-type-coverage v2.0.0 requires pestphp/pest-plugin ^2.0.1 -> satisfiable by pestphp/pest-plugin[v2.0.1, v2.1.0, v2.1.1, 2.x-dev]. - pestphp/pest-plugin[v2.0.1, ..., 2.x-dev] conflict with pestphp/pest <2.2.3. - pestphp/pest-plugin-laravel v1.2.0 requires pestphp/pest ^1.7 -> satisfiable by pestphp/pest[v1.7.0, ..., 1.x-dev]. - Conclusion: don't install pestphp/pest v1.11.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.12.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.17.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.21.1 (conflict analysis result) - Root composer.json requires pestphp/pest-plugin-laravel ^1.0|^2.0 -> satisfiable by pestphp/pest-plugin-laravel[v1.0.0, ..., 1.x-dev, v2.0.0, ..., 2.x-dev]. - Root composer.json requires pestphp/pest-plugin-type-coverage ^1.0|^2.0 -> satisfiable by pestphp/pest-plugin-type-coverage[v2.0.0, ..., 2.x-dev]. 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 - pestphp/pest-plugin-laravel[v1.3.0, ..., 1.x-dev] require pestphp/pest ^1.22.1 -> satisfiable by pestphp/pest[v1.22.1, ..., 1.x-dev]. - Conclusion: don't install pestphp/pest v1.22.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.22.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.22.4 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.22.5 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.22.6 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.23.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.23.1 (conflict analysis result) - pestphp/pest-plugin-laravel[v1.0.0, ..., v1.1.0] require laravel/framework ^7.0 || ^8.0 -> found laravel/framework[v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel v2.0.0 requires laravel/framework ^10.4.1 -> found laravel/framework[v10.4.1, ..., 10.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel v2.1.0 requires laravel/framework ^10.15.0 -> found laravel/framework[v10.15.0, ..., 10.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (9.*). - pestphp/pest-plugin-type-coverage[v2.1.0, ..., 2.x-dev] require pestphp/pest-plugin ^2.1.1 -> satisfiable by pestphp/pest-plugin[v2.1.1, 2.x-dev]. - pestphp/pest-plugin-type-coverage v2.0.0 requires pestphp/pest-plugin ^2.0.1 -> satisfiable by pestphp/pest-plugin[v2.0.1, v2.1.0, v2.1.1, 2.x-dev]. - pestphp/pest-plugin[v2.0.1, ..., 2.x-dev] conflict with pestphp/pest <2.2.3. - pestphp/pest-plugin-laravel v1.2.0 requires pestphp/pest ^1.7 -> satisfiable by pestphp/pest[v1.7.0, ..., 1.x-dev]. - Conclusion: don't install pestphp/pest v1.11.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.12.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.17.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v1.21.1 (conflict analysis result) - Root composer.json requires pestphp/pest-plugin-laravel ^1.0|^2.0 -> satisfiable by pestphp/pest-plugin-laravel[v1.0.0, ..., 1.x-dev, v2.0.0, ..., 2.x-dev]. - Root composer.json requires pestphp/pest-plugin-type-coverage ^1.0|^2.0 -> satisfiable by pestphp/pest-plugin-type-coverage[v2.0.0, ..., 2.x-dev]. 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 - pestphp/pest-plugin-type-coverage[v2.0.0, ..., 2.x-dev] require php ^8.1 -> your php version (8.0.30) does not satisfy that requirement. - Root composer.json requires pestphp/pest-plugin-type-coverage ^1.0|^2.0 -> satisfiable by pestphp/pest-plugin-type-coverage[v2.0.0, ..., 2.x-dev].

Process completed with exit code 2.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/