Rector changes #170
Annotations
9 errors and 18 warnings
build (8.1, ^13.4)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires typo3/cms-core ^13.4 -> satisfiable by typo3/cms-core[v13.4.0].
- typo3/cms-core v13.4.0 requires php ^8.2 -> your php version (8.1.30) does not satisfy that requirement.
Problem 2
- Root composer.json requires typo3/cms-frontend ^13.4 -> satisfiable by typo3/cms-frontend[v13.4.0].
- typo3/cms-core v13.4.0 requires php ^8.2 -> your php version (8.1.30) does not satisfy that requirement.
- typo3/cms-frontend v13.4.0 requires typo3/cms-core 13.4.0 -> satisfiable by typo3/cms-core[v13.4.0].
|
build (8.1, ^13.4)
Process completed with exit code 2.
|
build (8.2, ^13.4)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires infection/infection ^0.26 -> satisfiable by infection/infection[0.26.0, ..., 0.26.21].
- Root composer.json requires typo3/cms-core ^13.4 -> satisfiable by typo3/cms-core[v13.4.0].
- infection/infection[0.26.0, ..., 0.26.11] require symfony/process ^3.4.29 || ^4.1.19 || ^5.0 || ^6.0 -> satisfiable by symfony/process[v3.4.29, ..., v3.4.47, v4.2.0, ..., v4.4.44, v5.0.0, ..., v5.4.44, v6.0.0, ..., v6.4.12].
- infection/infection[0.26.12, ..., 0.26.21] require symfony/process ^5.4 || ^6.0 -> satisfiable by symfony/process[v5.4.0, ..., v5.4.44, v6.0.0, ..., v6.4.12].
- symfony/process[v4.2.0, ..., v4.4.10] require php ^7.1.3 -> your php version (8.2.24) does not satisfy that requirement.
- symfony/process[v5.0.0, ..., v5.0.8] require php ^7.2.5 -> your php version (8.2.24) does not satisfy that requirement.
- typo3/cms-core v13.4.0 requires symfony/process ^7.1.3 -> satisfiable by symfony/process[v7.1.3, v7.1.5].
- You can only install one version of a package, so only one of these can be installed: symfony/process[v3.4.29, ..., v3.4.47, v4.2.0, ..., v4.4.44, v5.0.0, ..., v5.4.44, v6.0.0, ..., v6.4.12, v7.0.0, ..., v7.1.5].
|
build (8.2, ^13.4)
Process completed with exit code 2.
|
build (8.3, ^13.4)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires infection/infection ^0.26 -> satisfiable by infection/infection[0.26.0, ..., 0.26.21].
- Root composer.json requires typo3/cms-core ^13.4 -> satisfiable by typo3/cms-core[v13.4.0].
- infection/infection[0.26.0, ..., 0.26.11] require symfony/process ^3.4.29 || ^4.1.19 || ^5.0 || ^6.0 -> satisfiable by symfony/process[v3.4.29, ..., v3.4.47, v4.2.0, ..., v4.4.44, v5.0.0, ..., v5.4.44, v6.0.0, ..., v6.4.12].
- infection/infection[0.26.12, ..., 0.26.21] require symfony/process ^5.4 || ^6.0 -> satisfiable by symfony/process[v5.4.0, ..., v5.4.44, v6.0.0, ..., v6.4.12].
- symfony/process[v4.2.0, ..., v4.4.10] require php ^7.1.3 -> your php version (8.3.12) does not satisfy that requirement.
- symfony/process[v5.0.0, ..., v5.0.8] require php ^7.2.5 -> your php version (8.3.12) does not satisfy that requirement.
- typo3/cms-core v13.4.0 requires symfony/process ^7.1.3 -> satisfiable by symfony/process[v7.1.3, v7.1.5].
- You can only install one version of a package, so only one of these can be installed: symfony/process[v3.4.29, ..., v3.4.47, v4.2.0, ..., v4.4.44, v5.0.0, ..., v5.4.44, v6.0.0, ..., v6.4.12, v7.0.0, ..., v7.1.5].
|
build (8.3, ^13.4)
Process completed with exit code 2.
|
build (8.3, ^12.4)
Process completed with exit code 1.
|
build (8.1, ^12.4)
Process completed with exit code 1.
|
build (8.2, ^12.4)
Process completed with exit code 1.
|
build (8.1, ^13.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
build (8.1, ^13.4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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/
|
build (8.1, ^13.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/
|
build (8.2, ^13.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
build (8.2, ^13.4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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/
|
build (8.2, ^13.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/
|
build (8.3, ^13.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
build (8.3, ^13.4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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/
|
build (8.3, ^13.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/
|
build (8.3, ^12.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
build (8.3, ^12.4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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/
|
build (8.3, ^12.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/
|
build (8.1, ^12.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
build (8.1, ^12.4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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/
|
build (8.1, ^12.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/
|
build (8.2, ^12.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
build (8.2, ^12.4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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/
|
build (8.2, ^12.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/
|