Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires neos/neos ^9.0 -> satisfiable by neos/neos[9.0.0, ..., 9.1.4]. - neos/contentrepositoryregistry 9.0.10 requires neos/contentrepositoryregistry-storageclient 9.0.10 -> could not be found in any version, but the following packages provide it: - neos/contentgraph-doctrinedbaladapter The Doctrine DBAL database backend for the Neos content graph - neos/neos-development-collection Neos packages in a joined repository for pull requests. - neos/contentrepositoryregistry-doctrinedbalclient Doctrine DBAL client for the Neos Content Repository Registry - neos/contentrepositoryregistry-postgresdbalclient PostgreSQL-optimized Doctrine DBAL client for the Neos Content Repository Registry Consider requiring one of these to satisfy the neos/contentrepositoryregistry-storageclient requirement. - neos/contentrepositoryregistry 9.0.11 requires neos/contentrepositoryregistry-storageclient 9.0.11 -> could not be found in any version, but the following packages provide it: - neos/contentgraph-doctrinedbaladapter The Doctrine DBAL database backend for the Neos content graph - neos/neos-development-collection Neos packages in a joined repository for pull requests. - neos/contentrepositoryregistry-doctrinedbalclient Doctrine DBAL client for the Neos Content Repository Registry - neos/contentrepositoryregistry-postgresdbalclient PostgreSQL-optimized Doctrine DBAL client for the Neos Content Repository Registry Consider requiring one of these to satisfy the neos/contentrepositoryregistry-storageclient requirement. - neos/contentrepositoryregistry 9.0.5 requires neos/contentrepositoryregistry-storageclient 9.0.5 -> could not be found in any version, but the following packages provide it: - neos/contentgraph-doctrinedbaladapter The Doctrine DBAL database backend for the Neos content graph - neos/neos-development-collection Neos packages in a joined repository for pull requests. - neos/contentrepositoryregistry-doctrinedbalclient Doctrine DBAL client for the Neos Content Repository Registry - neos/contentrepositoryregistry-postgresdbalclient PostgreSQL-optimized Doctrine DBAL client for the Neos Content Repository Registry Consider requiring one of these to satisfy the neos/contentrepositoryregistry-storageclient requirement. - neos/contentrepositoryregistry 9.0.6 requires neos/contentrepositoryregistry-storageclient 9.0.6 -> could not be found in any version, but the following packages provide it: - neos/contentgraph-doctrinedbaladapter The Doctrine DBAL database backend for the Neos content graph - neos/neos-development-collection Neos packages in a joined repository for pull requests. - neos/contentrepositoryregistry-doctrinedbalclient Doctrine DBAL client for the Neos Content Repository Registry - neos/contentrepositoryregistry-postgresdbalclient PostgreSQL-optimized Doctrine DBAL client for the Neos Content Repository Registry Consider requiring one of these to satisfy the neos/contentrepositoryregistry-storageclient requirement. - neos/contentrepositoryregistry 9.0.7 requires neos/contentrepositoryregistry-storageclient 9.0.7 -> could not be found in any version, but the following packages provide it: - neos/contentgraph-doctrinedbaladapter The Doctrine DBAL database backend for the Neos content graph - neos/neos-development-collection Neos packages in a joined repository for pull requests. - neos/contentrepositoryregistry-doctrinedbalclient Doctrine DBAL client for the Neos Content Repository Registry - neos/contentrepositoryregistry-postgresdbalclient PostgreSQL-optimized Doctrine DBAL client for the Neos Content Repository Registry Consider requiring one of these to satisfy the neos/contentrepositoryregistry-storageclient requirement. - neos/contentrepositoryregistry 9.0.8 requires neos/contentrepositoryregistry-storageclient 9.0.8 -> could not be fou

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires neos/neos ^9.0 -> satisfiable by neos/neos[9.0.0, ..., 9.1.4]. - neos/contentrepositoryregistry 9.0.10 requires neos/contentrepositoryregistry-storageclient 9.0.10 -> could not be found in any version, but the following packages provide it: - neos/contentgraph-doctrinedbaladapter The Doctrine DBAL database backend for the Neos content graph - neos/neos-development-collection Neos packages in a joined repository for pull requests. - neos/contentrepositoryregistry-doctrinedbalclient Doctrine DBAL client for the Neos Content Repository Registry - neos/contentrepositoryregistry-postgresdbalclient PostgreSQL-optimized Doctrine DBAL client for the Neos Content Repository Registry Consider requiring one of these to satisfy the neos/contentrepositoryregistry-storageclient requirement. - neos/contentrepositoryregistry 9.0.11 requires neos/contentrepositoryregistry-storageclient 9.0.11 -> could not be found in any version, but the following packages provide it: - neos/contentgraph-doctrinedbaladapter The Doctrine DBAL database backend for the Neos content graph - neos/neos-development-collection Neos packages in a joined repository for pull requests. - neos/contentrepositoryregistry-doctrinedbalclient Doctrine DBAL client for the Neos Content Repository Registry - neos/contentrepositoryregistry-postgresdbalclient PostgreSQL-optimized Doctrine DBAL client for the Neos Content Repository Registry Consider requiring one of these to satisfy the neos/contentrepositoryregistry-storageclient requirement. - neos/contentrepositoryregistry 9.0.5 requires neos/contentrepositoryregistry-storageclient 9.0.5 -> could not be found in any version, but the following packages provide it: - neos/contentgraph-doctrinedbaladapter The Doctrine DBAL database backend for the Neos content graph - neos/neos-development-collection Neos packages in a joined repository for pull requests. - neos/contentrepositoryregistry-doctrinedbalclient Doctrine DBAL client for the Neos Content Repository Registry - neos/contentrepositoryregistry-postgresdbalclient PostgreSQL-optimized Doctrine DBAL client for the Neos Content Repository Registry Consider requiring one of these to satisfy the neos/contentrepositoryregistry-storageclient requirement. - neos/contentrepositoryregistry 9.0.6 requires neos/contentrepositoryregistry-storageclient 9.0.6 -> could not be found in any version, but the following packages provide it: - neos/contentgraph-doctrinedbaladapter The Doctrine DBAL database backend for the Neos content graph - neos/neos-development-collection Neos packages in a joined repository for pull requests. - neos/contentrepositoryregistry-doctrinedbalclient Doctrine DBAL client for the Neos Content Repository Registry - neos/contentrepositoryregistry-postgresdbalclient PostgreSQL-optimized Doctrine DBAL client for the Neos Content Repository Registry Consider requiring one of these to satisfy the neos/contentrepositoryregistry-storageclient requirement. - neos/contentrepositoryregistry 9.0.7 requires neos/contentrepositoryregistry-storageclient 9.0.7 -> could not be found in any version, but the following packages provide it: - neos/contentgraph-doctrinedbaladapter The Doctrine DBAL database backend for the Neos content graph - neos/neos-development-collection Neos packages in a joined repository for pull requests. - neos/contentrepositoryregistry-doctrinedbalclient Doctrine DBAL client for the Neos Content Repository Registry - neos/contentrepositoryregistry-postgresdbalclient PostgreSQL-optimized Doctrine DBAL client for the Neos Content Repository Registry Consider requiring one of these to satisfy the neos/contentrepositoryregistry-storageclient requirement. - neos/contentrepositoryregistry 9.0.8 requires neos/contentrepositoryregistry-storageclient 9.0.8 -> could not be fou

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/