Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires illuminate/support 9.* -> satisfiable by laravel/framework[v9.0.0-beta.1, ..., 9.x-dev], illuminate/support[v9.0.0-beta.1, ..., 9.x-dev]. - Root composer.json requires spatie/laravel-feed ^4.4.0 -> satisfiable by spatie/laravel-feed[4.4.0]. - laravel/framework[v11.0.0, ..., 11.x-dev] require php ^8.2 -> your php version (8.1.30) does not satisfy that requirement. - spatie/laravel-feed 4.4.0 requires illuminate/support ^10.0|^11.0 -> satisfiable by laravel/framework[v10.0.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev]. - Conclusion: don't install laravel/framework 10.x-dev (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/framework v10.16.1 (conflict analysis result) - Conclusion: don't inst

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires spatie/laravel-feed ^4.4.0 -> satisfiable by spatie/laravel-feed[4.4.0]. - illuminate/contracts[v10.0.0, ..., 10.x-dev] require php ^8.1 -> your php version (8.0.30) does not satisfy that requirement. - laravel/framework[v10.0.0, ..., 10.x-dev] require php ^8.1 -> your php version (8.0.30) does not satisfy that requirement. - illuminate/contracts[v11.0.0, ..., 11.x-dev] require php ^8.2 -> your php version (8.0.30) does not satisfy that requirement. - laravel/framework[v11.0.0, ..., 11.x-dev] require php ^8.2 -> your php version (8.0.30) does not satisfy that requirement. - spatie/laravel-feed 4.4.0 requires illuminate/contracts ^10.0|^11.0 -> satisfiable by laravel/framework[v10.0.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev], illuminate/contracts[v10.0.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires illuminate/support 9.* -> satisfiable by laravel/framework[v9.0.0-beta.1, ..., 9.x-dev], illuminate/support[v9.0.0-beta.1, ..., 9.x-dev]. - Root composer.json requires spatie/laravel-feed ^4.4.0 -> satisfiable by spatie/laravel-feed[4.4.0]. - spatie/laravel-feed 4.4.0 requires illuminate/support ^10.0|^11.0 -> satisfiable by laravel/framework[v10.0.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev]. - Conclusion: don't install laravel/framework 10.x-dev (conflict analysis result) - Conclusion: don't install laravel/framework 11.x-dev (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/framework v10.16.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.17.0 (conflict an

Process completed with exit code 2.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@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/setup-node@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 following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@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/setup-node@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 following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@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/setup-node@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 following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@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/setup-node@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 following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@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/setup-node@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 following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@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/setup-node@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 following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@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/setup-node@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 following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/