Skip to content

IBX-8470: Fixed outstanding issues after Symfony 6 upgrade #595

IBX-8470: Fixed outstanding issues after Symfony 6 upgrade

IBX-8470: Fixed outstanding issues after Symfony 6 upgrade #595

Triggered via pull request February 5, 2025 09:14
Status Failure
Total duration 43s
Artifacts

ci.yaml

on: pull_request
Matrix: Run code style check
Matrix: Tests
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 6 warnings
Run code style check (8.3)
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires behat/mink-goutte-driver ^1.2 -> satisfiable by behat/mink-goutte-driver[v1.2.0, v1.2.1, v1.3.0]. - Root composer.json requires ibexa/core ~5.0.0@dev -> satisfiable by ibexa/core[5.0.x-dev (alias of dev-main)]. - Root composer.json requires symfony/http-kernel ^6.4 -> satisfiable by symfony/http-kernel[v6.4.0, ..., v6.4.18]. - fabpot/goutte v3.3.1 requires symfony/browser-kit ^4.4|^5.0 -> satisfiable by symfony/browser-kit[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.45]. - ibexa/core dev-main requires symfony/framework-bundle ^6.4.0 -> satisfiable by symfony/framework-bundle[v6.4.0, ..., v6.4.18]. - symfony/browser-kit[v4.4.0, ..., v4.4.8] require php ^7.1.3 -> your php version (8.3.16) does not satisfy that requirement. - symfony/dom-crawler[v4.4.0, ..., v4.4.8] require php ^7.1.3 -> your php version (8.3.16) does not satisfy that requirement. - symfony/browser-kit[v5.0.0, ..., v5.0.8] require php ^7.2.5 -> your php version (8.3.16) does not satisfy that requirement. - symfony/dom-crawler[v5.0.0, ..., v5.0.8] require php ^7.2.5 -> your php version (8.3.16) does not satisfy that requirement. - symfony/browser-kit[v5.4.0, ..., v5.4.45] require symfony/dom-crawler ^4.4|^5.0|^6.0 -> satisfiable by symfony/dom-crawler[v4.4.0, ..., v4.4.45, v5.0.0, ..., v5.4.48, v6.0.0, ..., v6.4.18]. - symfony/framework-bundle[v6.4.0, ..., v6.4.1] conflict with symfony/dom-crawler <6.4. - symfony/http-kernel[v6.4.0, ..., v6.4.18] conflict with symfony/browser-kit v5.3.14. - symfony/http-kernel[v6.4.0, ..., v6.4.18] conflict with symfony/browser-kit v5.3.0. - symfony/http-kernel[v6.4.0, ..., v6.4.18] conflict with symfony/browser-kit v4.4.44. - symfony/http-kernel[v6.4.0, ..., v6.4.18] conflict with symfony/browser-kit v4.4.25. - Conclusion: don't install symfony/framework-bundle v6.4.2 (conflict analysis result) - Conclusion: don't install symfony/framework-bundle v6.4.3 (conflict analysis result) - Conclusion: don't install symfony/framework-bundle v6.4.10 (conflict analysis result) - Conclusion: don't install symfony/framework-bundle v6.4.12 (conflict analysis result) - Conclusion: don't install symfony/framework-bundle v6.4.18 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v5.2.12 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v5.3.0 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v5.3.14 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v5.4.48 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v6.0.19 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v6.2.12 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v6.3.12 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v6.4.18 (conflict analysis result) - Conclusion: install fabpot/goutte v3.3.1 (conflict analysis result) - ibexa/core 5.0.x-dev is an alias of ibexa/core dev-main and thus requires it to be installed too.
Run code style check (8.3)
The process '/usr/local/bin/composer' failed with exit code 2
Tests (8.3)
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires behat/mink-goutte-driver ^1.2 -> satisfiable by behat/mink-goutte-driver[v1.2.0, v1.2.1, v1.3.0]. - Root composer.json requires ibexa/core ~5.0.0@dev -> satisfiable by ibexa/core[5.0.x-dev (alias of dev-main)]. - Root composer.json requires symfony/http-kernel ^6.4 -> satisfiable by symfony/http-kernel[v6.4.0, ..., v6.4.18]. - fabpot/goutte v3.3.1 requires symfony/browser-kit ^4.4|^5.0 -> satisfiable by symfony/browser-kit[v4.4.0, ..., v4.4.44, v5.0.0, ..., v5.4.45]. - ibexa/core dev-main requires symfony/framework-bundle ^6.4.0 -> satisfiable by symfony/framework-bundle[v6.4.0, ..., v6.4.18]. - symfony/browser-kit[v4.4.0, ..., v4.4.8] require php ^7.1.3 -> your php version (8.3.16) does not satisfy that requirement. - symfony/dom-crawler[v4.4.0, ..., v4.4.8] require php ^7.1.3 -> your php version (8.3.16) does not satisfy that requirement. - symfony/browser-kit[v5.0.0, ..., v5.0.8] require php ^7.2.5 -> your php version (8.3.16) does not satisfy that requirement. - symfony/dom-crawler[v5.0.0, ..., v5.0.8] require php ^7.2.5 -> your php version (8.3.16) does not satisfy that requirement. - symfony/browser-kit[v5.4.0, ..., v5.4.45] require symfony/dom-crawler ^4.4|^5.0|^6.0 -> satisfiable by symfony/dom-crawler[v4.4.0, ..., v4.4.45, v5.0.0, ..., v5.4.48, v6.0.0, ..., v6.4.18]. - symfony/framework-bundle[v6.4.0, ..., v6.4.1] conflict with symfony/dom-crawler <6.4. - symfony/http-kernel[v6.4.0, ..., v6.4.18] conflict with symfony/browser-kit v5.3.14. - symfony/http-kernel[v6.4.0, ..., v6.4.18] conflict with symfony/browser-kit v5.3.0. - symfony/http-kernel[v6.4.0, ..., v6.4.18] conflict with symfony/browser-kit v4.4.44. - symfony/http-kernel[v6.4.0, ..., v6.4.18] conflict with symfony/browser-kit v4.4.25. - Conclusion: don't install symfony/framework-bundle v6.4.2 (conflict analysis result) - Conclusion: don't install symfony/framework-bundle v6.4.3 (conflict analysis result) - Conclusion: don't install symfony/framework-bundle v6.4.10 (conflict analysis result) - Conclusion: don't install symfony/framework-bundle v6.4.12 (conflict analysis result) - Conclusion: don't install symfony/framework-bundle v6.4.18 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v5.2.12 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v5.3.0 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v5.3.14 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v5.4.48 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v6.0.19 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v6.2.12 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v6.3.12 (conflict analysis result) - Conclusion: don't install symfony/dom-crawler v6.4.18 (conflict analysis result) - Conclusion: install fabpot/goutte v3.3.1 (conflict analysis result) - ibexa/core 5.0.x-dev is an alias of ibexa/core dev-main and thus requires it to be installed too.
Tests (8.3)
The process '/usr/local/bin/composer' failed with exit code 2
Run code style check (8.3)
The `save-state` 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/
Run code style check (8.3)
The `save-state` 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/
Run code style check (8.3)
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/
Tests (8.3)
The `save-state` 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/
Tests (8.3)
The `save-state` 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/
Tests (8.3)
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/