Skip to content

testing on second machine, re-wrote splash page to empty template. #2

testing on second machine, re-wrote splash page to empty template.

testing on second machine, re-wrote splash page to empty template. #2

Triggered via push March 19, 2026 22:31
Status Failure
Total duration 22s
Artifacts

tests.yml

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

Annotations

6 errors and 3 warnings
ci (8.3)
Process completed with exit code 2.
ci (8.3)
Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/clock is locked to version v8.0.0 and an update of this package was not requested. - symfony/clock v8.0.0 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 2 - symfony/console is locked to version v8.0.7 and an update of this package was not requested. - symfony/console v8.0.7 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 3 - symfony/css-selector is locked to version v8.0.6 and an update of this package was not requested. - symfony/css-selector v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 4 - symfony/error-handler is locked to version v8.0.4 and an update of this package was not requested. - symfony/error-handler v8.0.4 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 5 - symfony/event-dispatcher is locked to version v8.0.4 and an update of this package was not requested. - symfony/event-dispatcher v8.0.4 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 6 - symfony/finder is locked to version v8.0.6 and an update of this package was not requested. - symfony/finder v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 7 - symfony/http-foundation is locked to version v8.0.7 and an update of this package was not requested. - symfony/http-foundation v8.0.7 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 8 - symfony/http-kernel is locked to version v8.0.7 and an update of this package was not requested. - symfony/http-kernel v8.0.7 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 9 - symfony/mailer is locked to version v8.0.6 and an update of this package was not requested. - symfony/mailer v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 10 - symfony/mime is locked to version v8.0.7 and an update of this package was not requested. - symfony/mime v8.0.7 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 11 - symfony/process is locked to version v8.0.5 and an update of this package was not requested. - symfony/process v8.0.5 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 12 - symfony/routing is locked to version v8.0.6 and an update of this package was not requested. - symfony/routing v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 13 - symfony/string is locked to version v8.0.6 and an update of this package was not requested. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 14 - symfony/translation is locked to version v8.0.6 and an update of this package was not requested. - symfony/translation v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 15 - symfony/uid is locked to version v8.0.4 and an update of this package was not requested. - symfony/uid v8.0.4 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 16 - symfony/var-dumper is locked to version v8.0.6 and an update of this package was not requested. - symfony/var-dumper v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 17 - symfony/yaml is locked to version v8.0.6 and an update of this package was not requested. - symfony/yaml v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 18 - laravel/framework is locked to version v13.0.0 and an update of this package was not requested. - laravel/framework v13.0.0 requires sy
ci (8.4)
The strategy configuration was canceled because "ci._8_3" failed
ci (8.4)
The operation was canceled.
ci (8.5)
The strategy configuration was canceled because "ci._8_3" failed
ci (8.5)
The operation was canceled.
ci (8.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
ci (8.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
ci (8.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/