Skip to content

Merge pull request #249 from techdivision/PAC-973 #326

Merge pull request #249 from techdivision/PAC-973

Merge pull request #249 from techdivision/PAC-973 #326

Triggered via push May 16, 2026 13:37
Status Failure
Total duration 32s
Artifacts

php.yml

on: push
Matrix: run
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 4 warnings
Build ubuntu-latest > 7.4
Process completed with exit code 2.
Build ubuntu-latest > 7.4
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php ^8.3 but your php version (7.4.33) does not satisfy that requirement. Problem 2 - Root composer.json requires techdivision/import-dbal ^2.1, found techdivision/import-dbal[2.1.0-alpha] but it does not match your minimum-stability. Problem 3 - Root composer.json requires techdivision/import-dbal-collection ^2.2, found techdivision/import-dbal-collection[2.2.0-alpha] but it does not match your minimum-stability. Problem 4 - Root composer.json requires techdivision/import-cache ^2.1, found techdivision/import-cache[2.1.0-alpha] but it does not match your minimum-stability. Problem 5 - Root composer.json requires techdivision/import-cache-collection ^2.1, found techdivision/import-cache-collection[2.1.0-alpha] but it does not match your minimum-stability. Problem 6 - Root composer.json requires techdivision/import-serializer ^2.2, found techdivision/import-serializer[2.2.0-alpha] but it does not match your minimum-stability. Problem 7 - Root composer.json requires techdivision/import-serializer-csv ^2.2, found techdivision/import-serializer-csv[2.2.0-alpha] but it does not match your minimum-stability. Problem 8 - Root composer.json requires techdivision/import-configuration ^6.2, found techdivision/import-configuration[6.2.0-alpha] but it does not match your minimum-stability. Problem 9 - Root composer.json requires psr/cache ^2.0|^3.0 -> satisfiable by psr/cache[2.0.0, 3.0.0]. - psr/cache[2.0.0, 3.0.0] require php >=8.0.0 -> your php version (7.4.33) does not satisfy that requirement. Problem 10 - Root composer.json requires laminas/laminas-filter ^2.31 -> satisfiable by laminas/laminas-filter[2.31.0, ..., 2.42.0]. - laminas/laminas-filter 2.31.0 requires php ~8.0.0 || ~8.1.0 || ~8.2.0 -> your php version (7.4.33) does not satisfy that requirement. - laminas/laminas-filter 2.32.0 requires php ~8.1.0 || ~8.2.0 -> your php version (7.4.33) does not satisfy that requirement. - laminas/laminas-filter[2.33.0, ..., 2.37.0] require php ~8.1.0 || ~8.2.0 || ~8.3.0 -> your php version (7.4.33) does not satisfy that requirement. - laminas/laminas-filter[2.38.0, ..., 2.41.0] require php ~8.1.0 || ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (7.4.33) does not satisfy that requirement. - laminas/laminas-filter 2.42.0 requires php ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (7.4.33) does not satisfy that requirement.
Build macos-latest > 7.3
The strategy configuration was canceled because "run.ubuntu-latest_7_4" failed
Build macos-latest > 7.3
The operation was canceled.
Build macos-latest > 7.4
The strategy configuration was canceled because "run.ubuntu-latest_7_4" failed
Build macos-latest > 7.4
The operation was canceled.
Build ubuntu-latest > 7.3
The strategy configuration was canceled because "run.ubuntu-latest_7_4" failed
Build ubuntu-latest > 7.3
The operation was canceled.
Build ubuntu-latest > 7.4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. 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/
Build macos-latest > 7.3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. 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/
Build macos-latest > 7.4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. 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/
Build ubuntu-latest > 7.3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. 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/