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/database >=8.80 -> satisfiable by illuminate/database[v8.80.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.64.0, v13.0.0, ..., v13.24.0]. - Root composer.json requires illuminate/filesystem >=8.80 -> satisfiable by illuminate/filesystem[v8.80.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.64.0, v13.0.0, ..., v13.24.0]. - illuminate/database[v10.0.0, ..., v10.49.0] require illuminate/support ^10.0 -> satisfiable by illuminate/support[v10.0.0, ..., v10.49.0]. - illuminate/database[v11.0.0, ..., v11.51.0] require illuminate/macroable ^11.0 -> satisfiable by illuminate/macroable[v11.0.0, ..., v11.51.0]. - illuminate/database[v12.0.0, ..., v12.64.0] require illuminate/macroable ^12.0 -> satisfiable by illuminate/macroable[v12.0.0, ..., v12.64.0]. - illuminate/database[v13.0.0, ..., v13.24.0] require laravel/serializable-closure ^2.0.10 -> found laravel/serializable-closure[v2.0.10, ..., v2.0.15] but it conflicts with your root composer.json require (^1.3). - illuminate/database[v8.80.0, ..., v8.83.27] require symfony/console ^5.4 -> found symfony/console[v5.4.0, ..., v5.4.47] but these were not loaded, likely because it conflicts with another require. - illuminate/database[v9.0.0, ..., v9.34.0] require symfony/console ^6.0 -> found symfony/console[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - illuminate/database[v9.35.0, ..., v9.52.16] require symfony/console ^6.0.9 -> found symfony/console[v6.0.9, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - illuminate/support[v10.0.0, ..., v10.16.1] require nesbot/carbon ^2.62.1 -> satisfiable by nesbot/carbon[2.72.6, 2.73.0]. - illuminate/support[v10.17.0, ..., v10.49.0] require nesbot/carbon ^2.67 -> satisfiable by nesbot/carbon[2.72.6, 2.73.0]. - nesbot/carbon[2.72.6, ..., 2.73.0] require symfony/translation ^3.4 || ^4.0 || ^5.0 || ^6.0 -> found symfony/translation[v3.4.0, ..., v3.4.47, v4.0.0, ..., v4.4.47, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.42] but these were not loaded, likely because it conflicts with another require. - Conclusion: install illuminate/macroable v13.24.0 (conflict analysis result) - You can only install one version of a package, so only one of these can be installed: illuminate/macroable[v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.64.0, v13.0.0, ..., v13.24.0].

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/database >=8.80 -> satisfiable by illuminate/database[v8.80.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.64.0, v13.0.0, ..., v13.24.0]. - Root composer.json requires illuminate/filesystem >=8.80 -> satisfiable by illuminate/filesystem[v8.80.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.64.0, v13.0.0, ..., v13.24.0]. - illuminate/database[v10.0.0, ..., v10.49.0] require illuminate/support ^10.0 -> satisfiable by illuminate/support[v10.0.0, ..., v10.49.0]. - illuminate/database[v11.0.0, ..., v11.51.0] require illuminate/macroable ^11.0 -> satisfiable by illuminate/macroable[v11.0.0, ..., v11.51.0]. - illuminate/database[v12.0.0, ..., v12.64.0] require illuminate/macroable ^12.0 -> satisfiable by illuminate/macroable[v12.0.0, ..., v12.64.0]. - illuminate/database[v13.0.0, ..., v13.24.0] require laravel/serializable-closure ^2.0.10 -> found laravel/serializable-closure[v2.0.10, ..., v2.0.15] but it conflicts with your root composer.json require (^1.3). - illuminate/database[v8.80.0, ..., v8.83.27] require symfony/console ^5.4 -> found symfony/console[v5.4.0, ..., v5.4.47] but these were not loaded, likely because it conflicts with another require. - illuminate/database[v9.0.0, ..., v9.34.0] require symfony/console ^6.0 -> found symfony/console[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - illuminate/database[v9.35.0, ..., v9.52.16] require symfony/console ^6.0.9 -> found symfony/console[v6.0.9, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - illuminate/support[v10.0.0, ..., v10.16.1] require nesbot/carbon ^2.62.1 -> satisfiable by nesbot/carbon[2.72.6, 2.73.0]. - illuminate/support[v10.17.0, ..., v10.49.0] require nesbot/carbon ^2.67 -> satisfiable by nesbot/carbon[2.72.6, 2.73.0]. - nesbot/carbon[2.72.6, ..., 2.73.0] require symfony/translation ^3.4 || ^4.0 || ^5.0 || ^6.0 -> found symfony/translation[v3.4.0, ..., v3.4.47, v4.0.0, ..., v4.4.47, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.42] but these were not loaded, likely because it conflicts with another require. - Conclusion: install illuminate/macroable v13.0.0 (conflict analysis result) - You can only install one version of a package, so only one of these can be installed: illuminate/macroable[v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.64.0, v13.0.0, ..., v13.24.0].

Process completed with exit code 2.

Process completed with exit code 2.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires wouterj/eloquent-bundle * -> satisfiable by wouterj/eloquent-bundle[v0.1.0, ..., 0.5.0, 1.0.0, ..., 1.1.0, 2.0.0, ..., 2.8.1]. - illuminate/database[v4.1.29, ..., v4.1.30] require nesbot/carbon 1.* -> found nesbot/carbon[1.0.0, ..., 1.39.1] but these were not loaded, because they are affected by security advisories ("�]8;;https://github.com/advisories/GHSA-j3f9-p6hm-5w6q�\PKSA-csyb-yc4p-mnbs�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false. - wouterj/eloquent-bundle v0.1.0 requires illuminate/database ~4.1.4 -> satisfiable by illuminate/database[v4.1.29, v4.1.30]. - wouterj/eloquent-bundle[0.2.0, ..., 0.3.0] require php ^5.5|^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[0.4.0, ..., 0.5.0] require php ^5.6.4|^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[1.0.0, ..., 1.0.3] require php ^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle 1.1.0 requires php ^7.1 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[2.0.0, ..., 2.1.1] require symfony/framework-bundle ^4.4 || ^5.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.2.0, ..., 2.3.1] require symfony/framework-bundle ^4.4 || ^5.0 || ^6.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.4.0, ..., 2.5.0] require symfony/framework-bundle ^5.4 || ^6.0 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle 2.6.0 requires symfony/framework-bundle ^6.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.7.0, ..., 2.8.1] require symfony/framework-bundle ^6.0 || ^7.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43, v7.0.0, ..., v7.4.15] but these were not loaded, likely because it conflicts with another require.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires wouterj/eloquent-bundle * -> satisfiable by wouterj/eloquent-bundle[v0.1.0, ..., 0.5.0, 1.0.0, ..., 1.1.0, 2.0.0, ..., 2.8.1]. - illuminate/database[v4.1.29, ..., v4.1.30] require nesbot/carbon 1.* -> found nesbot/carbon[1.0.0, ..., 1.39.1] but these were not loaded, because they are affected by security advisories ("�]8;;https://github.com/advisories/GHSA-j3f9-p6hm-5w6q�\PKSA-csyb-yc4p-mnbs�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false. - wouterj/eloquent-bundle v0.1.0 requires illuminate/database ~4.1.4 -> satisfiable by illuminate/database[v4.1.29, v4.1.30]. - wouterj/eloquent-bundle[0.2.0, ..., 0.3.0] require php ^5.5|^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[0.4.0, ..., 0.5.0] require php ^5.6.4|^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[1.0.0, ..., 1.0.3] require php ^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle 1.1.0 requires php ^7.1 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[2.0.0, ..., 2.1.1] require symfony/framework-bundle ^4.4 || ^5.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.2.0, ..., 2.3.1] require symfony/framework-bundle ^4.4 || ^5.0 || ^6.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.4.0, ..., 2.5.0] require symfony/framework-bundle ^5.4 || ^6.0 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle 2.6.0 requires symfony/framework-bundle ^6.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.7.0, ..., 2.8.1] require symfony/framework-bundle ^6.0 || ^7.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43, v7.0.0, ..., v7.4.15] but these were not loaded, likely because it conflicts with another require.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires wouterj/eloquent-bundle * -> satisfiable by wouterj/eloquent-bundle[v0.1.0, ..., 0.5.0, 1.0.0, ..., 1.1.0, 2.0.0, ..., 2.8.1]. - illuminate/database[v4.1.29, ..., v4.1.30] require nesbot/carbon 1.* -> found nesbot/carbon[1.0.0, ..., 1.39.1] but these were not loaded, because they are affected by security advisories ("�]8;;https://github.com/advisories/GHSA-j3f9-p6hm-5w6q�\PKSA-csyb-yc4p-mnbs�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false. - wouterj/eloquent-bundle v0.1.0 requires illuminate/database ~4.1.4 -> satisfiable by illuminate/database[v4.1.29, v4.1.30]. - wouterj/eloquent-bundle[0.2.0, ..., 0.3.0] require php ^5.5|^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[0.4.0, ..., 0.5.0] require php ^5.6.4|^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[1.0.0, ..., 1.0.3] require php ^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle 1.1.0 requires php ^7.1 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[2.0.0, ..., 2.1.1] require symfony/framework-bundle ^4.4 || ^5.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.2.0, ..., 2.3.1] require symfony/framework-bundle ^4.4 || ^5.0 || ^6.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.4.0, ..., 2.5.0] require symfony/framework-bundle ^5.4 || ^6.0 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle 2.6.0 requires symfony/framework-bundle ^6.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.7.0, ..., 2.8.1] require symfony/framework-bundle ^6.0 || ^7.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43, v7.0.0, ..., v7.4.15] but these were not loaded, likely because it conflicts with another require.

Process completed with exit code 2.

Process completed with exit code 2.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires wouterj/eloquent-bundle * -> satisfiable by wouterj/eloquent-bundle[v0.1.0, ..., 0.5.0, 1.0.0, ..., 1.1.0, 2.0.0, ..., 2.8.1]. - illuminate/database[v4.1.29, ..., v4.1.30] require nesbot/carbon 1.* -> found nesbot/carbon[1.0.0, ..., 1.39.1] but these were not loaded, because they are affected by security advisories ("�]8;;https://github.com/advisories/GHSA-j3f9-p6hm-5w6q�\PKSA-csyb-yc4p-mnbs�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false. - wouterj/eloquent-bundle v0.1.0 requires illuminate/database ~4.1.4 -> satisfiable by illuminate/database[v4.1.29, v4.1.30]. - wouterj/eloquent-bundle[0.2.0, ..., 0.3.0] require php ^5.5|^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[0.4.0, ..., 0.5.0] require php ^5.6.4|^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[1.0.0, ..., 1.0.3] require php ^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle 1.1.0 requires php ^7.1 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[2.0.0, ..., 2.1.1] require symfony/framework-bundle ^4.4 || ^5.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.2.0, ..., 2.3.1] require symfony/framework-bundle ^4.4 || ^5.0 || ^6.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.4.0, ..., 2.5.0] require symfony/framework-bundle ^5.4 || ^6.0 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle 2.6.0 requires symfony/framework-bundle ^6.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.7.0, ..., 2.8.1] require symfony/framework-bundle ^6.0 || ^7.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43, v7.0.0, ..., v7.4.15] but these were not loaded, likely because it conflicts with another require.

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/database >=8.80 -> satisfiable by illuminate/database[v8.80.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.64.0, v13.0.0, ..., v13.24.0]. - Root composer.json requires illuminate/filesystem >=8.80 -> satisfiable by illuminate/filesystem[v8.80.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.64.0, v13.0.0, ..., v13.24.0]. - illuminate/database[v10.0.0, ..., v10.49.0] require illuminate/support ^10.0 -> satisfiable by illuminate/support[v10.0.0, ..., v10.49.0]. - illuminate/database[v11.0.0, ..., v11.51.0] require illuminate/macroable ^11.0 -> satisfiable by illuminate/macroable[v11.0.0, ..., v11.51.0]. - illuminate/database[v12.0.0, ..., v12.64.0] require illuminate/macroable ^12.0 -> satisfiable by illuminate/macroable[v12.0.0, ..., v12.64.0]. - illuminate/database[v13.0.0, ..., v13.24.0] require laravel/serializable-closure ^2.0.10 -> found laravel/serializable-closure[v2.0.10, ..., v2.0.15] but it conflicts with your root composer.json require (^1.3). - illuminate/database[v8.80.0, ..., v8.83.27] require symfony/console ^5.4 -> found symfony/console[v5.4.0, ..., v5.4.47] but these were not loaded, likely because it conflicts with another require. - illuminate/database[v9.0.0, ..., v9.34.0] require symfony/console ^6.0 -> found symfony/console[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - illuminate/database[v9.35.0, ..., v9.52.16] require symfony/console ^6.0.9 -> found symfony/console[v6.0.9, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - illuminate/support[v10.0.0, ..., v10.16.1] require nesbot/carbon ^2.62.1 -> satisfiable by nesbot/carbon[2.72.6, 2.73.0]. - illuminate/support[v10.17.0, ..., v10.49.0] require nesbot/carbon ^2.67 -> satisfiable by nesbot/carbon[2.72.6, 2.73.0]. - nesbot/carbon[2.72.6, ..., 2.73.0] require symfony/translation ^3.4 || ^4.0 || ^5.0 || ^6.0 -> found symfony/translation[v3.4.0, ..., v3.4.47, v4.0.0, ..., v4.4.47, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.42] but these were not loaded, likely because it conflicts with another require. - Conclusion: install illuminate/macroable v13.24.0 (conflict analysis result) - You can only install one version of a package, so only one of these can be installed: illuminate/macroable[v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.64.0, v13.0.0, ..., v13.24.0].

Process completed with exit code 2.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires wouterj/eloquent-bundle * -> satisfiable by wouterj/eloquent-bundle[v0.1.0, ..., 0.5.0, 1.0.0, ..., 1.1.0, 2.0.0, ..., 2.8.1]. - illuminate/database[v4.1.29, ..., v4.1.30] require nesbot/carbon 1.* -> found nesbot/carbon[1.0.0, ..., 1.39.1] but these were not loaded, because they are affected by security advisories ("�]8;;https://github.com/advisories/GHSA-j3f9-p6hm-5w6q�\PKSA-csyb-yc4p-mnbs�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false. - wouterj/eloquent-bundle v0.1.0 requires illuminate/database ~4.1.4 -> satisfiable by illuminate/database[v4.1.29, v4.1.30]. - wouterj/eloquent-bundle[0.2.0, ..., 0.3.0] require php ^5.5|^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[0.4.0, ..., 0.5.0] require php ^5.6.4|^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[1.0.0, ..., 1.0.3] require php ^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle 1.1.0 requires php ^7.1 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[2.0.0, ..., 2.1.1] require symfony/framework-bundle ^4.4 || ^5.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.2.0, ..., 2.3.1] require symfony/framework-bundle ^4.4 || ^5.0 || ^6.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.4.0, ..., 2.5.0] require symfony/framework-bundle ^5.4 || ^6.0 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle 2.6.0 requires symfony/framework-bundle ^6.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.7.0, ..., 2.8.1] require symfony/framework-bundle ^6.0 || ^7.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43, v7.0.0, ..., v7.4.15] but these were not loaded, likely because it conflicts with another require.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires wouterj/eloquent-bundle * -> satisfiable by wouterj/eloquent-bundle[v0.1.0, ..., 0.5.0, 1.0.0, ..., 1.1.0, 2.0.0, ..., 2.8.1]. - illuminate/database[v4.1.29, ..., v4.1.30] require nesbot/carbon 1.* -> found nesbot/carbon[1.0.0, ..., 1.39.1] but these were not loaded, because they are affected by security advisories ("�]8;;https://github.com/advisories/GHSA-j3f9-p6hm-5w6q�\PKSA-csyb-yc4p-mnbs�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false. - wouterj/eloquent-bundle v0.1.0 requires illuminate/database ~4.1.4 -> satisfiable by illuminate/database[v4.1.29, v4.1.30]. - wouterj/eloquent-bundle[0.2.0, ..., 0.3.0] require php ^5.5|^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[0.4.0, ..., 0.5.0] require php ^5.6.4|^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[1.0.0, ..., 1.0.3] require php ^7.0 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle 1.1.0 requires php ^7.1 -> your php version (8.4.24) does not satisfy that requirement. - wouterj/eloquent-bundle[2.0.0, ..., 2.1.1] require symfony/framework-bundle ^4.4 || ^5.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.2.0, ..., 2.3.1] require symfony/framework-bundle ^4.4 || ^5.0 || ^6.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.4.0, ..., 2.5.0] require symfony/framework-bundle ^5.4 || ^6.0 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle 2.6.0 requires symfony/framework-bundle ^6.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.7.0, ..., 2.8.1] require symfony/framework-bundle ^6.0 || ^7.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43, v7.0.0, ..., v7.4.15] but these were not loaded, likely because it conflicts with another require.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires wouterj/eloquent-bundle * -> satisfiable by wouterj/eloquent-bundle[v0.1.0, ..., 0.5.0, 1.0.0, ..., 1.1.0, 2.0.0, ..., 2.8.1]. - illuminate/database[v4.1.29, ..., v4.1.30] require nesbot/carbon 1.* -> found nesbot/carbon[1.0.0, ..., 1.39.1] but these were not loaded, because they are affected by security advisories ("�]8;;https://github.com/advisories/GHSA-j3f9-p6hm-5w6q�\PKSA-csyb-yc4p-mnbs�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false. - wouterj/eloquent-bundle v0.1.0 requires illuminate/database ~4.1.4 -> satisfiable by illuminate/database[v4.1.29, v4.1.30]. - wouterj/eloquent-bundle[0.2.0, ..., 0.3.0] require php ^5.5|^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[0.4.0, ..., 0.5.0] require php ^5.6.4|^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[1.0.0, ..., 1.0.3] require php ^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle 1.1.0 requires php ^7.1 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[2.0.0, ..., 2.1.1] require symfony/framework-bundle ^4.4 || ^5.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.2.0, ..., 2.3.1] require symfony/framework-bundle ^4.4 || ^5.0 || ^6.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.4.0, ..., 2.5.0] require symfony/framework-bundle ^5.4 || ^6.0 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle 2.6.0 requires symfony/framework-bundle ^6.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.7.0, ..., 2.8.1] require symfony/framework-bundle ^6.0 || ^7.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43, v7.0.0, ..., v7.4.15] but these were not loaded, likely because it conflicts with another require.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires wouterj/eloquent-bundle * -> satisfiable by wouterj/eloquent-bundle[v0.1.0, ..., 0.5.0, 1.0.0, ..., 1.1.0, 2.0.0, ..., 2.8.1]. - illuminate/database[v4.1.29, ..., v4.1.30] require nesbot/carbon 1.* -> found nesbot/carbon[1.0.0, ..., 1.39.1] but these were not loaded, because they are affected by security advisories ("�]8;;https://github.com/advisories/GHSA-j3f9-p6hm-5w6q�\PKSA-csyb-yc4p-mnbs�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false. - wouterj/eloquent-bundle v0.1.0 requires illuminate/database ~4.1.4 -> satisfiable by illuminate/database[v4.1.29, v4.1.30]. - wouterj/eloquent-bundle[0.2.0, ..., 0.3.0] require php ^5.5|^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[0.4.0, ..., 0.5.0] require php ^5.6.4|^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[1.0.0, ..., 1.0.3] require php ^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle 1.1.0 requires php ^7.1 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[2.0.0, ..., 2.1.1] require symfony/framework-bundle ^4.4 || ^5.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.2.0, ..., 2.3.1] require symfony/framework-bundle ^4.4 || ^5.0 || ^6.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.4.0, ..., 2.5.0] require symfony/framework-bundle ^5.4 || ^6.0 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle 2.6.0 requires symfony/framework-bundle ^6.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.7.0, ..., 2.8.1] require symfony/framework-bundle ^6.0 || ^7.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43, v7.0.0, ..., v7.4.15] but these were not loaded, likely because it conflicts with another require.

Process completed with exit code 2.

Process completed with exit code 2.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires wouterj/eloquent-bundle * -> satisfiable by wouterj/eloquent-bundle[v0.1.0, ..., 0.5.0, 1.0.0, ..., 1.1.0, 2.0.0, ..., 2.8.1]. - illuminate/database[v4.1.29, ..., v4.1.30] require nesbot/carbon 1.* -> found nesbot/carbon[1.0.0, ..., 1.39.1] but these were not loaded, because they are affected by security advisories ("�]8;;https://github.com/advisories/GHSA-j3f9-p6hm-5w6q�\PKSA-csyb-yc4p-mnbs�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false. - wouterj/eloquent-bundle v0.1.0 requires illuminate/database ~4.1.4 -> satisfiable by illuminate/database[v4.1.29, v4.1.30]. - wouterj/eloquent-bundle[0.2.0, ..., 0.3.0] require php ^5.5|^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[0.4.0, ..., 0.5.0] require php ^5.6.4|^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[1.0.0, ..., 1.0.3] require php ^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle 1.1.0 requires php ^7.1 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[2.0.0, ..., 2.1.1] require symfony/framework-bundle ^4.4 || ^5.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.2.0, ..., 2.3.1] require symfony/framework-bundle ^4.4 || ^5.0 || ^6.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.4.0, ..., 2.5.0] require symfony/framework-bundle ^5.4 || ^6.0 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle 2.6.0 requires symfony/framework-bundle ^6.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.7.0, ..., 2.8.1] require symfony/framework-bundle ^6.0 || ^7.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43, v7.0.0, ..., v7.4.15] but these were not loaded, likely because it conflicts with another require.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires wouterj/eloquent-bundle * -> satisfiable by wouterj/eloquent-bundle[v0.1.0, ..., 0.5.0, 1.0.0, ..., 1.1.0, 2.0.0, ..., 2.8.1]. - illuminate/database[v4.1.29, ..., v4.1.30] require nesbot/carbon 1.* -> found nesbot/carbon[1.0.0, ..., 1.39.1] but these were not loaded, because they are affected by security advisories ("�]8;;https://github.com/advisories/GHSA-j3f9-p6hm-5w6q�\PKSA-csyb-yc4p-mnbs�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false. - wouterj/eloquent-bundle v0.1.0 requires illuminate/database ~4.1.4 -> satisfiable by illuminate/database[v4.1.29, v4.1.30]. - wouterj/eloquent-bundle[0.2.0, ..., 0.3.0] require php ^5.5|^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[0.4.0, ..., 0.5.0] require php ^5.6.4|^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[1.0.0, ..., 1.0.3] require php ^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle 1.1.0 requires php ^7.1 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[2.0.0, ..., 2.1.1] require symfony/framework-bundle ^4.4 || ^5.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.2.0, ..., 2.3.1] require symfony/framework-bundle ^4.4 || ^5.0 || ^6.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.4.0, ..., 2.5.0] require symfony/framework-bundle ^5.4 || ^6.0 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle 2.6.0 requires symfony/framework-bundle ^6.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.7.0, ..., 2.8.1] require symfony/framework-bundle ^6.0 || ^7.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43, v7.0.0, ..., v7.4.15] but these were not loaded, likely because it conflicts with another require.

Process completed with exit code 2.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires wouterj/eloquent-bundle * -> satisfiable by wouterj/eloquent-bundle[v0.1.0, ..., 0.5.0, 1.0.0, ..., 1.1.0, 2.0.0, ..., 2.8.1]. - illuminate/database[v4.1.29, ..., v4.1.30] require nesbot/carbon 1.* -> found nesbot/carbon[1.0.0, ..., 1.39.1] but these were not loaded, because they are affected by security advisories ("�]8;;https://github.com/advisories/GHSA-j3f9-p6hm-5w6q�\PKSA-csyb-yc4p-mnbs�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false. - wouterj/eloquent-bundle v0.1.0 requires illuminate/database ~4.1.4 -> satisfiable by illuminate/database[v4.1.29, v4.1.30]. - wouterj/eloquent-bundle[0.2.0, ..., 0.3.0] require php ^5.5|^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[0.4.0, ..., 0.5.0] require php ^5.6.4|^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[1.0.0, ..., 1.0.3] require php ^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle 1.1.0 requires php ^7.1 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[2.0.0, ..., 2.1.1] require symfony/framework-bundle ^4.4 || ^5.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.2.0, ..., 2.3.1] require symfony/framework-bundle ^4.4 || ^5.0 || ^6.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.4.0, ..., 2.5.0] require symfony/framework-bundle ^5.4 || ^6.0 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle 2.6.0 requires symfony/framework-bundle ^6.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.7.0, ..., 2.8.1] require symfony/framework-bundle ^6.0 || ^7.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43, v7.0.0, ..., v7.4.15] but these were not loaded, likely because it conflicts with another require.

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/database >=8.80 -> satisfiable by illuminate/database[v8.80.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.64.0, v13.0.0, ..., v13.24.0]. - Root composer.json requires illuminate/filesystem >=8.80 -> satisfiable by illuminate/filesystem[v8.80.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.64.0, v13.0.0, ..., v13.24.0]. - illuminate/database[v10.0.0, ..., v10.49.0] require illuminate/support ^10.0 -> satisfiable by illuminate/support[v10.0.0, ..., v10.49.0]. - illuminate/database[v11.0.0, ..., v11.51.0] require illuminate/macroable ^11.0 -> satisfiable by illuminate/macroable[v11.0.0, ..., v11.51.0]. - illuminate/database[v12.0.0, ..., v12.64.0] require illuminate/macroable ^12.0 -> satisfiable by illuminate/macroable[v12.0.0, ..., v12.64.0]. - illuminate/database[v13.0.0, ..., v13.24.0] require laravel/serializable-closure ^2.0.10 -> found laravel/serializable-closure[v2.0.10, ..., v2.0.15] but it conflicts with your root composer.json require (^1.3). - illuminate/database[v8.80.0, ..., v8.83.27] require symfony/console ^5.4 -> found symfony/console[v5.4.0, ..., v5.4.47] but these were not loaded, likely because it conflicts with another require. - illuminate/database[v9.0.0, ..., v9.34.0] require symfony/console ^6.0 -> found symfony/console[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - illuminate/database[v9.35.0, ..., v9.52.16] require symfony/console ^6.0.9 -> found symfony/console[v6.0.9, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - illuminate/support[v10.0.0, ..., v10.16.1] require nesbot/carbon ^2.62.1 -> satisfiable by nesbot/carbon[2.72.6, 2.73.0]. - illuminate/support[v10.17.0, ..., v10.49.0] require nesbot/carbon ^2.67 -> satisfiable by nesbot/carbon[2.72.6, 2.73.0]. - nesbot/carbon[2.72.6, ..., 2.73.0] require symfony/translation ^3.4 || ^4.0 || ^5.0 || ^6.0 -> found symfony/translation[v3.4.0, ..., v3.4.47, v4.0.0, ..., v4.4.47, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.42] but these were not loaded, likely because it conflicts with another require. - Conclusion: install illuminate/macroable v13.0.0 (conflict analysis result) - You can only install one version of a package, so only one of these can be installed: illuminate/macroable[v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.49.0, v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.64.0, v13.0.0, ..., v13.24.0].

Process completed with exit code 2.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires wouterj/eloquent-bundle * -> satisfiable by wouterj/eloquent-bundle[v0.1.0, ..., 0.5.0, 1.0.0, ..., 1.1.0, 2.0.0, ..., 2.8.1]. - illuminate/database[v4.1.29, ..., v4.1.30] require nesbot/carbon 1.* -> found nesbot/carbon[1.0.0, ..., 1.39.1] but these were not loaded, because they are affected by security advisories ("�]8;;https://github.com/advisories/GHSA-j3f9-p6hm-5w6q�\PKSA-csyb-yc4p-mnbs�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false. - wouterj/eloquent-bundle v0.1.0 requires illuminate/database ~4.1.4 -> satisfiable by illuminate/database[v4.1.29, v4.1.30]. - wouterj/eloquent-bundle[0.2.0, ..., 0.3.0] require php ^5.5|^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[0.4.0, ..., 0.5.0] require php ^5.6.4|^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[1.0.0, ..., 1.0.3] require php ^7.0 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle 1.1.0 requires php ^7.1 -> your php version (8.5.9) does not satisfy that requirement. - wouterj/eloquent-bundle[2.0.0, ..., 2.1.1] require symfony/framework-bundle ^4.4 || ^5.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.2.0, ..., 2.3.1] require symfony/framework-bundle ^4.4 || ^5.0 || ^6.0 -> found symfony/framework-bundle[v4.4.0, ..., v4.4.51, v5.0.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.4.0, ..., 2.5.0] require symfony/framework-bundle ^5.4 || ^6.0 -> found symfony/framework-bundle[v5.4.0, ..., v5.4.45, v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle 2.6.0 requires symfony/framework-bundle ^6.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43] but these were not loaded, likely because it conflicts with another require. - wouterj/eloquent-bundle[2.7.0, ..., 2.8.1] require symfony/framework-bundle ^6.0 || ^7.0 -> found symfony/framework-bundle[v6.0.0, ..., v6.4.43, v7.0.0, ..., v7.4.15] but these were not loaded, likely because it conflicts with another require.

Process completed with exit code 2.

Process completed with exit code 1.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/