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 ^4.0|^5.0|^6.0|^7.0|^8.0|^9.0|^10.0 -> satisfiable by orchestra/testbench[v4.0.0, ..., v4.18.0, v5.0.0, ..., v5.20.0, v6.0.0, ..., v6.47.1, v7.0.0, ..., v7.56.0, v8.0.0, ..., v8.37.0, v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0]. - orchestra/testbench[v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0] require php ^8.2 -> your php version (7.2.34) does not satisfy that requirement. - orchestra/testbench[v4.0.0, ..., v4.0.1] require laravel/framework ^6.0 -> found laravel/framework[v6.0.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench v4.1.0 requires laravel/framework ^6.1 -> found laravel/framework[v6.1.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench[v4.7.0, ..., v4.13.0] require laravel/framework ^6.18 -> found laravel/framework[v6.18.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench[v4.14.0, ..., v4.18.0] require laravel/framework ^6.20.12 -> found laravel/framework[v6.20.12, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench v4.2.0 requires laravel/framework ^6.2 -> found laravel/framework[v6.2.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench[v4.3.0, ..., v4.4.1] require laravel/framework ^6.4 -> found laravel/framework[v6.4.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m

The strategy configuration was canceled because "tests._7_2__6_0" failed

The strategy configuration was canceled because "tests._7_2__6_0" failed

The strategy configuration was canceled because "tests._7_2__6_0" failed

The strategy configuration was canceled because "tests._7_2__6_0" failed

The strategy configuration was canceled because "tests._7_2__6_0" failed

The strategy configuration was canceled because "tests._7_2__6_0" failed

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 ^4.0|^5.0|^6.0|^7.0|^8.0|^9.0|^10.0 -> satisfiable by orchestra/testbench[v4.0.0, ..., v4.18.0, v5.0.0, ..., v5.20.0, v6.0.0, ..., v6.47.1, v7.0.0, ..., v7.56.0, v8.0.0, ..., v8.37.0, v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0]. - orchestra/testbench[v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0] require php ^8.2 -> your php version (7.2.34) does not satisfy that requirement. - orchestra/testbench[v4.0.0, ..., v4.0.1] require laravel/framework ^6.0 -> found laravel/framework[v6.0.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench v4.1.0 requires laravel/framework ^6.1 -> found laravel/framework[v6.1.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench[v4.7.0, ..., v4.13.0] require laravel/framework ^6.18 -> found laravel/framework[v6.18.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench[v4.14.0, ..., v4.18.0] require laravel/framework ^6.20.12 -> found laravel/framework[v6.20.12, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench v4.2.0 requires laravel/framework ^6.2 -> found laravel/framework[v6.2.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench[v4.3.0, ..., v4.4.1] require laravel/framework ^6.4 -> found laravel/framework[v6.4.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench[v4.5.0, ..., v4.6.0] require laravel/framework ^6.9 -> found laravel/framework[v6.9.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench v5.0.0 requires laravel/framework ^7.0 -> found laravel/framework[v7.0.0, ..., v7.30.7] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-rvky-x3cg-y3qd", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench v5.0.1 requires laravel/framework ^7.0.1 -> found laravel/framework[v7.0.1, ..., v7.30.7] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-rvky-x3cg-y3qd", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench v5.0.2 requires laravel/framework ^7.0.6 -> found laravel/framework[v7.0.6, ..., v7.30.7] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-rvky-x3cg-y3qd", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench[v5.5.0, ..., v5.12.1] require laravel/framework ^7.24 -> found laravel/framework[v7.24.0, ..., v7.30.7] but these were

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^4.0|^5.0|^6.0|^7.0|^8.0|^9.0|^10.0 -> satisfiable by orchestra/testbench[v4.0.0, ..., v4.18.0, v5.0.0, ..., v5.20.0, v6.0.0, ..., v6.47.1, v7.0.0, ..., v7.56.0, v8.0.0, ..., v8.37.0, v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0]. - orchestra/testbench[v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0] require php ^8.2 -> your php version (7.4.33) does not satisfy that requirement. - orchestra/testbench[v4.0.0, ..., v4.0.1] require laravel/framework ^6.0 -> found laravel/framework[v6.0.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench v4.1.0 requires laravel/framework ^6.1 -> found laravel/framework[v6.1.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench[v4.7.0, ..., v4.13.0] require laravel/framework ^6.18 -> found laravel/framework[v6.18.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench[v4.14.0, ..., v4.18.0] require laravel/framework ^6.20.12 -> found laravel/framework[v6.20.12, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench v4.2.0 requires laravel/framework ^6.2 -> found laravel/framework[v6.2.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench[v4.3.0, ..., v4.4.1] require laravel/framework ^6.4 -> found laravel/framework[v6.4.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^4.0|^5.0|^6.0|^7.0|^8.0|^9.0|^10.0 -> satisfiable by orchestra/testbench[v4.0.0, ..., v4.18.0, v5.0.0, ..., v5.20.0, v6.0.0, ..., v6.47.1, v7.0.0, ..., v7.56.0, v8.0.0, ..., v8.37.0, v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0]. - orchestra/testbench[v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0] require php ^8.2 -> your php version (7.4.33) does not satisfy that requirement. - orchestra/testbench[v4.0.0, ..., v4.0.1] require laravel/framework ^6.0 -> found laravel/framework[v6.0.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench v4.1.0 requires laravel/framework ^6.1 -> found laravel/framework[v6.1.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench[v4.7.0, ..., v4.13.0] require laravel/framework ^6.18 -> found laravel/framework[v6.18.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench[v4.14.0, ..., v4.18.0] require laravel/framework ^6.20.12 -> found laravel/framework[v6.20.12, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench v4.2.0 requires laravel/framework ^6.2 -> found laravel/framework[v6.2.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench[v4.3.0, ..., v4.4.1] require laravel/framework ^6.4 -> found laravel/framework[v6.4.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench[v4.5.0, ..., v4.6.0] require laravel/framework ^6.9 -> found laravel/framework[v6.9.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench v5.0.0 requires laravel/framework ^7.0 -> found laravel/framework[v7.0.0, ..., v7.30.7] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-rvky-x3cg-y3qd", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench v5.0.1 requires laravel/framework ^7.0.1 -> found laravel/framework[v7.0.1, ..., v7.30.7] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-rvky-x3cg-y3qd", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench v5.0.2 requires laravel/framework ^7.0.6 -> found laravel/framework[v7.0.6, ..., v7.30.7] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-rvky-x3cg-y3qd", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench[v5.5.0, ..., v5.12.1] require laravel/framework ^7.24 -> found laravel/framework[v7.24.0, ..., v7.30.7] but these were

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^4.0|^5.0|^6.0|^7.0|^8.0|^9.0|^10.0 -> satisfiable by orchestra/testbench[v4.0.0, ..., v4.18.0, v5.0.0, ..., v5.20.0, v6.0.0, ..., v6.47.1, v7.0.0, ..., v7.56.0, v8.0.0, ..., v8.37.0, v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0]. - orchestra/testbench[v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0] require php ^8.2 -> your php version (8.0.30) does not satisfy that requirement. - orchestra/testbench[v4.0.0, ..., v4.0.1] require laravel/framework ^6.0 -> found laravel/framework[v6.0.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench v4.1.0 requires laravel/framework ^6.1 -> found laravel/framework[v6.1.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench[v4.7.0, ..., v4.13.0] require laravel/framework ^6.18 -> found laravel/framework[v6.18.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench[v4.14.0, ..., v4.18.0] require laravel/framework ^6.20.12 -> found laravel/framework[v6.20.12, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench v4.2.0 requires laravel/framework ^6.2 -> found laravel/framework[v6.2.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench[v4.3.0, ..., v4.4.1] require laravel/framework ^6.4 -> found laravel/framework[v6.4.0, ..., v6.20.45] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-dpt9-7cmv-dk65", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^4.0|^5.0|^6.0|^7.0|^8.0|^9.0|^10.0 -> satisfiable by orchestra/testbench[v4.0.0, ..., v4.18.0, v5.0.0, ..., v5.20.0, v6.0.0, ..., v6.47.1, v7.0.0, ..., v7.56.0, v8.0.0, ..., v8.37.0, v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0]. - orchestra/testbench[v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0] require php ^8.2 -> your php version (8.0.30) does not satisfy that requirement. - orchestra/testbench[v4.0.0, ..., v4.0.1] require laravel/framework ^6.0 -> found laravel/framework[v6.0.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench v4.1.0 requires laravel/framework ^6.1 -> found laravel/framework[v6.1.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench[v4.7.0, ..., v4.13.0] require laravel/framework ^6.18 -> found laravel/framework[v6.18.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench[v4.14.0, ..., v4.18.0] require laravel/framework ^6.20.12 -> found laravel/framework[v6.20.12, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench v4.2.0 requires laravel/framework ^6.2 -> found laravel/framework[v6.2.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench[v4.3.0, ..., v4.4.1] require laravel/framework ^6.4 -> found laravel/framework[v6.4.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench[v4.5.0, ..., v4.6.0] require laravel/framework ^6.9 -> found laravel/framework[v6.9.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^7.0). - orchestra/testbench v5.0.0 requires laravel/framework ^7.0 -> found laravel/framework[v7.0.0, ..., v7.30.7] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-rvky-x3cg-y3qd", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench v5.0.1 requires laravel/framework ^7.0.1 -> found laravel/framework[v7.0.1, ..., v7.30.7] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-rvky-x3cg-y3qd", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench v5.0.2 requires laravel/framework ^7.0.6 -> found laravel/framework[v7.0.6, ..., v7.30.7] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-7ywf-hktb-jkn9", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-vhvj-tvg4-96jj", "PKSA-nrj3-r2wg-yt8b", "PKSA-rvky-x3cg-y3qd", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench[v5.5.0, ..., v5.12.1] require laravel/framework ^7.24 -> found laravel/framework[v7.24.0, ..., v7.30.7] but these were

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^4.0|^5.0|^6.0|^7.0|^8.0|^9.0|^10.0 -> satisfiable by orchestra/testbench[v4.0.0, ..., v4.18.0, v5.0.0, ..., v5.20.0, v6.0.0, ..., v6.47.1, v7.0.0, ..., v7.56.0, v8.0.0, ..., v8.37.0, v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0]. - orchestra/testbench[v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0] require php ^8.2 -> your php version (7.4.33) does not satisfy that requirement. - orchestra/testbench[v4.0.0, ..., v4.0.1] require laravel/framework ^6.0 -> found laravel/framework[v6.0.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench v4.1.0 requires laravel/framework ^6.1 -> found laravel/framework[v6.1.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench[v4.7.0, ..., v4.13.0] require laravel/framework ^6.18 -> found laravel/framework[v6.18.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench[v4.14.0, ..., v4.18.0] require laravel/framework ^6.20.12 -> found laravel/framework[v6.20.12, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench v4.2.0 requires laravel/framework ^6.2 -> found laravel/framework[v6.2.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench[v4.3.0, ..., v4.4.1] require laravel/framework ^6.4 -> found laravel/framework[v6.4.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench[v4.5.0, ..., v4.6.0] require laravel/framework ^6.9 -> found laravel/framework[v6.9.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench v5.0.0 requires laravel/framework ^7.0 -> found laravel/framework[v7.0.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench v5.0.1 requires laravel/framework ^7.0.1 -> found laravel/framework[v7.0.1, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench v5.0.2 requires laravel/framework ^7.0.6 -> found laravel/framework[v7.0.6, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench[v5.5.0, ..., v5.12.1] require laravel/framework ^7.24 -> found laravel/framework[v7.24.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench[v5.13.0, ..., v5.20.0] require laravel/framework ^7.30.3 -> found laravel/framework[v7.30.3, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench[v5.1.0, ..., v5.2.0] require laravel/framework ^7.1 -> found laravel/framework[v7.1.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench[v5.3.0, ..., v5.4.0] require laravel/framework ^7.10 -> found laravel/framework[v7.10.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^8.0). - orchestra/testbench[v6.0.0, ..., v6.7.0] require laravel/framework ^8.0 -> found laravel/framework[v8.0.0, ..., v8.83.29] but these were not loaded, because they are affected by security advisories ("PKSA-8qx3-n5y5-vvnd", "PKSA-w7xr-vk7n-rstm", "PKSA-p3rx-dfwp-73ny", "PKSA-ckwp-rt7t-c46m", "PKSA-4npr-btr6-zhny", "PKSA-njrm-6dtg-m2pc", "PKSA-985r-hryy-555b"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. - orchestra/testbench[v6.10.0, ..., v6.18.0] require laravel/framework ^8.25 -> fou

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^4.0|^5.0|^6.0|^7.0|^8.0|^9.0|^10.0 -> satisfiable by orchestra/testbench[v4.0.0, ..., v4.18.0, v5.0.0, ..., v5.20.0, v6.0.0, ..., v6.47.1, v7.0.0, ..., v7.56.0, v8.0.0, ..., v8.37.0, v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0]. - orchestra/testbench[v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0] require php ^8.2 -> your php version (8.1.34) does not satisfy that requirement. - orchestra/testbench[v4.0.0, ..., v4.0.1] require laravel/framework ^6.0 -> found laravel/framework[v6.0.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v4.1.0 requires laravel/framework ^6.1 -> found laravel/framework[v6.1.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.7.0, ..., v4.13.0] require laravel/framework ^6.18 -> found laravel/framework[v6.18.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.14.0, ..., v4.18.0] require laravel/framework ^6.20.12 -> found laravel/framework[v6.20.12, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v4.2.0 requires laravel/framework ^6.2 -> found laravel/framework[v6.2.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.3.0, ..., v4.4.1] require laravel/framework ^6.4 -> found laravel/framework[v6.4.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.5.0, ..., v4.6.0] require laravel/framework ^6.9 -> found laravel/framework[v6.9.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v5.0.0 requires laravel/framework ^7.0 -> found laravel/framework[v7.0.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v5.0.1 requires laravel/framework ^7.0.1 -> found laravel/framework[v7.0.1, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v5.0.2 requires laravel/framework ^7.0.6 -> found laravel/framework[v7.0.6, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v5.5.0, ..., v5.12.1] require laravel/framework ^7.24 -> found laravel/framework[v7.24.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v5.13.0, ..., v5.20.0] require laravel/framework ^7.30.3 -> found laravel/framework[v7.30.3, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v5.1.0, ..., v5.2.0] require laravel/framework ^7.1 -> found laravel/framework[v7.1.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v5.3.0, ..., v5.4.0] require laravel/framework ^7.10 -> found laravel/framework[v7.10.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v6.0.0, ..., v6.7.0] require laravel/framework ^8.0 -> found laravel/framework[v8.0.0, ..., v8.83.29] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v6.10.0, ..., v6.18.0] require laravel/framework ^8.25 -> found laravel/framework[v8.25.0, ..., v8.83.29] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v6.19.0 requires laravel/framework ^8.26 -> found laravel/framework[v8.26.0, ..., v8.83.29] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v6.20.0, ..., v6.21.1] require laravel/fram

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^4.0|^5.0|^6.0|^7.0|^8.0|^9.0|^10.0 -> satisfiable by orchestra/testbench[v4.0.0, ..., v4.18.0, v5.0.0, ..., v5.20.0, v6.0.0, ..., v6.47.1, v7.0.0, ..., v7.56.0, v8.0.0, ..., v8.37.0, v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0]. - orchestra/testbench v10.0.0 requires laravel/framework ^12.0.1 -> found laravel/framework[v12.0.1, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v10.1.0 requires laravel/framework ^12.1.1 -> found laravel/framework[v12.1.1, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v10.8.0, ..., v10.10.0] require laravel/framework ^12.40.0 -> found laravel/framework[v12.40.0, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v10.11.0 requires laravel/framework ^12.55.0 -> found laravel/framework[v12.55.0, v12.55.1, v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v10.2.0, ..., v10.2.2] require laravel/framework ^12.3.0 -> found laravel/framework[v12.3.0, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v10.3.0, ..., v10.5.0] require laravel/framework ^12.8.0 -> found laravel/framework[v12.8.0, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v10.6.0 requires laravel/framework ^12.24.0 -> found laravel/framework[v12.24.0, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v10.7.0 requires laravel/framework ^12.28.0 -> found laravel/framework[v12.28.0, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.0.0, ..., v4.0.1] require laravel/framework ^6.0 -> found laravel/framework[v6.0.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v4.1.0 requires laravel/framework ^6.1 -> found laravel/framework[v6.1.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.7.0, ..., v4.13.0] require laravel/framework ^6.18 -> found laravel/framework[v6.18.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.14.0, ..., v4.18.0] require laravel/framework ^6.20.12 -> found laravel/framework[v6.20.12, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v4.2.0 requires laravel/framework ^6.2 -> found laravel/framework[v6.2.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.3.0, ..., v4.4.1] require laravel/framework ^6.4 -> found laravel/framework[v6.4.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.5.0, ..., v4.6.0] require laravel/framework ^6.9 -> found laravel/framework[v6.9.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v5.0.0 requires laravel/framework ^7.0 -> found laravel/framework[v7.0.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v5.0.1 requires laravel/framework ^7.0.1 -> found laravel/framework[v7.0.1, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v5.0.2 requires laravel/framework ^7.0.6 -> found laravel/framework[v7.0.6, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testb

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^4.0|^5.0|^6.0|^7.0|^8.0|^9.0|^10.0 -> satisfiable by orchestra/testbench[v4.0.0, ..., v4.18.0, v5.0.0, ..., v5.20.0, v6.0.0, ..., v6.47.1, v7.0.0, ..., v7.56.0, v8.0.0, ..., v8.37.0, v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0]. - orchestra/testbench v10.0.0 requires laravel/framework ^12.0.1 -> found laravel/framework[v12.0.1, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v10.1.0 requires laravel/framework ^12.1.1 -> found laravel/framework[v12.1.1, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v10.8.0, ..., v10.10.0] require laravel/framework ^12.40.0 -> found laravel/framework[v12.40.0, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v10.11.0 requires laravel/framework ^12.55.0 -> found laravel/framework[v12.55.0, v12.55.1, v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v10.2.0, ..., v10.2.2] require laravel/framework ^12.3.0 -> found laravel/framework[v12.3.0, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v10.3.0, ..., v10.5.0] require laravel/framework ^12.8.0 -> found laravel/framework[v12.8.0, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v10.6.0 requires laravel/framework ^12.24.0 -> found laravel/framework[v12.24.0, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v10.7.0 requires laravel/framework ^12.28.0 -> found laravel/framework[v12.28.0, ..., v12.56.0] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.0.0, ..., v4.0.1] require laravel/framework ^6.0 -> found laravel/framework[v6.0.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v4.1.0 requires laravel/framework ^6.1 -> found laravel/framework[v6.1.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.7.0, ..., v4.13.0] require laravel/framework ^6.18 -> found laravel/framework[v6.18.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.14.0, ..., v4.18.0] require laravel/framework ^6.20.12 -> found laravel/framework[v6.20.12, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v4.2.0 requires laravel/framework ^6.2 -> found laravel/framework[v6.2.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.3.0, ..., v4.4.1] require laravel/framework ^6.4 -> found laravel/framework[v6.4.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.5.0, ..., v4.6.0] require laravel/framework ^6.9 -> found laravel/framework[v6.9.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v5.0.0 requires laravel/framework ^7.0 -> found laravel/framework[v7.0.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v5.0.1 requires laravel/framework ^7.0.1 -> found laravel/framework[v7.0.1, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v5.0.2 requires laravel/framework ^7.0.6 -> found laravel/framework[v7.0.6, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testb

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires orchestra/testbench ^4.0|^5.0|^6.0|^7.0|^8.0|^9.0|^10.0 -> satisfiable by orchestra/testbench[v4.0.0, ..., v4.18.0, v5.0.0, ..., v5.20.0, v6.0.0, ..., v6.47.1, v7.0.0, ..., v7.56.0, v8.0.0, ..., v8.37.0, v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0]. - orchestra/testbench[v9.0.0, ..., v9.17.0, v10.0.0, ..., v10.11.0] require php ^8.2 -> your php version (8.0.30) does not satisfy that requirement. - orchestra/testbench[v4.0.0, ..., v4.0.1] require laravel/framework ^6.0 -> found laravel/framework[v6.0.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v4.1.0 requires laravel/framework ^6.1 -> found laravel/framework[v6.1.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.7.0, ..., v4.13.0] require laravel/framework ^6.18 -> found laravel/framework[v6.18.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.14.0, ..., v4.18.0] require laravel/framework ^6.20.12 -> found laravel/framework[v6.20.12, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v4.2.0 requires laravel/framework ^6.2 -> found laravel/framework[v6.2.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.3.0, ..., v4.4.1] require laravel/framework ^6.4 -> found laravel/framework[v6.4.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v4.5.0, ..., v4.6.0] require laravel/framework ^6.9 -> found laravel/framework[v6.9.0, ..., v6.20.45] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v5.0.0 requires laravel/framework ^7.0 -> found laravel/framework[v7.0.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v5.0.1 requires laravel/framework ^7.0.1 -> found laravel/framework[v7.0.1, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v5.0.2 requires laravel/framework ^7.0.6 -> found laravel/framework[v7.0.6, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v5.5.0, ..., v5.12.1] require laravel/framework ^7.24 -> found laravel/framework[v7.24.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v5.13.0, ..., v5.20.0] require laravel/framework ^7.30.3 -> found laravel/framework[v7.30.3, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v5.1.0, ..., v5.2.0] require laravel/framework ^7.1 -> found laravel/framework[v7.1.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v5.3.0, ..., v5.4.0] require laravel/framework ^7.10 -> found laravel/framework[v7.10.0, ..., v7.30.7] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v6.0.0, ..., v6.7.0] require laravel/framework ^8.0 -> found laravel/framework[v8.0.0, ..., v8.83.29] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v6.10.0, ..., v6.18.0] require laravel/framework ^8.25 -> found laravel/framework[v8.25.0, ..., v8.83.29] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench v6.19.0 requires laravel/framework ^8.26 -> found laravel/framework[v8.26.0, ..., v8.83.29] but it conflicts with your temporary update constraint (laravel/framework:^9.0). - orchestra/testbench[v6.20.0, ..., v6.21.1] require laravel/fram

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

The strategy configuration was canceled because "tests._7_2__6_0" failed

The operation was canceled.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/