Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php ^8.2 but your php version (8.1.31) does not satisfy that requirement. Problem 2 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 php ^8.2 but your php version (8.1.31) does not satisfy that requirement. Problem 2 - Root composer.json requires symfony/proxy-manager-bridge ^6.4 || ^7.1 -> satisfiable by symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13]. - symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13] require symfony/dependency-injection ^6.3|^7.0 -> found symfony/dependency-injection[v6.3.0, ..., v6.4.16, v7.0.0, ..., v7.2.0] but these were not loaded, likely because it conflicts with another require. Problem 3 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 php ^8.2 but your php version (8.1.31) does not satisfy that requirement. Problem 2 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 php ^8.2 but your php version (8.1.31) does not satisfy that requirement. Problem 2 - Root composer.json requires symfony/proxy-manager-bridge ^6.4 || ^7.1 -> satisfiable by symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13]. - symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13] require symfony/dependency-injection ^6.3|^7.0 -> found symfony/dependency-injection[v6.3.0, ..., v6.4.16, v7.0.0, ..., v7.2.0] but these were not loaded, likely because it conflicts with another require. Problem 3 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 php ^8.2 but your php version (8.1.31) does not satisfy that requirement. Problem 2 - Root composer.json requires symfony/proxy-manager-bridge ^6.4 || ^7.1 -> satisfiable by symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13]. - symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13] require symfony/dependency-injection ^6.3|^7.0 -> found symfony/dependency-injection[v6.3.0, ..., v6.4.16, v7.0.0, ..., v7.2.0] but these were not loaded, likely because it conflicts with another require. Problem 3 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 symfony/proxy-manager-bridge ^6.4 || ^7.1 -> satisfiable by symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13]. - symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13] require symfony/dependency-injection ^6.3|^7.0 -> found symfony/dependency-injection[v6.3.0, ..., v6.4.16, v7.0.0, ..., v7.2.0] but these were not loaded, likely because it conflicts with another require. Problem 2 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 php ^8.2 but your php version (8.1.31) does not satisfy that requirement. Problem 2 - Root composer.json requires symfony/proxy-manager-bridge ^6.4 || ^7.1 -> satisfiable by symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13]. - symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13] require symfony/dependency-injection ^6.3|^7.0 -> found symfony/dependency-injection[v6.3.0, ..., v6.4.16, v7.0.0, ..., v7.2.0] but these were not loaded, likely because it conflicts with another require. Problem 3 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 symfony/proxy-manager-bridge ^6.4 || ^7.1 -> satisfiable by symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13]. - symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13] require symfony/dependency-injection ^6.3|^7.0 -> found symfony/dependency-injection[v6.3.0, ..., v6.4.16, v7.0.0, ..., v7.2.0] but these were not loaded, likely because it conflicts with another require. Problem 2 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 symfony/proxy-manager-bridge ^6.4 || ^7.1 -> satisfiable by symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13]. - symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13] require symfony/dependency-injection ^6.3|^7.0 -> found symfony/dependency-injection[v6.3.0, ..., v6.4.16, v7.0.0, ..., v7.2.0] but these were not loaded, likely because it conflicts with another require. Problem 2 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 symfony/proxy-manager-bridge ^6.4 || ^7.1 -> satisfiable by symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13]. - symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13] require symfony/dependency-injection ^6.3|^7.0 -> found symfony/dependency-injection[v6.3.0, ..., v6.4.16, v7.0.0, ..., v7.2.0] but these were not loaded, likely because it conflicts with another require. Problem 2 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 symfony/proxy-manager-bridge ^6.4 || ^7.1 -> satisfiable by symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13]. - symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13] require symfony/dependency-injection ^6.3|^7.0 -> found symfony/dependency-injection[v6.3.0, ..., v6.4.16, v7.0.0, ..., v7.2.0] but these were not loaded, likely because it conflicts with another require. Problem 2 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 php ^8.2 but your php version (8.1.31) does not satisfy that requirement. Problem 2 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 symfony/proxy-manager-bridge ^6.4 || ^7.1 -> satisfiable by symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13]. - symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13] require symfony/dependency-injection ^6.3|^7.0 -> found symfony/dependency-injection[v6.3.0, ..., v6.4.16, v7.0.0, ..., v7.2.0] but these were not loaded, likely because it conflicts with another require. Problem 2 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 symfony/proxy-manager-bridge ^6.4 || ^7.1 -> satisfiable by symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13]. - symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13] require symfony/dependency-injection ^6.3|^7.0 -> found symfony/dependency-injection[v6.3.0, ..., v6.4.16, v7.0.0, ..., v7.2.0] but these were not loaded, likely because it conflicts with another require. Problem 2 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 symfony/proxy-manager-bridge ^6.4 || ^7.1 -> satisfiable by symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13]. - symfony/proxy-manager-bridge[v6.4.0, ..., v6.4.13] require symfony/dependency-injection ^6.3|^7.0 -> found symfony/dependency-injection[v6.3.0, ..., v6.4.16, v7.0.0, ..., v7.2.0] but these were not loaded, likely because it conflicts with another require. Problem 2 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 php ^8.2 but your php version (8.1.31) does not satisfy that requirement. Problem 2 - Root composer.json requires sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.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 sylius/sylius ~1.13.0 -> satisfiable by sylius/sylius[v1.13.0, ..., v1.13.9]. - sylius/sylius[v1.13.0, ..., v1.13.9] require symfony/webpack-encore-bundle ^1.15 -> found symfony/webpack-encore-bundle[v1.15.0, ..., v1.17.2] but it conflicts with your root composer.json require (^2.2).

Process completed with exit code 2.

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636