Your requirements could not be resolved to an installable set of packages. Problem 1 - Conclusion: don't install sylius/resource-bundle v1.10.2 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.1 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.0 (conflict analysis result) - sylius/resource-bundle[v1.6.0, ..., v1.6.4] require php ^7.2 -> your php version (8.1.27) does not satisfy that requirement. - sylius/resource-bundle[v1.7.0, ..., v1.7.1] require php ^7.3 -> your php version (8.1.27) does not satisfy that requirement. - sylius/resource-bundle[v1.8.0, ..., v1.8.4] require symfony/expression-language ^4.4 || ^5.2 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.2.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - sylius/resource-bundle[v1.9.0, ..., v1.9.1] require symfony/expression-language ^4.4 || ^5.4 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.4.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - sylius/resource-bundle v1.10.3 requires symfony/form ^5.4 || ^6.0 -> satisfiable by symfony/form[v5.4.0, ..., v5.4.33, v6.4.0, v6.4.1]. - symfony/form[v5.4.21, ..., v5.4.33, v6.4.0, ..., v6.4.1] conflict with symfony/twig-bridge v6.1.0. - symfony/twig-bridge[v6.1.0, ..., v6.1.11] conflict with symfony/form <6.1. - symfony/twig-bundle[v6.1.0, ..., v6.1.11] require symfony/twig-bridge ^5.4|^6.0 -> satisfiable by symfony/twig-bridge[v6.1.0, ..., v6.1.11]. - sylius/resource-bundle v1.10.3 requires symfony/twig-bundle ^5.4 || ^6.0 -> satisfiable by symfony/twig-bundle[v6.1.0, v6.1.1, v6.1.9, v6.1.11]. - Root composer.json requires sylius/resource-bundle ^1.6 -> satisfiable by sylius/resource-bundle[v1.6.0, ..., v1.10.3].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Conclusion: don't install sylius/resource-bundle v1.10.1 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.2 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.3 (conflict analysis result) - sylius/resource-bundle[v1.6.0, ..., v1.6.4] require php ^7.2 -> your php version (8.2.14) does not satisfy that requirement. - sylius/resource-bundle[v1.7.0, ..., v1.7.1] require php ^7.3 -> your php version (8.2.14) does not satisfy that requirement. - sylius/resource-bundle[v1.8.0, ..., v1.8.4] require symfony/expression-language ^4.4 || ^5.2 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.2.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - sylius/resource-bundle[v1.9.0, ..., v1.9.1] require symfony/expression-language ^4.4 || ^5.4 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.4.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - sylius/resource-bundle v1.10.0 requires symfony/form ^5.4 || ^6.0 -> satisfiable by symfony/form[v5.4.0, ..., v5.4.33, v6.4.0, v6.4.1]. - symfony/form[v5.4.21, ..., v5.4.33, v6.4.0, ..., v6.4.1] conflict with symfony/twig-bridge v6.1.11. - symfony/twig-bridge[v6.1.0, ..., v6.1.11] conflict with symfony/form <6.1. - symfony/twig-bundle[v6.1.0, ..., v6.1.11] require symfony/twig-bridge ^5.4|^6.0 -> satisfiable by symfony/twig-bridge[v6.1.0, ..., v6.1.11]. - sylius/resource-bundle v1.10.0 requires symfony/twig-bundle ^5.4 || ^6.0 -> satisfiable by symfony/twig-bundle[v6.1.0, v6.1.1, v6.1.9, v6.1.11]. - Root composer.json requires sylius/resource-bundle ^1.6 -> satisfiable by sylius/resource-bundle[v1.6.0, ..., v1.10.3].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires symfony/form ^5.4 || ^6.4 -> satisfiable by symfony/form[v5.4.0, ..., v5.4.33, v6.4.0, v6.4.1]. - Conclusion: don't install sylius/resource-bundle v1.10.3 (conflict analysis result) - sylius/resource-bundle[v1.6.0, ..., v1.6.4] require php ^7.2 -> your php version (8.1.27) does not satisfy that requirement. - sylius/resource-bundle[v1.7.0, ..., v1.7.1] require php ^7.3 -> your php version (8.1.27) does not satisfy that requirement. - sylius/resource-bundle[v1.8.0, ..., v1.8.4] require symfony/expression-language ^4.4 || ^5.2 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.2.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - sylius/resource-bundle[v1.9.0, ..., v1.9.1] require symfony/expression-language ^4.4 || ^5.4 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.4.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - sylius/resource-bundle[v1.10.0, ..., v1.10.2] require symfony/twig-bundle ^5.4 || ^6.0 -> satisfiable by symfony/twig-bundle[v6.2.0, ..., v6.2.7]. - Conclusion: don't install symfony/twig-bundle v6.2.7 (conflict analysis result) - Root composer.json requires sylius/resource-bundle ^1.6 -> satisfiable by sylius/resource-bundle[v1.6.0, ..., v1.10.3].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Conclusion: don't install sylius/resource-bundle v1.10.2 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.1 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.0 (conflict analysis result) - sylius/resource-bundle[v1.6.0, ..., v1.6.4] require php ^7.2 -> your php version (8.2.14) does not satisfy that requirement. - sylius/resource-bundle[v1.7.0, ..., v1.7.1] require php ^7.3 -> your php version (8.2.14) does not satisfy that requirement. - sylius/resource-bundle[v1.8.0, ..., v1.8.4] require symfony/expression-language ^4.4 || ^5.2 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.2.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - sylius/resource-bundle[v1.9.0, ..., v1.9.1] require symfony/expression-language ^4.4 || ^5.4 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.4.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - sylius/resource-bundle v1.10.3 requires symfony/form ^5.4 || ^6.0 -> satisfiable by symfony/form[v5.4.0, ..., v5.4.33, v6.4.0, v6.4.1]. - symfony/form[v5.4.21, ..., v5.4.33, v6.4.0, ..., v6.4.1] conflict with symfony/twig-bridge v6.1.0. - symfony/twig-bridge[v6.1.0, ..., v6.1.11] conflict with symfony/form <6.1. - symfony/twig-bundle[v6.1.0, ..., v6.1.11] require symfony/twig-bridge ^5.4|^6.0 -> satisfiable by symfony/twig-bridge[v6.1.0, ..., v6.1.11]. - sylius/resource-bundle v1.10.3 requires symfony/twig-bundle ^5.4 || ^6.0 -> satisfiable by symfony/twig-bundle[v6.1.0, v6.1.1, v6.1.9, v6.1.11]. - Root composer.json requires sylius/resource-bundle ^1.6 -> satisfiable by sylius/resource-bundle[v1.6.0, ..., v1.10.3].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - setono/job-status-bundle v0.2.3 requires symfony/config ^4.4 || ^5.0 -> found symfony/config[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.31] but these were not loaded, likely because it conflicts with another require. - doctrine/persistence[1.3.0, ..., 1.3.7, 2.0.0] require php ^7.1 -> your php version (8.2.14) does not satisfy that requirement. - Root composer.json requires doctrine/orm ^2.7 -> satisfiable by doctrine/orm[v2.7.0, ..., 2.17.4]. - Conclusion: don't install doctrine/persistence 2.5.2 (conflict analysis result) - doctrine/persistence[2.2.1, ..., 2.5.1] require doctrine/deprecations ^0.5.3 -> satisfiable by doctrine/deprecations[v0.5.3]. - You can only install one version of a package, so only one of these can be installed: doctrine/deprecations[v0.5.3, v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - doctrine/lexer[2.0.0, ..., 2.1.0] require doctrine/deprecations ^1.0 -> satisfiable by doctrine/deprecations[v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - Conclusion: install doctrine/lexer 2.0.0 (conflict analysis result) - Conclusion: install symfony/doctrine-bridge v6.4.0 (conflict analysis result) - Root composer.json requires setono/job-status-bundle ^0.2.3 -> satisfiable by setono/job-status-bundle[v0.2.3, v0.2.4, v0.2.5]. - setono/job-status-bundle[v0.2.4, ..., v0.2.5] require doctrine/persistence ^1.3 || ^2.0 -> satisfiable by doctrine/persistence[1.3.0, ..., 1.3.8, 2.0.0, ..., 2.5.7]. - You can only install one version of a package, so only one of these can be installed: doctrine/persistence[v1.0.0, ..., 1.3.8, 2.0.0, ..., 2.5.7, 3.0.0, ..., 3.2.0]. - symfony/doctrine-bridge[v6.4.0, ..., v6.4.2] require doctrine/persistence ^3.1 -> satisfiable by doctrine/persistence[3.1.0, ..., 3.2.0]. - Conclusion: don't install doctrine/persistence 3.1.0 (conflict analysis result)

Process completed with exit code 2.

The job was canceled because "_8_1_lowest__6_1_0" failed.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Conclusion: don't install sylius/resource-bundle v1.10.2 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.1 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.0 (conflict analysis result) - sylius/resource-bundle[v1.6.0, ..., v1.6.4] require php ^7.2 -> your php version (8.2.14) does not satisfy that requirement. - sylius/resource-bundle[v1.7.0, ..., v1.7.1] require php ^7.3 -> your php version (8.2.14) does not satisfy that requirement. - sylius/resource-bundle[v1.8.0, ..., v1.8.4] require symfony/expression-language ^4.4 || ^5.2 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.2.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - sylius/resource-bundle[v1.9.0, ..., v1.9.1] require symfony/expression-language ^4.4 || ^5.4 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.4.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - symfony/twig-bundle[v6.2.0, ..., v6.2.7] require symfony/twig-bridge ^6.2 -> satisfiable by symfony/twig-bridge[v6.2.0, ..., v6.2.13]. - symfony/form[v6.4.0, ..., v6.4.1] conflict with symfony/twig-bridge v6.2.7. - symfony/form[v6.4.0, ..., v6.4.1] conflict with symfony/twig-bridge v6.2.1. - symfony/form[v6.4.0, ..., v6.4.1] conflict with symfony/twig-bridge v6.2.0. - sylius/resource-bundle v1.10.3 requires symfony/form ^5.4 || ^6.0 -> satisfiable by symfony/form[v5.4.0, ..., v5.4.33, v6.4.0, v6.4.1]. - Conclusion: don't install one of symfony/twig-bundle[v6.2.0], symfony/form[v5.4.0] (conflict analysis result) - Conclusion: don't install one of symfony/twig-bundle[v6.2.0], symfony/form[v5.4.21] (conflict analysis result) - Conclusion: don't install one of symfony/twig-bundle[v6.2.0], symfony/form[v5.4.24] (conflict analysis result) - sylius/resource-bundle v1.10.3 requires symfony/twig-bundle ^5.4 || ^6.0 -> satisfiable by symfony/twig-bundle[v6.2.0, ..., v6.2.7]. - Root composer.json requires sylius/resource-bundle ^1.6 -> satisfiable by sylius/resource-bundle[v1.6.0, ..., v1.10.3].

Process completed with exit code 2.

The job was canceled because "_8_1_lowest__6_1_0" failed.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Conclusion: don't install sylius/resource-bundle v1.10.1 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.2 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.3 (conflict analysis result) - sylius/resource-bundle[v1.6.0, ..., v1.6.4] require php ^7.2 -> your php version (8.1.27) does not satisfy that requirement. - sylius/resource-bundle[v1.7.0, ..., v1.7.1] require php ^7.3 -> your php version (8.1.27) does not satisfy that requirement. - sylius/resource-bundle[v1.8.0, ..., v1.8.4] require symfony/expression-language ^4.4 || ^5.2 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.2.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - sylius/resource-bundle[v1.9.0, ..., v1.9.1] require symfony/expression-language ^4.4 || ^5.4 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.4.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - sylius/resource-bundle v1.10.0 requires symfony/form ^5.4 || ^6.0 -> satisfiable by symfony/form[v5.4.0, ..., v5.4.33, v6.4.0, v6.4.1]. - symfony/form[v5.4.21, ..., v5.4.33, v6.4.0, ..., v6.4.1] conflict with symfony/twig-bridge v6.1.11. - symfony/twig-bridge[v6.1.0, ..., v6.1.11] conflict with symfony/form <6.1. - symfony/twig-bundle[v6.1.0, ..., v6.1.11] require symfony/twig-bridge ^5.4|^6.0 -> satisfiable by symfony/twig-bridge[v6.1.0, ..., v6.1.11]. - sylius/resource-bundle v1.10.0 requires symfony/twig-bundle ^5.4 || ^6.0 -> satisfiable by symfony/twig-bundle[v6.1.0, v6.1.1, v6.1.9, v6.1.11]. - Root composer.json requires sylius/resource-bundle ^1.6 -> satisfiable by sylius/resource-bundle[v1.6.0, ..., v1.10.3].

Process completed with exit code 2.

The operation was canceled.

The operation was canceled.

The job was canceled because "_8_1_lowest__6_1_0" failed.

The operation was canceled.

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - setono/job-status-bundle v0.2.3 requires symfony/config ^4.4 || ^5.0 -> found symfony/config[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.31] but these were not loaded, likely because it conflicts with another require. - doctrine/doctrine-bundle[1.12.0, ..., 1.12.9] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement. - doctrine/doctrine-bundle[1.12.10, ..., 1.12.13] require symfony/cache ^3.4.30|^4.3.3 -> found symfony/cache[v3.4.30, ..., v3.4.47, v4.3.3, ..., v4.4.48] but these were not loaded, likely because it conflicts with another require. - doctrine/doctrine-bundle[2.1.1, ..., 2.3.2] require symfony/cache ^4.3.3|^5.0 -> found symfony/cache[v4.3.3, ..., v4.4.48, v5.0.0, ..., v5.4.34] but these were not loaded, likely because it conflicts with another require. - doctrine/doctrine-bundle[2.8.0, ..., 2.8.3] require doctrine/dbal ^3.4.0 -> found doctrine/dbal[3.4.0, ..., 3.8.0] but it conflicts with your root composer.json require (^2.13). - doctrine/doctrine-bundle[2.9.0, ..., 2.10.3] require doctrine/dbal ^3.6.0 -> found doctrine/dbal[3.6.0, ..., 3.8.0] but it conflicts with your root composer.json require (^2.13). - doctrine/doctrine-bundle[2.11.0, ..., 2.11.1] require doctrine/dbal ^3.7.0 || ^4.0 -> found doctrine/dbal[3.7.0, ..., 3.8.0] but it conflicts with your root composer.json require (^2.13). - Root composer.json requires setono/job-status-bundle ^0.2.3 -> satisfiable by setono/job-status-bundle[v0.2.3, v0.2.4, v0.2.5]. - setono/job-status-bundle[v0.2.4, ..., v0.2.5] require doctrine/doctrine-bundle ^1.12 || ^2.3 -> satisfiable by doctrine/doctrine-bundle[1.12.0, ..., 1.12.13, 2.3.0, ..., 2.11.1]. - doctrine/doctrine-bundle[2.7.1, ..., 2.7.2] require symfony/doctrine-bridge ^4.4.22 || ^5.4 || ^6.0 -> satisfiable by symfony/doctrine-bridge[v6.4.0, v6.4.2]. - doctrine/doctrine-bundle[2.4.0, ..., 2.7.0] require symfony/doctrine-bridge ^4.4.22|^5.2.7|^6.0 -> satisfiable by symfony/doctrine-bridge[v6.4.0, v6.4.2]. - Conclusion: don't install symfony/doctrine-bridge v6.4.2 (conflict analysis result)

Process completed with exit code 2.

The operation was canceled.

The operation was canceled.

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - setono/job-status-bundle v0.2.3 requires symfony/config ^4.4 || ^5.0 -> found symfony/config[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.31] but these were not loaded, likely because it conflicts with another require. - doctrine/persistence[1.3.0, ..., 1.3.7, 2.0.0] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement. - Root composer.json requires doctrine/orm ^2.7 -> satisfiable by doctrine/orm[v2.7.0, ..., 2.17.4]. - Conclusion: don't install doctrine/persistence 2.5.2 (conflict analysis result) - doctrine/persistence[2.2.1, ..., 2.5.1] require doctrine/deprecations ^0.5.3 -> satisfiable by doctrine/deprecations[v0.5.3]. - You can only install one version of a package, so only one of these can be installed: doctrine/deprecations[v0.5.3, v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - doctrine/lexer[2.0.0, ..., 2.1.0] require doctrine/deprecations ^1.0 -> satisfiable by doctrine/deprecations[v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - Conclusion: install doctrine/lexer 2.0.0 (conflict analysis result) - Conclusion: install symfony/doctrine-bridge v6.4.0 (conflict analysis result) - Root composer.json requires setono/job-status-bundle ^0.2.3 -> satisfiable by setono/job-status-bundle[v0.2.3, v0.2.4, v0.2.5]. - setono/job-status-bundle[v0.2.4, ..., v0.2.5] require doctrine/persistence ^1.3 || ^2.0 -> satisfiable by doctrine/persistence[1.3.0, ..., 1.3.8, 2.0.0, ..., 2.5.7]. - You can only install one version of a package, so only one of these can be installed: doctrine/persistence[v1.0.0, ..., 1.3.8, 2.0.0, ..., 2.5.7, 3.0.0, ..., 3.2.0]. - symfony/doctrine-bridge[v6.4.0, ..., v6.4.2] require doctrine/persistence ^3.1 -> satisfiable by doctrine/persistence[3.1.0, ..., 3.2.0]. - Conclusion: don't install doctrine/persistence 3.1.0 (conflict analysis result)

Process completed with exit code 2.

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - setono/job-status-bundle v0.2.3 requires symfony/config ^4.4 || ^5.0 -> found symfony/config[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.31] but these were not loaded, likely because it conflicts with another require. - doctrine/doctrine-bundle[1.12.0, ..., 1.12.9] require php ^7.1 -> your php version (8.2.14) does not satisfy that requirement. - doctrine/doctrine-bundle[1.12.10, ..., 1.12.13] require symfony/cache ^3.4.30|^4.3.3 -> found symfony/cache[v3.4.30, ..., v3.4.47, v4.3.3, ..., v4.4.48] but these were not loaded, likely because it conflicts with another require. - doctrine/doctrine-bundle[2.1.1, ..., 2.3.2] require symfony/cache ^4.3.3|^5.0 -> found symfony/cache[v4.3.3, ..., v4.4.48, v5.0.0, ..., v5.4.34] but these were not loaded, likely because it conflicts with another require. - doctrine/doctrine-bundle[2.8.0, ..., 2.8.3] require doctrine/dbal ^3.4.0 -> found doctrine/dbal[3.4.0, ..., 3.8.0] but it conflicts with your root composer.json require (^2.13). - doctrine/doctrine-bundle[2.9.0, ..., 2.10.3] require doctrine/dbal ^3.6.0 -> found doctrine/dbal[3.6.0, ..., 3.8.0] but it conflicts with your root composer.json require (^2.13). - doctrine/doctrine-bundle[2.11.0, ..., 2.11.1] require doctrine/dbal ^3.7.0 || ^4.0 -> found doctrine/dbal[3.7.0, ..., 3.8.0] but it conflicts with your root composer.json require (^2.13). - Root composer.json requires setono/job-status-bundle ^0.2.3 -> satisfiable by setono/job-status-bundle[v0.2.3, v0.2.4, v0.2.5]. - setono/job-status-bundle[v0.2.4, ..., v0.2.5] require doctrine/doctrine-bundle ^1.12 || ^2.3 -> satisfiable by doctrine/doctrine-bundle[1.12.0, ..., 1.12.13, 2.3.0, ..., 2.11.1]. - doctrine/doctrine-bundle[2.7.1, ..., 2.7.2] require symfony/doctrine-bridge ^4.4.22 || ^5.4 || ^6.0 -> satisfiable by symfony/doctrine-bridge[v6.4.0, v6.4.2]. - doctrine/doctrine-bundle[2.4.0, ..., 2.7.0] require symfony/doctrine-bridge ^4.4.22|^5.2.7|^6.0 -> satisfiable by symfony/doctrine-bridge[v6.4.0, v6.4.2]. - Conclusion: don't install symfony/doctrine-bridge v6.4.2 (conflict analysis result)

The operation was canceled.

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Conclusion: don't install sylius/resource-bundle v1.10.2 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.1 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.0 (conflict analysis result) - sylius/resource-bundle[v1.6.0, ..., v1.6.4] require php ^7.2 -> your php version (8.1.27) does not satisfy that requirement. - sylius/resource-bundle[v1.7.0, ..., v1.7.1] require php ^7.3 -> your php version (8.1.27) does not satisfy that requirement. - sylius/resource-bundle[v1.8.0, ..., v1.8.4] require symfony/expression-language ^4.4 || ^5.2 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.2.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - sylius/resource-bundle[v1.9.0, ..., v1.9.1] require symfony/expression-language ^4.4 || ^5.4 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.4.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - symfony/twig-bundle[v6.2.0, ..., v6.2.7] require symfony/twig-bridge ^6.2 -> satisfiable by symfony/twig-bridge[v6.2.0, ..., v6.2.13]. - symfony/form[v6.4.0, ..., v6.4.1] conflict with symfony/twig-bridge v6.2.7. - symfony/form[v6.4.0, ..., v6.4.1] conflict with symfony/twig-bridge v6.2.1. - symfony/form[v6.4.0, ..., v6.4.1] conflict with symfony/twig-bridge v6.2.0. - sylius/resource-bundle v1.10.3 requires symfony/form ^5.4 || ^6.0 -> satisfiable by symfony/form[v5.4.0, ..., v5.4.33, v6.4.0, v6.4.1]. - Conclusion: don't install one of symfony/twig-bundle[v6.2.0], symfony/form[v5.4.0] (conflict analysis result) - Conclusion: don't install one of symfony/twig-bundle[v6.2.0], symfony/form[v5.4.21] (conflict analysis result) - Conclusion: don't install one of symfony/twig-bundle[v6.2.0], symfony/form[v5.4.24] (conflict analysis result) - sylius/resource-bundle v1.10.3 requires symfony/twig-bundle ^5.4 || ^6.0 -> satisfiable by symfony/twig-bundle[v6.2.0, ..., v6.2.7]. - Root composer.json requires sylius/resource-bundle ^1.6 -> satisfiable by sylius/resource-bundle[v1.6.0, ..., v1.10.3].

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/framework-bundle[v6.1.0, ..., v6.1.11] require symfony/dependency-injection ^6.1 -> satisfiable by symfony/dependency-injection[v6.4.0, v6.4.1, v6.4.2]. - symfony/dependency-injection[v6.4.0, ..., v6.4.2] conflict with symfony/proxy-manager-bridge v6.1.11. - sylius/sylius v1.12.13 requires symfony/framework-bundle ^5.4 || ^6.0 -> satisfiable by symfony/framework-bundle[v6.1.0, ..., v6.1.11]. - sylius/sylius v1.12.13 requires symfony/proxy-manager-bridge ^5.4 || ^6.0 -> satisfiable by symfony/proxy-manager-bridge[v6.1.0, v6.1.11]. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Conclusion: don't install sylius/resource-bundle v1.10.2 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.1 (conflict analysis result) - Conclusion: don't install sylius/resource-bundle v1.10.0 (conflict analysis result) - sylius/resource-bundle[v1.6.0, ..., v1.6.4] require php ^7.2 -> your php version (8.1.27) does not satisfy that requirement. - sylius/resource-bundle[v1.7.0, ..., v1.7.1] require php ^7.3 -> your php version (8.1.27) does not satisfy that requirement. - sylius/resource-bundle[v1.8.0, ..., v1.8.4] require symfony/expression-language ^4.4 || ^5.2 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.2.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - sylius/resource-bundle[v1.9.0, ..., v1.9.1] require symfony/expression-language ^4.4 || ^5.4 -> found symfony/expression-language[v4.4.0, ..., v4.4.47, v5.4.0, ..., v5.4.21] but these were not loaded, likely because it conflicts with another require. - symfony/twig-bundle[v6.2.0, ..., v6.2.7] require symfony/twig-bridge ^6.2 -> satisfiable by symfony/twig-bridge[v6.2.0, ..., v6.2.13]. - symfony/form[v6.4.0, ..., v6.4.1] conflict with symfony/twig-bridge v6.2.7. - symfony/form[v6.4.0, ..., v6.4.1] conflict with symfony/twig-bridge v6.2.1. - symfony/form[v6.4.0, ..., v6.4.1] conflict with symfony/twig-bridge v6.2.0. - sylius/resource-bundle v1.10.3 requires symfony/form ^5.4 || ^6.0 -> satisfiable by symfony/form[v5.4.0, ..., v5.4.33, v6.4.0, v6.4.1]. - Conclusion: don't install one of symfony/twig-bundle[v6.2.0], symfony/form[v5.4.0] (conflict analysis result) - Conclusion: don't install one of symfony/twig-bundle[v6.2.0], symfony/form[v5.4.21] (conflict analysis result) - Conclusion: don't install one of symfony/twig-bundle[v6.2.0], symfony/form[v5.4.24] (conflict analysis result) - sylius/resource-bundle v1.10.3 requires symfony/twig-bundle ^5.4 || ^6.0 -> satisfiable by symfony/twig-bundle[v6.2.0, ..., v6.2.7]. - Root composer.json requires sylius/resource-bundle ^1.6 -> satisfiable by sylius/resource-bundle[v1.6.0, ..., v1.10.3].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - setono/job-status-bundle v0.2.3 requires symfony/config ^4.4 || ^5.0 -> found symfony/config[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.31] but these were not loaded, likely because it conflicts with another require. - doctrine/doctrine-bundle[1.12.0, ..., 1.12.9] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement. - doctrine/doctrine-bundle[1.12.10, ..., 1.12.13] require symfony/cache ^3.4.30|^4.3.3 -> found symfony/cache[v3.4.30, ..., v3.4.47, v4.3.3, ..., v4.4.48] but these were not loaded, likely because it conflicts with another require. - doctrine/doctrine-bundle[2.1.1, ..., 2.3.2] require symfony/cache ^4.3.3|^5.0 -> found symfony/cache[v4.3.3, ..., v4.4.48, v5.0.0, ..., v5.4.34] but these were not loaded, likely because it conflicts with another require. - doctrine/doctrine-bundle[2.8.0, ..., 2.8.3] require doctrine/dbal ^3.4.0 -> found doctrine/dbal[3.4.0, ..., 3.8.0] but it conflicts with your root composer.json require (^2.13). - doctrine/doctrine-bundle[2.9.0, ..., 2.10.3] require doctrine/dbal ^3.6.0 -> found doctrine/dbal[3.6.0, ..., 3.8.0] but it conflicts with your root composer.json require (^2.13). - doctrine/doctrine-bundle[2.11.0, ..., 2.11.1] require doctrine/dbal ^3.7.0 || ^4.0 -> found doctrine/dbal[3.7.0, ..., 3.8.0] but it conflicts with your root composer.json require (^2.13). - Root composer.json requires setono/job-status-bundle ^0.2.3 -> satisfiable by setono/job-status-bundle[v0.2.3, v0.2.4, v0.2.5]. - setono/job-status-bundle[v0.2.4, ..., v0.2.5] require doctrine/doctrine-bundle ^1.12 || ^2.3 -> satisfiable by doctrine/doctrine-bundle[1.12.0, ..., 1.12.13, 2.3.0, ..., 2.11.1]. - doctrine/doctrine-bundle[2.7.1, ..., 2.7.2] require symfony/doctrine-bridge ^4.4.22 || ^5.4 || ^6.0 -> satisfiable by symfony/doctrine-bridge[v6.4.0, v6.4.2]. - doctrine/doctrine-bundle[2.4.0, ..., 2.7.0] require symfony/doctrine-bridge ^4.4.22|^5.2.7|^6.0 -> satisfiable by symfony/doctrine-bridge[v6.4.0, v6.4.2]. - Conclusion: don't install symfony/doctrine-bridge v6.4.2 (conflict analysis result)

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/dependency-injection[v6.4.0, ..., v6.4.2] conflict with symfony/proxy-manager-bridge v6.2.7. - symfony/twig-bundle[v6.2.0, ..., v6.2.7] require symfony/dependency-injection ^6.1 -> satisfiable by symfony/dependency-injection[v6.4.0, v6.4.1, v6.4.2]. - sylius/sylius v1.12.13 requires symfony/proxy-manager-bridge ^5.4 || ^6.0 -> satisfiable by symfony/proxy-manager-bridge[v6.2.0, v6.2.5, v6.2.7]. - sylius/sylius v1.12.13 requires symfony/twig-bundle ^5.4 || ^6.0 -> satisfiable by symfony/twig-bundle[v6.2.0, ..., v6.2.7]. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13].

Process completed with exit code 2.

The job was canceled because "_8_2_highest__6_1_0" failed.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires symfony/form ^5.4 || ^6.4 -> satisfiable by symfony/form[v5.4.0, ..., v5.4.33, v6.4.0, v6.4.1]. - symfony/web-profiler-bundle[v6.4.0, ..., v6.4.2] require symfony/framework-bundle ^6.4|^7.0 -> found symfony/framework-bundle[v6.4.0, v6.4.1, v6.4.2, v7.0.0, v7.0.1, v7.0.2] but these were not loaded, likely because it conflicts with another require. - symfony/web-profiler-bundle[v5.4.0, ..., v5.4.34] require symfony/twig-bundle ^4.4|^5.0|^6.0 -> satisfiable by symfony/twig-bundle[v6.2.0, ..., v6.2.7]. - Conclusion: don't install symfony/twig-bundle v6.2.7 (conflict analysis result) - Root composer.json requires symfony/web-profiler-bundle ^5.4 || ^6.4 -> satisfiable by symfony/web-profiler-bundle[v5.4.0, ..., v5.4.34, v6.4.0, v6.4.2].

Process completed with exit code 2.

The job was canceled because "_8_1_lowest__6_2_0" failed.

Your requirements could not be resolved to an installable set of packages. Problem 1 - setono/sylius-behat-pack v0.2.1 requires symfony/browser-kit ^4.4 -> found symfony/browser-kit[v4.4.0, ..., v4.4.44] but these were not loaded, likely because it conflicts with another require. - friends-of-behat/symfony-extension[v2.2.0, ..., v2.2.1] require symfony/http-kernel ^4.4 || ^5.1 -> found symfony/http-kernel[v4.4.0, ..., v4.4.51, v5.1.0, ..., v5.4.34] but these were not loaded, likely because it conflicts with another require. - friends-of-behat/symfony-extension v2.5.0 requires symfony/http-kernel ^6.2 || ^7.0 -> found symfony/http-kernel[v6.2.0, ..., v6.4.2, v7.0.0, v7.0.1, v7.0.2] but these were not loaded, likely because it conflicts with another require. - setono/job-status-bundle v0.2.3 requires symfony/event-dispatcher ^4.4 || ^5.0 -> found symfony/event-dispatcher[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.34] but these were not loaded, likely because it conflicts with another require. - Root composer.json requires setono/job-status-bundle ^0.2.3 -> satisfiable by setono/job-status-bundle[v0.2.3, v0.2.4, v0.2.5]. - setono/sylius-behat-pack v0.2.2 requires friends-of-behat/symfony-extension ^2.2 -> satisfiable by friends-of-behat/symfony-extension[v2.2.0, ..., v2.5.0]. - friends-of-behat/symfony-extension[v2.3.1, ..., v2.4.2] require symfony/proxy-manager-bridge ^4.4 || ^5.3 || ^6.0 -> satisfiable by symfony/proxy-manager-bridge[v6.1.0, v6.1.11]. - friends-of-behat/symfony-extension v2.3.0 requires symfony/proxy-manager-bridge ^4.4 || ^5.1 || ^6.0 -> satisfiable by symfony/proxy-manager-bridge[v6.1.0, v6.1.11]. - symfony/dependency-injection[v6.4.0, ..., v6.4.2] conflict with symfony/proxy-manager-bridge v6.1.11. - setono/job-status-bundle[v0.2.4, ..., v0.2.5] require symfony/dependency-injection ^5.4 || ^6.0 -> satisfiable by symfony/dependency-injection[v5.4.0, ..., v5.4.34, v6.4.0, v6.4.1, v6.4.2]. - symfony/http-kernel[v6.1.0, ..., v6.1.12] conflict with symfony/dependency-injection <6.1. - setono/job-status-bundle[v0.2.4, ..., v0.2.5] require symfony/http-kernel ^5.4 || ^6.0 -> satisfiable by symfony/http-kernel[v6.1.0, ..., v6.1.12]. - Root composer.json requires setono/sylius-behat-pack ^0.2.1 -> satisfiable by setono/sylius-behat-pack[v0.2.1, v0.2.2].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/dependency-injection[v6.4.0, ..., v6.4.2] conflict with symfony/proxy-manager-bridge v6.2.7. - symfony/twig-bundle[v6.2.0, ..., v6.2.7] require symfony/dependency-injection ^6.1 -> satisfiable by symfony/dependency-injection[v6.4.0, v6.4.1, v6.4.2]. - sylius/sylius v1.12.13 requires symfony/proxy-manager-bridge ^5.4 || ^6.0 -> satisfiable by symfony/proxy-manager-bridge[v6.2.0, v6.2.5, v6.2.7]. - sylius/sylius v1.12.13 requires symfony/twig-bundle ^5.4 || ^6.0 -> satisfiable by symfony/twig-bundle[v6.2.0, ..., v6.2.7]. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13].

The operation was canceled.

The job was canceled because "_8_2_highest__6_1_0" failed.

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/dependency-injection[v6.4.0, ..., v6.4.2] conflict with symfony/proxy-manager-bridge v6.2.0. - symfony/twig-bundle[v6.2.0, ..., v6.2.7] require symfony/dependency-injection ^6.1 -> satisfiable by symfony/dependency-injection[v6.4.0, v6.4.1, v6.4.2]. - sylius/sylius v1.12.13 requires symfony/proxy-manager-bridge ^5.4 || ^6.0 -> satisfiable by symfony/proxy-manager-bridge[v6.2.0, v6.2.5, v6.2.7]. - sylius/sylius v1.12.13 requires symfony/twig-bundle ^5.4 || ^6.0 -> satisfiable by symfony/twig-bundle[v6.2.0, ..., v6.2.7]. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/framework-bundle[v6.1.0, ..., v6.1.11] require symfony/dependency-injection ^6.1 -> satisfiable by symfony/dependency-injection[v6.4.0, v6.4.1, v6.4.2]. - symfony/dependency-injection[v6.4.0, ..., v6.4.2] conflict with symfony/proxy-manager-bridge v6.1.11. - sylius/sylius v1.12.13 requires symfony/framework-bundle ^5.4 || ^6.0 -> satisfiable by symfony/framework-bundle[v6.1.0, ..., v6.1.11]. - sylius/sylius v1.12.13 requires symfony/proxy-manager-bridge ^5.4 || ^6.0 -> satisfiable by symfony/proxy-manager-bridge[v6.1.0, v6.1.11]. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13].

Process completed with exit code 2.

The job was canceled because "_8_1_lowest__6_2_0" failed.

The operation was canceled.

Process completed with exit code 1.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/framework-bundle[v6.1.0, ..., v6.1.11] require symfony/dependency-injection ^6.1 -> satisfiable by symfony/dependency-injection[v6.4.0, v6.4.1, v6.4.2]. - symfony/dependency-injection[v6.4.0, ..., v6.4.2] conflict with symfony/proxy-manager-bridge v6.1.0. - sylius/sylius v1.12.13 requires symfony/framework-bundle ^5.4 || ^6.0 -> satisfiable by symfony/framework-bundle[v6.1.0, ..., v6.1.11]. - sylius/sylius v1.12.13 requires symfony/proxy-manager-bridge ^5.4 || ^6.0 -> satisfiable by symfony/proxy-manager-bridge[v6.1.0, v6.1.11]. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13].

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - sylius-labs/association-hydrator[v1.1.0, ..., v1.1.1] require php ^7.1 -> your php version (8.2.14) does not satisfy that requirement. - doctrine/persistence[1.3.0, ..., 1.3.7, 2.0.0] require php ^7.1 -> your php version (8.2.14) does not satisfy that requirement. - doctrine/orm[v2.7.0, ..., 2.7.5] require php ^7.1 -> your php version (8.2.14) does not satisfy that requirement. - sylius-labs/association-hydrator[v1.1.2, ..., v1.1.3] require php ^7.2 -> your php version (8.2.14) does not satisfy that requirement. - sylius-labs/association-hydrator v1.1.4 requires symfony/property-access ^3.4|^4.4|^5.0 -> found symfony/property-access[v3.4.0, ..., v3.4.47, v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.26] but these were not loaded, likely because it conflicts with another require. - setono/job-status-bundle v0.2.3 requires symfony/config ^4.4 || ^5.0 -> found symfony/config[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.31] but these were not loaded, likely because it conflicts with another require. - doctrine/orm[2.8.0, ..., 2.8.4] require symfony/console ^3.0|^4.0|^5.0 -> found symfony/console[v3.0.0, ..., v3.4.47, v4.0.0, ..., v4.4.49, v5.0.0, ..., v5.4.34] but these were not loaded, likely because it conflicts with another require. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13]. - Conclusion: don't install doctrine/persistence 2.5.7 (conflict analysis result) - doctrine/persistence[2.2.1, ..., 2.5.1] require doctrine/deprecations ^0.5.3 -> satisfiable by doctrine/deprecations[v0.5.3]. - You can only install one version of a package, so only one of these can be installed: doctrine/deprecations[v0.5.3, v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - doctrine/lexer[2.0.0, ..., 2.1.0] require doctrine/deprecations ^1.0 -> satisfiable by doctrine/deprecations[v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - doctrine/orm[2.15.0, ..., 2.15.5] require doctrine/lexer ^2 -> satisfiable by doctrine/lexer[2.0.0, 2.1.0]. - sylius-labs/association-hydrator v1.2.0 requires doctrine/orm ^2.4 -> satisfiable by doctrine/orm[v2.7.0, ..., 2.17.4]. - symfony/doctrine-bridge[v6.4.0, ..., v6.4.2] conflict with doctrine/orm <2.15. - sylius/sylius v1.12.13 requires sylius-labs/association-hydrator ^1.1 || ^1.2 -> satisfiable by sylius-labs/association-hydrator[v1.1.0, ..., v1.2.0]. - sylius/sylius v1.12.13 requires symfony/doctrine-bridge ^5.4 || ^6.0 -> satisfiable by symfony/doctrine-bridge[v6.4.0, v6.4.2]. - sylius/sylius v1.12.13 conflicts with doctrine/orm >= 2.16.0. - Root composer.json requires setono/job-status-bundle ^0.2.3 -> satisfiable by setono/job-status-bundle[v0.2.3, v0.2.4, v0.2.5]. - setono/job-status-bundle[v0.2.4, ..., v0.2.5] require doctrine/persistence ^1.3 || ^2.0 -> satisfiable by doctrine/persistence[1.3.0, ..., 1.3.8, 2.0.0, ..., 2.5.7]. - You can only install one version of a package, so only one of these can be installed: doctrine/persistence[v1.0.0, ..., 1.3.8, 2.0.0, ..., 2.5.7, 3.0.0, ..., 3.2.0]. - symfony/doctrine-bridge[v6.4.0, ..., v6.4.2] require doctrine/persistence ^3.1 -> satisfiable by doctrine/persistence[3.1.0, ..., 3.2.0]. - Conclusion: don't install doctrine/persistence 3.2.0 (conflict analysis result)

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - sylius-labs/association-hydrator[v1.1.0, ..., v1.1.1] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement. - doctrine/persistence[1.3.0, ..., 1.3.7, 2.0.0] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement. - doctrine/orm[v2.7.0, ..., 2.7.5] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement. - sylius-labs/association-hydrator[v1.1.2, ..., v1.1.3] require php ^7.2 -> your php version (8.1.27) does not satisfy that requirement. - sylius-labs/association-hydrator v1.1.4 requires symfony/property-access ^3.4|^4.4|^5.0 -> found symfony/property-access[v3.4.0, ..., v3.4.47, v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.26] but these were not loaded, likely because it conflicts with another require. - setono/job-status-bundle v0.2.3 requires symfony/config ^4.4 || ^5.0 -> found symfony/config[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.31] but these were not loaded, likely because it conflicts with another require. - doctrine/orm[2.8.0, ..., 2.8.4] require symfony/console ^3.0|^4.0|^5.0 -> found symfony/console[v3.0.0, ..., v3.4.47, v4.0.0, ..., v4.4.49, v5.0.0, ..., v5.4.34] but these were not loaded, likely because it conflicts with another require. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13]. - Conclusion: don't install doctrine/persistence 2.5.7 (conflict analysis result) - doctrine/persistence[2.2.1, ..., 2.5.1] require doctrine/deprecations ^0.5.3 -> satisfiable by doctrine/deprecations[v0.5.3]. - You can only install one version of a package, so only one of these can be installed: doctrine/deprecations[v0.5.3, v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - doctrine/lexer[2.0.0, ..., 2.1.0] require doctrine/deprecations ^1.0 -> satisfiable by doctrine/deprecations[v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - doctrine/orm[2.15.0, ..., 2.15.5] require doctrine/lexer ^2 -> satisfiable by doctrine/lexer[2.0.0, 2.1.0]. - sylius-labs/association-hydrator v1.2.0 requires doctrine/orm ^2.4 -> satisfiable by doctrine/orm[v2.7.0, ..., 2.17.4]. - symfony/doctrine-bridge[v6.4.0, ..., v6.4.2] conflict with doctrine/orm <2.15. - sylius/sylius v1.12.13 requires sylius-labs/association-hydrator ^1.1 || ^1.2 -> satisfiable by sylius-labs/association-hydrator[v1.1.0, ..., v1.2.0]. - sylius/sylius v1.12.13 requires symfony/doctrine-bridge ^5.4 || ^6.0 -> satisfiable by symfony/doctrine-bridge[v6.4.0, v6.4.2]. - sylius/sylius v1.12.13 conflicts with doctrine/orm >= 2.16.0. - Root composer.json requires setono/job-status-bundle ^0.2.3 -> satisfiable by setono/job-status-bundle[v0.2.3, v0.2.4, v0.2.5]. - setono/job-status-bundle[v0.2.4, ..., v0.2.5] require doctrine/persistence ^1.3 || ^2.0 -> satisfiable by doctrine/persistence[1.3.0, ..., 1.3.8, 2.0.0, ..., 2.5.7]. - You can only install one version of a package, so only one of these can be installed: doctrine/persistence[v1.0.0, ..., 1.3.8, 2.0.0, ..., 2.5.7, 3.0.0, ..., 3.2.0]. - symfony/doctrine-bridge[v6.4.0, ..., v6.4.2] require doctrine/persistence ^3.1 -> satisfiable by doctrine/persistence[3.1.0, ..., 3.2.0]. - Conclusion: don't install doctrine/persistence 3.2.0 (conflict analysis result)

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - sylius-labs/association-hydrator[v1.1.0, ..., v1.1.1] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement. - doctrine/persistence[1.3.0, ..., 1.3.7, 2.0.0] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement. - doctrine/orm[v2.7.0, ..., 2.7.5] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement. - sylius-labs/association-hydrator[v1.1.2, ..., v1.1.3] require php ^7.2 -> your php version (8.1.27) does not satisfy that requirement. - sylius-labs/association-hydrator v1.1.4 requires symfony/property-access ^3.4|^4.4|^5.0 -> found symfony/property-access[v3.4.0, ..., v3.4.47, v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.26] but these were not loaded, likely because it conflicts with another require. - setono/job-status-bundle v0.2.3 requires symfony/config ^4.4 || ^5.0 -> found symfony/config[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.31] but these were not loaded, likely because it conflicts with another require. - doctrine/orm[2.8.0, ..., 2.8.4] require symfony/console ^3.0|^4.0|^5.0 -> found symfony/console[v3.0.0, ..., v3.4.47, v4.0.0, ..., v4.4.49, v5.0.0, ..., v5.4.34] but these were not loaded, likely because it conflicts with another require. - Root composer.json requires setono/job-status-bundle ^0.2.3 -> satisfiable by setono/job-status-bundle[v0.2.3, v0.2.4, v0.2.5]. - Conclusion: don't install doctrine/persistence 1.3.8 (conflict analysis result) - Conclusion: don't install doctrine/persistence 2.5.2 (conflict analysis result) - doctrine/persistence[2.2.1, ..., 2.5.1] require doctrine/deprecations ^0.5.3 -> satisfiable by doctrine/deprecations[v0.5.3]. - You can only install one version of a package, so only one of these can be installed: doctrine/deprecations[v0.5.3, v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - doctrine/lexer[2.0.0, ..., 2.1.0] require doctrine/deprecations ^1.0 -> satisfiable by doctrine/deprecations[v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - doctrine/orm[2.15.0, ..., 2.15.5] require doctrine/lexer ^2 -> satisfiable by doctrine/lexer[2.0.0, 2.1.0]. - sylius-labs/association-hydrator v1.2.0 requires doctrine/orm ^2.4 -> satisfiable by doctrine/orm[v2.7.0, ..., 2.17.4]. - symfony/doctrine-bridge[v6.4.0, ..., v6.4.2] conflict with doctrine/orm <2.15. - sylius/sylius v1.12.13 requires sylius-labs/association-hydrator ^1.1 || ^1.2 -> satisfiable by sylius-labs/association-hydrator[v1.1.0, ..., v1.2.0]. - sylius/sylius v1.12.13 requires symfony/doctrine-bridge ^5.4 || ^6.0 -> satisfiable by symfony/doctrine-bridge[v6.4.0, v6.4.2]. - sylius/sylius v1.12.13 conflicts with doctrine/orm >= 2.16.0. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13]. - setono/job-status-bundle[v0.2.4, ..., v0.2.5] require doctrine/persistence ^1.3 || ^2.0 -> satisfiable by doctrine/persistence[1.3.0, ..., 1.3.8, 2.0.0, ..., 2.5.7]. - You can only install one version of a package, so only one of these can be installed: doctrine/persistence[v1.0.0, ..., 1.3.8, 2.0.0, ..., 2.5.7, 3.0.0, ..., 3.2.0]. - symfony/doctrine-bridge[v6.4.0, ..., v6.4.2] require doctrine/persistence ^3.1 -> satisfiable by doctrine/persistence[3.1.0, ..., 3.2.0]. - Conclusion: don't install doctrine/persistence 3.1.0 (conflict analysis result)

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

src/Command/ProcessPromotionsCommand.php:45:13: MissingDependency: Setono\SyliusCatalogPromotionPlugin\Repository\ProductRepositoryInterface depends on class or interface sylius\component\core\repository\productrepositoryinterface that does not exist (see https://psalm.dev/157)

src/Command/ProcessPromotionsCommand.php:47:13: MissingDependency: Setono\SyliusCatalogPromotionPlugin\Repository\ProductVariantRepositoryInterface depends on class or interface sylius\component\core\repository\productvariantrepositoryinterface that does not exist (see https://psalm.dev/157)

src/Command/ProcessPromotionsCommand.php:63:9: MissingDependency: Setono\SyliusCatalogPromotionPlugin\Repository\ProductRepositoryInterface depends on class or interface sylius\component\core\repository\productrepositoryinterface that does not exist (see https://psalm.dev/157)

src/Command/ProcessPromotionsCommand.php:64:9: MissingDependency: Setono\SyliusCatalogPromotionPlugin\Repository\ProductVariantRepositoryInterface depends on class or interface sylius\component\core\repository\productvariantrepositoryinterface that does not exist (see https://psalm.dev/157)

src/Command/ProcessPromotionsCommand.php:107:52: MissingDependency: Setono\SyliusCatalogPromotionPlugin\Model\PromotionInterface depends on class or interface sylius\component\channel\model\channelsawareinterface that does not exist (see https://psalm.dev/157)

src/Command/ProcessPromotionsCommand.php:138:19: MissingDependency: Setono\SyliusCatalogPromotionPlugin\Repository\ProductVariantRepositoryInterface depends on class or interface sylius\component\core\repository\productvariantrepositoryinterface that does not exist (see https://psalm.dev/157)

src/Command/ProcessPromotionsCommand.php:142:17: MissingDependency: Setono\SyliusCatalogPromotionPlugin\Model\PromotionInterface depends on class or interface sylius\component\channel\model\channelsawareinterface that does not exist (see https://psalm.dev/157)

src/Command/ProcessPromotionsCommand.php:146:22: MissingDependency: Setono\SyliusCatalogPromotionPlugin\Model\PromotionInterface depends on class or interface sylius\component\channel\model\channelsawareinterface that does not exist (see https://psalm.dev/157)

src/Command/ProcessPromotionsCommand.php:173:30: MissingDependency: Setono\SyliusCatalogPromotionPlugin\Model\PromotionInterface depends on class or interface sylius\component\channel\model\channelsawareinterface that does not exist (see https://psalm.dev/157)

src/Command/ProcessPromotionsCommand.php:174:21: MissingDependency: Setono\SyliusCatalogPromotionPlugin\Model\PromotionInterface depends on class or interface sylius\component\channel\model\channelsawareinterface that does not exist (see https://psalm.dev/157)

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - sylius-labs/association-hydrator[v1.1.0, ..., v1.1.1] require php ^7.1 -> your php version (8.2.14) does not satisfy that requirement. - doctrine/persistence[1.3.0, ..., 1.3.7, 2.0.0] require php ^7.1 -> your php version (8.2.14) does not satisfy that requirement. - doctrine/orm[v2.7.0, ..., 2.7.5] require php ^7.1 -> your php version (8.2.14) does not satisfy that requirement. - sylius-labs/association-hydrator[v1.1.2, ..., v1.1.3] require php ^7.2 -> your php version (8.2.14) does not satisfy that requirement. - sylius-labs/association-hydrator v1.1.4 requires symfony/property-access ^3.4|^4.4|^5.0 -> found symfony/property-access[v3.4.0, ..., v3.4.47, v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.26] but these were not loaded, likely because it conflicts with another require. - setono/job-status-bundle v0.2.3 requires symfony/config ^4.4 || ^5.0 -> found symfony/config[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.31] but these were not loaded, likely because it conflicts with another require. - doctrine/orm[2.8.0, ..., 2.8.4] require symfony/console ^3.0|^4.0|^5.0 -> found symfony/console[v3.0.0, ..., v3.4.47, v4.0.0, ..., v4.4.49, v5.0.0, ..., v5.4.34] but these were not loaded, likely because it conflicts with another require. - Root composer.json requires setono/job-status-bundle ^0.2.3 -> satisfiable by setono/job-status-bundle[v0.2.3, v0.2.4, v0.2.5]. - Conclusion: don't install doctrine/persistence 1.3.8 (conflict analysis result) - Conclusion: don't install doctrine/persistence 2.5.2 (conflict analysis result) - doctrine/persistence[2.2.1, ..., 2.5.1] require doctrine/deprecations ^0.5.3 -> satisfiable by doctrine/deprecations[v0.5.3]. - You can only install one version of a package, so only one of these can be installed: doctrine/deprecations[v0.5.3, v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - doctrine/lexer[2.0.0, ..., 2.1.0] require doctrine/deprecations ^1.0 -> satisfiable by doctrine/deprecations[v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - doctrine/orm[2.15.0, ..., 2.15.5] require doctrine/lexer ^2 -> satisfiable by doctrine/lexer[2.0.0, 2.1.0]. - sylius-labs/association-hydrator v1.2.0 requires doctrine/orm ^2.4 -> satisfiable by doctrine/orm[v2.7.0, ..., 2.17.4]. - symfony/doctrine-bridge[v6.4.0, ..., v6.4.2] conflict with doctrine/orm <2.15. - sylius/sylius v1.12.13 requires sylius-labs/association-hydrator ^1.1 || ^1.2 -> satisfiable by sylius-labs/association-hydrator[v1.1.0, ..., v1.2.0]. - sylius/sylius v1.12.13 requires symfony/doctrine-bridge ^5.4 || ^6.0 -> satisfiable by symfony/doctrine-bridge[v6.4.0, v6.4.2]. - sylius/sylius v1.12.13 conflicts with doctrine/orm >= 2.16.0. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13]. - setono/job-status-bundle[v0.2.4, ..., v0.2.5] require doctrine/persistence ^1.3 || ^2.0 -> satisfiable by doctrine/persistence[1.3.0, ..., 1.3.8, 2.0.0, ..., 2.5.7]. - You can only install one version of a package, so only one of these can be installed: doctrine/persistence[v1.0.0, ..., 1.3.8, 2.0.0, ..., 2.5.7, 3.0.0, ..., 3.2.0]. - symfony/doctrine-bridge[v6.4.0, ..., v6.4.2] require doctrine/persistence ^3.1 -> satisfiable by doctrine/persistence[3.1.0, ..., 3.2.0]. - Conclusion: don't install doctrine/persistence 3.1.0 (conflict analysis result)

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - setono/job-status-bundle v0.2.3 requires symfony/config ^4.4 || ^5.0 -> found symfony/config[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.31] but these were not loaded, likely because it conflicts with another require. - doctrine/persistence[1.3.0, ..., 1.3.7, 2.0.0] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement. - Root composer.json requires doctrine/orm ^2.7 -> satisfiable by doctrine/orm[v2.7.0, ..., 2.17.4]. - Conclusion: don't install doctrine/persistence 2.5.2 (conflict analysis result) - doctrine/persistence[2.2.1, ..., 2.5.1] require doctrine/deprecations ^0.5.3 -> satisfiable by doctrine/deprecations[v0.5.3]. - You can only install one version of a package, so only one of these can be installed: doctrine/deprecations[v0.5.3, v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - doctrine/lexer[2.0.0, ..., 2.1.0] require doctrine/deprecations ^1.0 -> satisfiable by doctrine/deprecations[v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - Conclusion: install doctrine/lexer 2.0.0 (conflict analysis result) - Conclusion: install symfony/doctrine-bridge v6.4.0 (conflict analysis result) - Root composer.json requires setono/job-status-bundle ^0.2.3 -> satisfiable by setono/job-status-bundle[v0.2.3, v0.2.4, v0.2.5]. - setono/job-status-bundle[v0.2.4, ..., v0.2.5] require doctrine/persistence ^1.3 || ^2.0 -> satisfiable by doctrine/persistence[1.3.0, ..., 1.3.8, 2.0.0, ..., 2.5.7]. - You can only install one version of a package, so only one of these can be installed: doctrine/persistence[v1.0.0, ..., 1.3.8, 2.0.0, ..., 2.5.7, 3.0.0, ..., 3.2.0]. - symfony/doctrine-bridge[v6.4.0, ..., v6.4.2] require doctrine/persistence ^3.1 -> satisfiable by doctrine/persistence[3.1.0, ..., 3.2.0]. - Conclusion: don't install doctrine/persistence 3.1.0 (conflict analysis result)

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - sylius-labs/association-hydrator[v1.1.0, ..., v1.1.1] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement. - doctrine/persistence[1.3.0, ..., 1.3.7, 2.0.0] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement. - doctrine/orm[v2.7.0, ..., 2.7.5] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement. - sylius-labs/association-hydrator[v1.1.2, ..., v1.1.3] require php ^7.2 -> your php version (8.1.27) does not satisfy that requirement. - sylius-labs/association-hydrator v1.1.4 requires symfony/property-access ^3.4|^4.4|^5.0 -> found symfony/property-access[v3.4.0, ..., v3.4.47, v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.26] but these were not loaded, likely because it conflicts with another require. - setono/job-status-bundle v0.2.3 requires symfony/config ^4.4 || ^5.0 -> found symfony/config[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.31] but these were not loaded, likely because it conflicts with another require. - doctrine/orm[2.8.0, ..., 2.8.4] require symfony/console ^3.0|^4.0|^5.0 -> found symfony/console[v3.0.0, ..., v3.4.47, v4.0.0, ..., v4.4.49, v5.0.0, ..., v5.4.34] but these were not loaded, likely because it conflicts with another require. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13]. - Conclusion: don't install doctrine/persistence 2.5.7 (conflict analysis result) - doctrine/persistence[2.2.1, ..., 2.5.1] require doctrine/deprecations ^0.5.3 -> satisfiable by doctrine/deprecations[v0.5.3]. - You can only install one version of a package, so only one of these can be installed: doctrine/deprecations[v0.5.3, v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - doctrine/lexer[2.0.0, ..., 2.1.0] require doctrine/deprecations ^1.0 -> satisfiable by doctrine/deprecations[v1.0.0, v1.1.0, v1.1.1, 1.1.2]. - doctrine/orm[2.15.0, ..., 2.15.5] require doctrine/lexer ^2 -> satisfiable by doctrine/lexer[2.0.0, 2.1.0]. - sylius-labs/association-hydrator v1.2.0 requires doctrine/orm ^2.4 -> satisfiable by doctrine/orm[v2.7.0, ..., 2.17.4]. - symfony/doctrine-bridge[v6.4.0, ..., v6.4.2] conflict with doctrine/orm <2.15. - sylius/sylius v1.12.13 requires sylius-labs/association-hydrator ^1.1 || ^1.2 -> satisfiable by sylius-labs/association-hydrator[v1.1.0, ..., v1.2.0]. - sylius/sylius v1.12.13 requires symfony/doctrine-bridge ^5.4 || ^6.0 -> satisfiable by symfony/doctrine-bridge[v6.4.0, v6.4.2]. - sylius/sylius v1.12.13 conflicts with doctrine/orm >= 2.16.0. - Root composer.json requires setono/job-status-bundle ^0.2.3 -> satisfiable by setono/job-status-bundle[v0.2.3, v0.2.4, v0.2.5]. - setono/job-status-bundle[v0.2.4, ..., v0.2.5] require doctrine/persistence ^1.3 || ^2.0 -> satisfiable by doctrine/persistence[1.3.0, ..., 1.3.8, 2.0.0, ..., 2.5.7]. - You can only install one version of a package, so only one of these can be installed: doctrine/persistence[v1.0.0, ..., 1.3.8, 2.0.0, ..., 2.5.7, 3.0.0, ..., 3.2.0]. - symfony/doctrine-bridge[v6.4.0, ..., v6.4.2] require doctrine/persistence ^3.1 -> satisfiable by doctrine/persistence[3.1.0, ..., 3.2.0]. - Conclusion: don't install doctrine/persistence 3.2.0 (conflict analysis result)

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/framework-bundle[v6.1.0, ..., v6.1.11] require symfony/dependency-injection ^6.1 -> satisfiable by symfony/dependency-injection[v6.4.0, v6.4.1, v6.4.2]. - symfony/dependency-injection[v6.4.0, ..., v6.4.2] conflict with symfony/proxy-manager-bridge v6.1.11. - sylius/sylius v1.12.13 requires symfony/framework-bundle ^5.4 || ^6.0 -> satisfiable by symfony/framework-bundle[v6.1.0, ..., v6.1.11]. - sylius/sylius v1.12.13 requires symfony/proxy-manager-bridge ^5.4 || ^6.0 -> satisfiable by symfony/proxy-manager-bridge[v6.1.0, v6.1.11]. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/framework-bundle[v6.1.0, ..., v6.1.11] require symfony/dependency-injection ^6.1 -> satisfiable by symfony/dependency-injection[v6.4.0, v6.4.1, v6.4.2]. - symfony/dependency-injection[v6.4.0, ..., v6.4.2] conflict with symfony/proxy-manager-bridge v6.1.0. - sylius/sylius v1.12.13 requires symfony/framework-bundle ^5.4 || ^6.0 -> satisfiable by symfony/framework-bundle[v6.1.0, ..., v6.1.11]. - sylius/sylius v1.12.13 requires symfony/proxy-manager-bridge ^5.4 || ^6.0 -> satisfiable by symfony/proxy-manager-bridge[v6.1.0, v6.1.11]. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13].

The operation was canceled.

The operation was canceled.

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/dependency-injection[v6.4.0, ..., v6.4.2] conflict with symfony/proxy-manager-bridge v6.2.7. - symfony/twig-bundle[v6.2.0, ..., v6.2.7] require symfony/dependency-injection ^6.1 -> satisfiable by symfony/dependency-injection[v6.4.0, v6.4.1, v6.4.2]. - sylius/sylius v1.12.13 requires symfony/proxy-manager-bridge ^5.4 || ^6.0 -> satisfiable by symfony/proxy-manager-bridge[v6.2.0, v6.2.5, v6.2.7]. - sylius/sylius v1.12.13 requires symfony/twig-bundle ^5.4 || ^6.0 -> satisfiable by symfony/twig-bundle[v6.2.0, ..., v6.2.7]. - Root composer.json requires sylius/sylius ~1.12.13 -> satisfiable by sylius/sylius[v1.12.13].

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

The operation was canceled.

Process completed with exit code 127.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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