Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^9.0 -> satisfiable by orchestra/testbench[v9.0.0]. - orchestra/testbench v9.0.0 requires phpunit/phpunit ^10.5 || ^11.0.1 -> found phpunit/phpunit[10.5.0, ..., 10.5.13, 11.0.1, ..., 11.0.6] but it conflicts with your root composer.json require (^9.1). Problem 2 - jasonmccreary/laravel-test-assertions v2.4.0 requires phpunit/phpunit ^10.1 -> found phpunit/phpunit[10.1.0, ..., 10.5.13] but it conflicts with your root composer.json require (^9.1). - Root composer.json requires jasonmccreary/laravel-test-assertions ^2.3 -> satisfiable by jasonmccreary/laravel-test-assertions[v2.3, v2.4.0]. - Conclusion: don't install laravel/framework v11.0.4 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.3 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.2 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.1 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.0 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.5 (conflict analysis result) - jasonmccreary/laravel-test-assertions v2.3 requires illuminate/testing ^9.0|^10.0 -> satisfiable by illuminate/testing[v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.48.3]. - Only one of these can be installed: illuminate/testing[v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.48.3, v11.0.0, ..., v11.0.6], laravel/framework[v11.0.0, ..., v11.0.6]. laravel/framework replaces illuminate/testing and thus cannot coexist with it. - Root composer.json requires laravel/framework 11.* -> satisfiable by laravel/framework[v11.0.0, ..., v11.0.6].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^9.0 -> satisfiable by orchestra/testbench[v9.0.0]. - orchestra/testbench v9.0.0 requires phpunit/phpunit ^10.5 || ^11.0.1 -> found phpunit/phpunit[10.5.0, ..., 10.5.13, 11.0.1, ..., 11.0.6] but it conflicts with your root composer.json require (^9.1). Problem 2 - jasonmccreary/laravel-test-assertions v2.4.0 requires phpunit/phpunit ^10.1 -> found phpunit/phpunit[10.1.0, ..., 10.5.13] but it conflicts with your root composer.json require (^9.1). - Root composer.json requires jasonmccreary/laravel-test-assertions ^2.3 -> satisfiable by jasonmccreary/laravel-test-assertions[v2.3, v2.4.0]. - Conclusion: don't install laravel/framework v11.0.2 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.3 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.4 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.5 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.6 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.1 (conflict analysis result) - jasonmccreary/laravel-test-assertions v2.3 requires illuminate/testing ^9.0|^10.0 -> satisfiable by illuminate/testing[v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.48.3]. - Only one of these can be installed: illuminate/testing[v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.48.3, v11.0.0, ..., v11.0.6], laravel/framework[v11.0.0, ..., v11.0.6]. laravel/framework replaces illuminate/testing and thus cannot coexist with it. - Root composer.json requires laravel/framework 11.* -> satisfiable by laravel/framework[v11.0.0, ..., v11.0.6].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^9.0 -> satisfiable by orchestra/testbench[v9.0.0]. - orchestra/testbench v9.0.0 requires phpunit/phpunit ^10.5 || ^11.0.1 -> found phpunit/phpunit[10.5.0, ..., 10.5.13, 11.0.1, ..., 11.0.6] but it conflicts with your root composer.json require (^9.1). Problem 2 - jasonmccreary/laravel-test-assertions v2.4.0 requires phpunit/phpunit ^10.1 -> found phpunit/phpunit[10.1.0, ..., 10.5.13] but it conflicts with your root composer.json require (^9.1). - Root composer.json requires jasonmccreary/laravel-test-assertions ^2.3 -> satisfiable by jasonmccreary/laravel-test-assertions[v2.3, v2.4.0]. - Conclusion: don't install laravel/framework v11.0.2 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.3 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.4 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.5 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.6 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.1 (conflict analysis result) - jasonmccreary/laravel-test-assertions v2.3 requires illuminate/testing ^9.0|^10.0 -> satisfiable by illuminate/testing[v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.48.3]. - Only one of these can be installed: illuminate/testing[v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.48.3, v11.0.0, ..., v11.0.6], laravel/framework[v11.0.0, ..., v11.0.6]. laravel/framework replaces illuminate/testing and thus cannot coexist with it. - Root composer.json requires laravel/framework 11.* -> satisfiable by laravel/framework[v11.0.0, ..., v11.0.6].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^9.0 -> satisfiable by orchestra/testbench[v9.0.0]. - orchestra/testbench v9.0.0 requires phpunit/phpunit ^10.5 || ^11.0.1 -> found phpunit/phpunit[10.5.0, ..., 10.5.13, 11.0.1, ..., 11.0.6] but it conflicts with your root composer.json require (^9.1). Problem 2 - jasonmccreary/laravel-test-assertions v2.4.0 requires phpunit/phpunit ^10.1 -> found phpunit/phpunit[10.1.0, ..., 10.5.13] but it conflicts with your root composer.json require (^9.1). - Root composer.json requires jasonmccreary/laravel-test-assertions ^2.3 -> satisfiable by jasonmccreary/laravel-test-assertions[v2.3, v2.4.0]. - Conclusion: don't install laravel/framework v11.0.4 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.3 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.2 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.1 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.0 (conflict analysis result) - Conclusion: don't install laravel/framework v11.0.5 (conflict analysis result) - jasonmccreary/laravel-test-assertions v2.3 requires illuminate/testing ^9.0|^10.0 -> satisfiable by illuminate/testing[v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.48.3]. - Only one of these can be installed: illuminate/testing[v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.48.3, v11.0.0, ..., v11.0.6], laravel/framework[v11.0.0, ..., v11.0.6]. laravel/framework replaces illuminate/testing and thus cannot coexist with it. - Root composer.json requires laravel/framework 11.* -> satisfiable by laravel/framework[v11.0.0, ..., v11.0.6].

Process completed with exit code 2.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

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/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.