Laravel 11 support #102
Annotations
2 errors and 5 warnings
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires gtmassey/period ^1.0 -> satisfiable by gtmassey/period[v1.0.0, v1.1.0].
- 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.1.4, ..., 10.x-dev, v11.0.0, ..., 11.x-dev].
- Root composer.json requires nunomaduro/collision ^8.0 -> satisfiable by nunomaduro/collision[v8.0.0, ..., v8.x-dev].
- Root composer.json requires orchestra/testbench ^7.15|^8.0.3|^9.0 -> satisfiable by orchestra/testbench[v7.15.0, ..., 7.x-dev, v8.0.3, ..., 8.x-dev, v9.0.0, ..., 9.x-dev].
- gtmassey/period v1.0.0 requires illuminate/contracts ^9.0 -> satisfiable by illuminate/contracts[v9.0.0-beta.1, ..., 9.x-dev], laravel/framework[v9.0.0-beta.1, ..., 9.x-dev].
- Conclusion: don't install laravel/framework 10.x-dev (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/framework v10.16.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.17.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.17.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.18.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.19.0 (conflict analysis result)
- Conclusion: don't install larave
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
The `save-state` 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/
|
The `save-state` 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/
|
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/
|
The logs for this run have expired and are no longer available.
Loading