phpactor config added #39
tolryAnnotations
6 errors and 20 warnings
|
Unit tests (7.4)
Your lock file does not contain a compatible set of packages. Please run composer update.
Problem 1
- Root composer.json requires php ^8.2 but your php version (7.4.33) does not satisfy that requirement.
Problem 2
- babdev/pagerfanta-bundle is locked to version v4.4.0 and an update of this package was not requested.
- babdev/pagerfanta-bundle v4.4.0 requires php ^8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 3
- doctrine/collections is locked to version 2.2.2 and an update of this package was not requested.
- doctrine/collections 2.2.2 requires php ^8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 4
- doctrine/event-manager is locked to version 2.0.1 and an update of this package was not requested.
- doctrine/event-manager 2.0.1 requires php ^8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 5
- doctrine/instantiator is locked to version 2.0.0 and an update of this package was not requested.
- doctrine/instantiator 2.0.0 requires php ^8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 6
- doctrine/lexer is locked to version 3.0.1 and an update of this package was not requested.
- doctrine/lexer 3.0.1 requires php ^8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 7
- doctrine/migrations is locked to version 3.8.2 and an update of this package was not requested.
- doctrine/migrations 3.8.2 requires php ^8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 8
- doctrine/sql-formatter is locked to version 1.5.1 and an update of this package was not requested.
- doctrine/sql-formatter 1.5.1 requires php ^8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 9
- monolog/monolog is locked to version 3.7.0 and an update of this package was not requested.
- monolog/monolog 3.7.0 requires php >=8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 10
- pagerfanta/pagerfanta is locked to version v4.7.0 and an update of this package was not requested.
- pagerfanta/pagerfanta v4.7.0 requires php ^8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 11
- psr/cache is locked to version 3.0.0 and an update of this package was not requested.
- psr/cache 3.0.0 requires php >=8.0.0 -> your php version (7.4.33) does not satisfy that requirement.
Problem 12
- psr/log is locked to version 3.0.2 and an update of this package was not requested.
- psr/log 3.0.2 requires php >=8.0.0 -> your php version (7.4.33) does not satisfy that requirement.
Problem 13
- symfony/asset is locked to version v6.4.8 and an update of this package was not requested.
- symfony/asset v6.4.8 requires php >=8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 14
- symfony/browser-kit is locked to version v6.4.8 and an update of this package was not requested.
- symfony/browser-kit v6.4.8 requires php >=8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 15
- symfony/cache is locked to version v6.4.12 and an update of this package was not requested.
- symfony/cache v6.4.12 requires php >=8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 16
- symfony/cache-contracts is locked to version v3.5.0 and an update of this package was not requested.
- symfony/cache-contracts v3.5.0 requires php >=8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 17
- symfony/clock is locked to version v7.1.1 and an update of this package was not requested.
- symfony/clock v7.1.1 requires php >=8.2 -> your php version (7.4.33) does not satisfy that requirement.
Problem 18
- symfony/config is locked to version v6.4.8 and an update of this package was not requested.
- symfony/config v6.4.8 requires php >=8.1 -> your php version (7.4.33) does not satisfy that requirement.
Problem 19
- symfony/console is
|
|
Unit tests (7.4)
Process completed with exit code 2.
|
|
Unit tests (7.4)
Process completed with exit code 1.
|
|
Unit tests (8.0)
Your lock file does not contain a compatible set of packages. Please run composer update.
Problem 1
- Root composer.json requires php ^8.2 but your php version (8.0.30) does not satisfy that requirement.
Problem 2
- babdev/pagerfanta-bundle is locked to version v4.4.0 and an update of this package was not requested.
- babdev/pagerfanta-bundle v4.4.0 requires php ^8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 3
- doctrine/collections is locked to version 2.2.2 and an update of this package was not requested.
- doctrine/collections 2.2.2 requires php ^8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 4
- doctrine/event-manager is locked to version 2.0.1 and an update of this package was not requested.
- doctrine/event-manager 2.0.1 requires php ^8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 5
- doctrine/instantiator is locked to version 2.0.0 and an update of this package was not requested.
- doctrine/instantiator 2.0.0 requires php ^8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 6
- doctrine/lexer is locked to version 3.0.1 and an update of this package was not requested.
- doctrine/lexer 3.0.1 requires php ^8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 7
- doctrine/migrations is locked to version 3.8.2 and an update of this package was not requested.
- doctrine/migrations 3.8.2 requires php ^8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 8
- doctrine/sql-formatter is locked to version 1.5.1 and an update of this package was not requested.
- doctrine/sql-formatter 1.5.1 requires php ^8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 9
- monolog/monolog is locked to version 3.7.0 and an update of this package was not requested.
- monolog/monolog 3.7.0 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 10
- pagerfanta/pagerfanta is locked to version v4.7.0 and an update of this package was not requested.
- pagerfanta/pagerfanta v4.7.0 requires php ^8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 11
- symfony/asset is locked to version v6.4.8 and an update of this package was not requested.
- symfony/asset v6.4.8 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 12
- symfony/browser-kit is locked to version v6.4.8 and an update of this package was not requested.
- symfony/browser-kit v6.4.8 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 13
- symfony/cache is locked to version v6.4.12 and an update of this package was not requested.
- symfony/cache v6.4.12 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 14
- symfony/cache-contracts is locked to version v3.5.0 and an update of this package was not requested.
- symfony/cache-contracts v3.5.0 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 15
- symfony/clock is locked to version v7.1.1 and an update of this package was not requested.
- symfony/clock v7.1.1 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement.
Problem 16
- symfony/config is locked to version v6.4.8 and an update of this package was not requested.
- symfony/config v6.4.8 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 17
- symfony/console is locked to version v6.4.12 and an update of this package was not requested.
- symfony/console v6.4.12 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement.
Problem 18
- symfony/dependency-injection is locked to version v6.4.12 and an update of this package was not requested.
- symfony/dependency-injection v6.4.12 requires php >=8.1 -> your php version (8.0.30) does not satis
|
|
Unit tests (8.0)
Process completed with exit code 2.
|
|
Unit tests (8.0)
Process completed with exit code 1.
|
|
Unit tests (7.4)
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/
|
|
Unit tests (7.4)
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/
|
|
Unit tests (7.4)
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/
|
|
Unit tests (7.4)
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/
|
|
Unit tests (7.4)
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/
|
|
Unit tests (7.4)
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/
|
|
Unit tests (7.4)
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/
|
|
Unit tests (7.4)
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/
|
|
Unit tests (7.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Unit tests (7.4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Unit tests (8.0)
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/
|
|
Unit tests (8.0)
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/
|
|
Unit tests (8.0)
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/
|
|
Unit tests (8.0)
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/
|
|
Unit tests (8.0)
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/
|
|
Unit tests (8.0)
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/
|
|
Unit tests (8.0)
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/
|
|
Unit tests (8.0)
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/
|
|
Unit tests (8.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Unit tests (8.0)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|