Update pestphp/pest requirement from ^2.20 to ^3.3 #51
Annotations
2 errors and 1 warning
Install dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires laravel/framework 10.* -> satisfiable by laravel/framework[v10.0.0, ..., 10.x-dev].
- Root composer.json requires orchestra/testbench ^7.0|8.22.3|^9.0 -> satisfiable by orchestra/testbench[v7.0.0, ..., 7.x-dev, v8.22.3, v9.0.0, ..., 9.x-dev].
- Root composer.json requires pestphp/pest ^3.3 -> satisfiable by pestphp/pest[v3.3.0, v3.3.1, v3.3.2, 3.x-dev].
- nunomaduro/collision[v8.4.0, ..., v8.x-dev] conflict with laravel/framework <11.0.0 || >=12.0.0.
- pestphp/pest[v3.3.0, ..., 3.x-dev] require nunomaduro/collision ^8.4.0 -> satisfiable by nunomaduro/collision[v8.4.0, v8.x-dev].
- Conclusion: don't install laravel/framework v10.0.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.0.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.0.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.0.3 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.1.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.1.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.1.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.1.3 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.1.4 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.1.5 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.2.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.3.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.3.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.3.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.3.3 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.4.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.4.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.5.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.5.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.6.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.6.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.6.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.7.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.7.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.8.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.9.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.10.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.10.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.11.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.12.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.13.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.13.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.13.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.13.3 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.13.5 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.14.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.14.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.15.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.16.0 (conflict analysis result)
- Conclusion: don't install laravel/fram
|
Install dependencies
Process completed with exit code 2.
|
Get composer cache directory
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Loading