!!![TASK] use ServerRequestInterface #821
Annotations
13 errors and 5 warnings
|
all tests (8.1, 12)
Process completed with exit code 2.
|
|
all tests (8.1, 12)
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.34) does not satisfy that requirement.
Problem 2
- Root composer.json requires typo3/cms-backend ^13.4 || ^14.0 -> satisfiable by typo3/cms-backend[v13.4.23, ..., v13.4.30, v14.0.2, ..., v14.3.2].
- typo3/cms-backend v13.4.23 requires typo3/cms-core 13.4.23 -> found typo3/cms-core[v13.4.23] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.24 requires typo3/cms-core 13.4.24 -> found typo3/cms-core[v13.4.24] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.25 requires typo3/cms-core 13.4.25 -> found typo3/cms-core[v13.4.25] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.26 requires typo3/cms-core 13.4.26 -> found typo3/cms-core[v13.4.26] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.27 requires typo3/cms-core 13.4.27 -> found typo3/cms-core[v13.4.27] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.28 requires typo3/cms-core 13.4.28 -> found typo3/cms-core[v13.4.28] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.29 requires typo3/cms-core 13.4.29 -> found typo3/cms-core[v13.4.29] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.30 requires typo3/cms-core 13.4.30 -> found typo3/cms-core[v13.4.30] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v14.3.0 requires typo3/cms-core 14.3.0 -> found typo3/cms-core[v14.3.0] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v14.3.1 requires typo3/cms-core 14.3.1 -> found typo3/cms-core[v14.3.1] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v14.3.2 requires typo3/cms-core 14.3.2 -> found typo3/cms-core[v14.3.2] but it conflicts with your root composer.json require (^12.4).
|
|
all tests (8.2, 12)
The strategy configuration was canceled because "testsuite._8_1_12" failed
|
|
all tests (8.2, 12)
Process completed with exit code 2.
|
|
all tests (8.2, 12)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires typo3/cms-backend ^13.4 || ^14.0 -> satisfiable by typo3/cms-backend[v13.4.23, ..., v13.4.30, v14.0.2, ..., v14.3.2].
- typo3/cms-backend v13.4.23 requires typo3/cms-core 13.4.23 -> found typo3/cms-core[v13.4.23] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.24 requires typo3/cms-core 13.4.24 -> found typo3/cms-core[v13.4.24] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.25 requires typo3/cms-core 13.4.25 -> found typo3/cms-core[v13.4.25] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.26 requires typo3/cms-core 13.4.26 -> found typo3/cms-core[v13.4.26] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.27 requires typo3/cms-core 13.4.27 -> found typo3/cms-core[v13.4.27] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.28 requires typo3/cms-core 13.4.28 -> found typo3/cms-core[v13.4.28] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.29 requires typo3/cms-core 13.4.29 -> found typo3/cms-core[v13.4.29] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v13.4.30 requires typo3/cms-core 13.4.30 -> found typo3/cms-core[v13.4.30] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v14.3.0 requires typo3/cms-core 14.3.0 -> found typo3/cms-core[v14.3.0] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v14.3.1 requires typo3/cms-core 14.3.1 -> found typo3/cms-core[v14.3.1] but it conflicts with your root composer.json require (^12.4).
- typo3/cms-backend v14.3.2 requires typo3/cms-core 14.3.2 -> found typo3/cms-core[v14.3.2] but it conflicts with your root composer.json require (^12.4).
|
|
all tests (8.2, 11)
The strategy configuration was canceled because "testsuite._8_1_12" failed
|
|
all tests (8.2, 11)
The operation was canceled.
|
|
all tests (8.2, 11)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires typo3/cms-core ^11.5, found typo3/cms-core[v11.5.0, ..., v11.5.41] but these were not loaded, because they are affected by security advisories ("PKSA-rtck-8z1q-gn5s", "PKSA-ns26-fz7n-2jm8", "PKSA-pz1k-khnw-3j7j", "PKSA-2ssc-6m7w-s9xh", "PKSA-q3vc-nbpk-d1gk", "PKSA-6d7x-2gs8-wr59", "PKSA-b5m3-ttcx-cz18", "PKSA-3gg2-48j5-46ky", "PKSA-tm11-834c-1wbq", "PKSA-443h-dk5w-qm2g", "PKSA-8vkj-4d3h-x586", "PKSA-prgj-sgzn-q6cs", "PKSA-zz7z-6zsy-d2hc", "PKSA-99mg-htb6-c272", "PKSA-h5xk-8nxx-znp4", "PKSA-d551-hdqh-5mmf", "PKSA-jbhx-knzt-5y6m", "PKSA-jp7z-h3vv-yr4s", "PKSA-83hy-ynvj-7pfq", "PKSA-vxw7-bfmg-pz5q", "PKSA-qbn4-sj3q-rvvx", "PKSA-pdn3-qb24-bkw6", "PKSA-ccxj-fgkz-pynv", "PKSA-3p3s-8w1v-x6b3", "PKSA-hf6f-qcwd-7279", "PKSA-j3x1-dtrb-kbct", "PKSA-p25q-9h89-q9b8", "PKSA-rwrz-v1bh-34yt", "PKSA-wjjh-fbmt-t55w", "PKSA-wkgp-n44t-r1jh", "PKSA-v1kb-vbr1-8fy1", "PKSA-d4cy-7k8v-3wtm", "PKSA-dnvg-71td-yz19", "PKSA-4kgv-d12j-68gk", "PKSA-dh2h-m334-x2dj", "PKSA-sy4v-bxfk-mjjn", "PKSA-1f5c-bp4y-tqft"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
Problem 2
- Root composer.json requires typo3/cms-backend ^13.4 || ^14.0 -> satisfiable by typo3/cms-backend[v13.4.23, ..., v13.4.30, v14.0.2, ..., v14.3.2].
- typo3/cms-backend v13.4.23 requires typo3/cms-core 13.4.23 -> found typo3/cms-core[v13.4.23] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.24 requires typo3/cms-core 13.4.24 -> found typo3/cms-core[v13.4.24] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.25 requires typo3/cms-core 13.4.25 -> found typo3/cms-core[v13.4.25] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.26 requires typo3/cms-core 13.4.26 -> found typo3/cms-core[v13.4.26] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.27 requires typo3/cms-core 13.4.27 -> found typo3/cms-core[v13.4.27] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.28 requires typo3/cms-core 13.4.28 -> found typo3/cms-core[v13.4.28] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.29 requires typo3/cms-core 13.4.29 -> found typo3/cms-core[v13.4.29] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.30 requires typo3/cms-core 13.4.30 -> found typo3/cms-core[v13.4.30] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v14.3.0 requires typo3/cms-core 14.3.0 -> found typo3/cms-core[v14.3.0] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v14.3.1 requires typo3/cms-core 14.3.1 -> found typo3/cms-core[v14.3.1] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v14.3.2 requires typo3/cms-core 14.3.2 -> found typo3/cms-core[v14.3.2] but it conflicts with your root composer.json require (^11.5).
|
|
all tests (13, 8.3)
The strategy configuration was canceled because "testsuite._8_1_12" failed
|
|
all tests (13, 8.3)
The operation was canceled.
|
|
all tests (8.1, 11)
The strategy configuration was canceled because "testsuite._8_1_12" failed
|
|
all tests (8.1, 11)
The operation was canceled.
|
|
all tests (8.1, 11)
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.34) does not satisfy that requirement.
Problem 2
- Root composer.json requires typo3/cms-core ^11.5, found typo3/cms-core[v11.5.0, ..., v11.5.41] but these were not loaded, because they are affected by security advisories ("PKSA-rtck-8z1q-gn5s", "PKSA-ns26-fz7n-2jm8", "PKSA-pz1k-khnw-3j7j", "PKSA-2ssc-6m7w-s9xh", "PKSA-q3vc-nbpk-d1gk", "PKSA-6d7x-2gs8-wr59", "PKSA-b5m3-ttcx-cz18", "PKSA-3gg2-48j5-46ky", "PKSA-tm11-834c-1wbq", "PKSA-443h-dk5w-qm2g", "PKSA-8vkj-4d3h-x586", "PKSA-prgj-sgzn-q6cs", "PKSA-zz7z-6zsy-d2hc", "PKSA-99mg-htb6-c272", "PKSA-h5xk-8nxx-znp4", "PKSA-d551-hdqh-5mmf", "PKSA-jbhx-knzt-5y6m", "PKSA-jp7z-h3vv-yr4s", "PKSA-83hy-ynvj-7pfq", "PKSA-vxw7-bfmg-pz5q", "PKSA-qbn4-sj3q-rvvx", "PKSA-pdn3-qb24-bkw6", "PKSA-ccxj-fgkz-pynv", "PKSA-3p3s-8w1v-x6b3", "PKSA-hf6f-qcwd-7279", "PKSA-j3x1-dtrb-kbct", "PKSA-p25q-9h89-q9b8", "PKSA-rwrz-v1bh-34yt", "PKSA-wjjh-fbmt-t55w", "PKSA-wkgp-n44t-r1jh", "PKSA-v1kb-vbr1-8fy1", "PKSA-d4cy-7k8v-3wtm", "PKSA-dnvg-71td-yz19", "PKSA-4kgv-d12j-68gk", "PKSA-dh2h-m334-x2dj", "PKSA-sy4v-bxfk-mjjn", "PKSA-1f5c-bp4y-tqft"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
Problem 3
- Root composer.json requires typo3/cms-backend ^13.4 || ^14.0 -> satisfiable by typo3/cms-backend[v13.4.23, ..., v13.4.30, v14.0.2, ..., v14.3.2].
- typo3/cms-backend v13.4.23 requires typo3/cms-core 13.4.23 -> found typo3/cms-core[v13.4.23] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.24 requires typo3/cms-core 13.4.24 -> found typo3/cms-core[v13.4.24] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.25 requires typo3/cms-core 13.4.25 -> found typo3/cms-core[v13.4.25] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.26 requires typo3/cms-core 13.4.26 -> found typo3/cms-core[v13.4.26] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.27 requires typo3/cms-core 13.4.27 -> found typo3/cms-core[v13.4.27] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.28 requires typo3/cms-core 13.4.28 -> found typo3/cms-core[v13.4.28] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.29 requires typo3/cms-core 13.4.29 -> found typo3/cms-core[v13.4.29] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v13.4.30 requires typo3/cms-core 13.4.30 -> found typo3/cms-core[v13.4.30] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v14.3.0 requires typo3/cms-core 14.3.0 -> found typo3/cms-core[v14.3.0] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v14.3.1 requires typo3/cms-core 14.3.1 -> found typo3/cms-core[v14.3.1] but it conflicts with your root composer.json require (^11.5).
- typo3/cms-backend v14.3.2 requires typo3/cms-core 14.3.2 -> found typo3/cms-core[v14.3.2] but it conflicts with your root composer.json require (^11.5).
|
|
all tests (8.1, 12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
all tests (8.2, 12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
all tests (8.2, 11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
all tests (13, 8.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
all tests (8.1, 11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|