Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires chimera/routing-implementation ^1.0, it could not be found in any version, but the following packages provide it: - chimera/routing-mezzio Laminas Mezzio implementation for chimera/routing - chimera/routing-expressive Zend Expressive implementation for chimera/routing Consider requiring one of these to satisfy the chimera/routing-implementation requirement. Problem 2 - Root composer.json requires chimera/routing-mezzio 0.4.0 -> satisfiable by chimera/routing-mezzio[0.4.0]. - chimera/routing-mezzio 0.4.0 requires chimera/foundation ^0.4 -> found chimera/foundation[0.4.0, 0.4.x-dev] but it conflicts with your root composer.json require (^1.0.x-dev). Potential causes: - A typo in the package name - The package is not available in a stable-enough version according to your minimum-stability setting see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details. - It's a private package and you forgot to add a custom repository to find it Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires chimera/routing-implementation ^1.0, it could not be found in any version, but the following packages provide it: - chimera/routing-mezzio Laminas Mezzio implementation for chimera/routing - chimera/routing-expressive Zend Expressive implementation for chimera/routing Consider requiring one of these to satisfy the chimera/routing-implementation requirement. Problem 2 - Root composer.json requires chimera/routing-mezzio 0.4.0 -> satisfiable by chimera/routing-mezzio[0.4.0]. - chimera/routing-mezzio 0.4.0 requires chimera/foundation ^0.4 -> found chimera/foundation[0.4.0, 0.4.x-dev] but it conflicts with your root composer.json require (^1.0.x-dev). Potential causes: - A typo in the package name - The package is not available in a stable-enough version according to your minimum-stability setting see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details. - It's a private package and you forgot to add a custom repository to find it Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

The job was canceled because "lowest_8_1_ubuntu-latest" failed.

Process completed with exit code 4.

Process completed with exit code 4.

Process completed with exit code 4.

The job was canceled because "lowest_8_1_ubuntu-latest" failed.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires chimera/routing-implementation ^1.0, it could not be found in any version, but the following packages provide it: - chimera/routing-mezzio Laminas Mezzio implementation for chimera/routing - chimera/routing-expressive Zend Expressive implementation for chimera/routing Consider requiring one of these to satisfy the chimera/routing-implementation requirement. Problem 2 - Root composer.json requires chimera/routing-mezzio 0.4.0 -> satisfiable by chimera/routing-mezzio[0.4.0]. - chimera/routing-mezzio 0.4.0 requires chimera/foundation ^0.4 -> found chimera/foundation[0.4.0, 0.4.x-dev] but it conflicts with your root composer.json require (^1.0.x-dev). Potential causes: - A typo in the package name - The package is not available in a stable-enough version according to your minimum-stability setting see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details. - It's a private package and you forgot to add a custom repository to find it Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The operation was canceled.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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/

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/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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/

The following actions use a deprecated Node.js version and will be forced to run on node20: shivammathur/[email protected], actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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/