Update pestphp/pest requirement from ^2.20 to ^3.0 #44
Annotations
2 errors and 1 warning
Your requirements could not be resolved to an installable set of packages.
Problem 1
- laravel/framework[v7.29.0, ..., 7.x-dev, v8.19.0, ..., 8.x-dev] require psr/simple-cache ^1.0 -> found psr/simple-cache[1.0.0, 1.0.1] but it conflicts with your root composer.json require (^3.0).
- laravel/framework[v7.20.0, ..., v7.28.4] require php ^7.2.5 -> your php version (8.3.11) does not satisfy that requirement.
- 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].
- Conclusion: don't install laravel/framework v10.48.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.47.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.46.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.45.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.45.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.44.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.43.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.42.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.41.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.40.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.39.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.38.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.38.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.38.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.37.3 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.37.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.37.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.37.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.36.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.35.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.34.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.34.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.34.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.33.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.32.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.32.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.31.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.30.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.30.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.29.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.28.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.27.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.26.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.26.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.26.0 (conflict analysis result)
- Conclusion: don't install illuminate/support v10.48.4 (conflict analysis result)
- Conclusion: don't install illuminate/support v10.39.0 (conflict analysis result)
- Conclusion: don't install illuminate/support v10.33.0 (conflict analysis result)
- Conclusion: don't install illuminate/support v10.26.0 (conflict analysis result)
- Conclusion: don't install illuminate/support v10.23.0 (conflict analysis result)
- Conclusion: don't install illuminate/support v10.17.0 (conflic
|
|
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/
|
This job failed
Loading