Your requirements could not be resolved to an installable set of packages. Problem 1 - laravel/framework dev-master requires symfony/process ^7.0 -> satisfiable by symfony/process[7.0.x-dev]. - orchestra/testbench[v6.28.0, ..., 6.x-dev] require laravel/framework ^8.83.27 -> found laravel/framework[v8.83.27, 8.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench[v7.26.2, ..., 7.x-dev] require laravel/framework ^9.52.15 -> found laravel/framework[v9.52.15, v9.52.16, 9.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench 8.x-dev requires laravel/framework 10.x-dev -> found laravel/framework[10.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench[v3.1.0, ..., v3.1.3] require laravel/framework ~5.1.0 -> found laravel/framework[v5.1.0, ..., 5.1.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench[v3.1.4, ..., v3.1.6] require laravel/framework ~5.1.11 -> found laravel/framework[v5.1.11, ..., 5.1.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench[v3.1.7, ..., 3.1.x-dev] require laravel/framework ~5.1.27 -> found laravel/framework[v5.1.27, ..., 5.1.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench v3.2.0 requires laravel/framework ~5.2.0 -> found laravel/framework[v5.2.0-beta1, ..., 5.2.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench[v3.2.1, ..., v3.2.2] require laravel/framework ~5.2.7 -> found laravel/framework[v5.2.7, ..., 5.2.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench v3.2.3 requires laravel/framework ~5.2.15 -> found laravel/framework[v5.2.15, ..., 5.2.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench[v3.2.4, ..., 3.2.x-dev] require laravel/framework ~5.2.28 -> found laravel/framework[v5.2.28, ..., 5.2.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench v3.3.0 requires laravel/framework ~5.3.0 -> found laravel/framework[v5.3.0-RC1, ..., 5.3.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench[v3.3.1, ..., v3.3.3] require laravel/framework ~5.3.3 -> found laravel/framework[v5.3.3, ..., 5.3.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench v3.3.4 requires laravel/framework ~5.3.11 -> found laravel/framework[v5.3.11, ..., 5.3.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench[v3.3.5, ..., 3.3.x-dev] require laravel/framework ~5.3.29 -> found laravel/framework[v5.3.29, v5.3.30, v5.3.31, 5.3.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench[v3.4.0, ..., v3.4.5] require laravel/framework ~5.4.0 -> found laravel/framework[v5.4.0, ..., 5.4.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench v3.4.6 requires laravel/framework ~5.4.15 -> found laravel/framework[v5.4.15, ..., 5.4.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench[v3.4.7, ..., v3.4.10] require laravel/framework ~5.4.17 -> found laravel/framework[v5.4.17, ..., 5.4.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench[v3.4.11, ..., 3.4.x-dev] require laravel/framework ~5.4.36 -> found laravel/framework[v5.4.36, 5.4.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench[v3.5.0, ..., v3.5.2] require laravel/framework ~5.5.0 -> found laravel/framework[v5.5.0, ..., 5.5.x-dev] but it conflicts with your root composer.json require (dev-master as 10). - orchestra/testbench v3.5.3

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/var-dumper[v4.1.0-BETA1, ..., v4.4.8] require php ^7.1.3 -> your php version (8.2.11) does not satisfy that requirement. - symfony/var-dumper[v5.0.0-BETA1, ..., v5.0.0-RC1] require php ^7.2.9 -> your php version (8.2.11) does not satisfy that requirement. - symfony/var-dumper[v5.0.0, ..., v5.1.0-RC1] require php ^7.2.5 -> your php version (8.2.11) does not satisfy that requirement. - Root composer.json requires laravel/framework dev-master as 10 -> satisfiable by laravel/framework[dev-master]. - laravel/tinker[v2.8.0, ..., 2.x-dev] require symfony/var-dumper ^4.3.4|^5.0|^6.0 -> satisfiable by symfony/var-dumper[v4.3.4, ..., 4.4.x-dev, v5.0.0-BETA1, ..., 5.4.x-dev, v6.0.0-BETA1, ..., 6.4.x-dev]. - You can only install one version of a package, so only one of these can be installed: symfony/var-dumper[v2.7.0-BETA1, ..., 2.8.x-dev, v3.0.0-BETA1, ..., 3.4.x-dev, v4.0.0-BETA1, ..., 4.4.x-dev, v5.0.0-BETA1, ..., 5.4.x-dev, v6.0.0-BETA1, ..., 6.4.x-dev, 7.0.x-dev]. - laravel/framework dev-master requires symfony/var-dumper ^7.0 -> satisfiable by symfony/var-dumper[7.0.x-dev]. - Root composer.json requires laravel/tinker ^2.8 -> satisfiable by laravel/tinker[v2.8.0, v2.8.1, v2.8.2, 2.x-dev]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

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