Kirby 4 Support #80
Annotations
9 errors and 6 warnings
test (8.1, ^3.5)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- getkirby/cms[3.5.0, ..., 3.5.8.4] require php >=7.3.0 <8.1.0 -> your php version (8.1.23) does not satisfy that requirement.
- getkirby/cms[3.6.0, ..., 3.6.1] require php >=7.4.0 <8.1.0 -> your php version (8.1.23) does not satisfy that requirement.
- getkirby/cms[3.6.1.1, ..., 3.7.4] require claviska/simpleimage 3.6.5 -> found claviska/simpleimage[3.6.5] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- getkirby/cms[3.7.5, ..., 3.8.4.2] require claviska/simpleimage 3.7.0 -> found claviska/simpleimage[3.7.0] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- getkirby/cms[3.9.0, ..., 3.9.2] require claviska/simpleimage 3.7.2 -> found claviska/simpleimage[3.7.2] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- getkirby/cms[3.9.3, ..., 3.9.4] require claviska/simpleimage 4.0.2 -> found claviska/simpleimage[4.0.2] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- getkirby/cms[3.9.5, ..., 3.9.6.1] require claviska/simpleimage 4.0.5 -> found claviska/simpleimage[4.0.5] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires getkirby/cms ^3.5 -> satisfiable by getkirby/cms[3.5.0, ..., 3.9.6.1].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
|
test (8.1, ^3.5)
Process completed with exit code 2.
|
test (8.0, ^3.5)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- getkirby/cms[3.5.0, ..., 3.5.4] require claviska/simpleimage 3.5.1 -> found claviska/simpleimage[3.5.1] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- getkirby/cms[3.5.5, ..., 3.6.0] require claviska/simpleimage 3.6.3 -> found claviska/simpleimage[3.6.3] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- getkirby/cms 3.6.1 requires claviska/simpleimage 3.6.4 -> found claviska/simpleimage[3.6.4] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- getkirby/cms[3.6.1.1, ..., 3.7.4] require claviska/simpleimage 3.6.5 -> found claviska/simpleimage[3.6.5] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- getkirby/cms[3.7.5, ..., 3.8.4.2] require claviska/simpleimage 3.7.0 -> found claviska/simpleimage[3.7.0] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- getkirby/cms[3.9.0, ..., 3.9.2] require claviska/simpleimage 3.7.2 -> found claviska/simpleimage[3.7.2] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- getkirby/cms[3.9.3, ..., 3.9.4] require claviska/simpleimage 4.0.2 -> found claviska/simpleimage[4.0.2] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- getkirby/cms[3.9.5, ..., 3.9.6.1] require claviska/simpleimage 4.0.5 -> found claviska/simpleimage[4.0.5] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires getkirby/cms ^3.5 -> satisfiable by getkirby/cms[3.5.0, ..., 3.9.6.1].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
|
test (8.0, ^3.5)
The operation was canceled.
|
test (8.1, ^4.0-beta.1)
The operation was canceled.
|
test (8.2, ^3.5)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- getkirby/cms[3.5.0, ..., 3.5.8.4] require php >=7.3.0 <8.1.0 -> your php version (8.2.10) does not satisfy that requirement.
- getkirby/cms[3.6.0, ..., 3.6.1] require php >=7.4.0 <8.1.0 -> your php version (8.2.10) does not satisfy that requirement.
- getkirby/cms[3.6.1.1, ..., 3.7.5.3] require php >=7.4.0 <8.2.0 -> your php version (8.2.10) does not satisfy that requirement.
- getkirby/cms[3.8.0, ..., 3.8.4.2] require php >=8.0.0 <8.2.0 -> your php version (8.2.10) does not satisfy that requirement.
- getkirby/cms[3.9.0, ..., 3.9.2] require claviska/simpleimage 3.7.2 -> found claviska/simpleimage[3.7.2] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- getkirby/cms[3.9.3, ..., 3.9.4] require claviska/simpleimage 4.0.2 -> found claviska/simpleimage[4.0.2] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- getkirby/cms[3.9.5, ..., 3.9.6.1] require claviska/simpleimage 4.0.5 -> found claviska/simpleimage[4.0.5] but the package is fixed to 4.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires getkirby/cms ^3.5 -> satisfiable by getkirby/cms[3.5.0, ..., 3.9.6.1].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
|
test (8.2, ^3.5)
Process completed with exit code 2.
|
test (8.0, ^4.0-beta.1)
The operation was canceled.
|
test (8.2, ^4.0-beta.1)
The operation was canceled.
|
test (8.1, ^3.5)
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/
|
test (8.0, ^3.5)
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/
|
test (8.1, ^4.0-beta.1)
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/
|
test (8.2, ^3.5)
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/
|
test (8.0, ^4.0-beta.1)
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/
|
test (8.2, ^4.0-beta.1)
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/
|