Skip to content

TASK: Neos 9 Compatibility #53

TASK: Neos 9 Compatibility

TASK: Neos 9 Compatibility #53

Re-run triggered April 16, 2026 09:43
Status Failure
Total duration 21s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
phpstan
Process completed with exit code 2.
phpstan
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires neos/contentrepositoryregistry-doctrinedbalclient ^9.0@beta -> satisfiable by neos/contentrepositoryregistry-doctrinedbalclient[9.0.0-beta1, ..., 9.0.0-beta10]. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta1 requires neos/contentrepository-core 9.0.0-beta1 -> found neos/contentrepository-core[9.0.0-beta1] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta10 requires neos/contentrepository-core 9.0.0-beta10 -> found neos/contentrepository-core[9.0.0-beta10] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta2 requires neos/contentrepository-core 9.0.0-beta2 -> found neos/contentrepository-core[9.0.0-beta2] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta3 requires neos/contentrepository-core 9.0.0-beta3 -> found neos/contentrepository-core[9.0.0-beta3] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta4 requires neos/contentrepository-core 9.0.0-beta4 -> found neos/contentrepository-core[9.0.0-beta4] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta5 requires neos/contentrepository-core 9.0.0-beta5 -> found neos/contentrepository-core[9.0.0-beta5] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta6 requires neos/contentrepository-core 9.0.0-beta6 -> found neos/contentrepository-core[9.0.0-beta6] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta7 requires neos/contentrepository-core 9.0.0-beta7 -> found neos/contentrepository-core[9.0.0-beta7] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta8 requires neos/contentrepository-core 9.0.0-beta8 -> found neos/contentrepository-core[9.0.0-beta8] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta9 requires neos/contentrepository-core 9.0.0-beta9 -> found neos/contentrepository-core[9.0.0-beta9] but it does not match your minimum-stability.
phpunit
Process completed with exit code 2.
phpunit
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires neos/contentrepositoryregistry-doctrinedbalclient ^9.0@beta -> satisfiable by neos/contentrepositoryregistry-doctrinedbalclient[9.0.0-beta1, ..., 9.0.0-beta10]. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta1 requires neos/contentrepository-core 9.0.0-beta1 -> found neos/contentrepository-core[9.0.0-beta1] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta10 requires neos/contentrepository-core 9.0.0-beta10 -> found neos/contentrepository-core[9.0.0-beta10] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta2 requires neos/contentrepository-core 9.0.0-beta2 -> found neos/contentrepository-core[9.0.0-beta2] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta3 requires neos/contentrepository-core 9.0.0-beta3 -> found neos/contentrepository-core[9.0.0-beta3] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta4 requires neos/contentrepository-core 9.0.0-beta4 -> found neos/contentrepository-core[9.0.0-beta4] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta5 requires neos/contentrepository-core 9.0.0-beta5 -> found neos/contentrepository-core[9.0.0-beta5] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta6 requires neos/contentrepository-core 9.0.0-beta6 -> found neos/contentrepository-core[9.0.0-beta6] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta7 requires neos/contentrepository-core 9.0.0-beta7 -> found neos/contentrepository-core[9.0.0-beta7] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta8 requires neos/contentrepository-core 9.0.0-beta8 -> found neos/contentrepository-core[9.0.0-beta8] but it does not match your minimum-stability. - neos/contentrepositoryregistry-doctrinedbalclient 9.0.0-beta9 requires neos/contentrepository-core 9.0.0-beta9 -> found neos/contentrepository-core[9.0.0-beta9] but it does not match your minimum-stability.
phpstan
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/
phpunit
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/