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 illuminate/support ^10.0|^11.0 -> satisfiable by illuminate/support[v10.0.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev], laravel/framework[v10.26.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev].
- Root composer.json requires livewire/livewire ^2.11|^3.3.5 -> satisfiable by livewire/livewire[v2.11.0].
- 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 10.x-dev.
- 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.26.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.26.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.26.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.27.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.28.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.29.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.30.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.30.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.31.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.32.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.32.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.33.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.34.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.34.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.34.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.35.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.36.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.37.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.37.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.37.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.37.3 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.38.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.38.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.38.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.39.0 (conflict analysis result)
- Conclusion: don't install laravel/framework 11.x-dev (conflict analysis result)
- Conclusion: don't install laravel/framework v10.40.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.41.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.42.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.43.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.44.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.45.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.45.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.46.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.47.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.1 (conflict analys
|
Install dependencies
Process completed with exit code 1.
|
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