Skip to content

build(deps): bump nanasess/setup-chromedriver #1320

build(deps): bump nanasess/setup-chromedriver

build(deps): bump nanasess/setup-chromedriver #1320

Status Failure
Total duration 35m 3s
Artifacts 4

dockerbuild.yml

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

Annotations

2 errors and 9 warnings
dockerbuild (ubuntu-24.04, 8.1, pgsql, admin01)
The template is not valid. .github/workflows/dockerbuild.yml (Line: 94, Col: 16): Error reading JToken from JsonReader. Path '', line 0, position 0.
dockerbuild (ubuntu-24.04, 8.1, pgsql, admin01)
The process '/home/runner/work/_actions/nanasess/setup-php/bc11abbf4dd060b7bfd20d03edeeb43417ebe245/lib/apt-install-php-ubuntu.sh' failed with exit code 100
dockerbuild (ubuntu-24.04, 8.1, pgsql, admin01)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nanasess/setup-php@bc11abbf4dd060b7bfd20d03edeeb43417ebe245. 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/
dockerbuild (ubuntu-24.04, 8.1, pgsql, admin01)
No files were found with the provided path: var/log/. No artifacts will be uploaded.
dockerbuild (ubuntu-24.04, 8.1, pgsql, admin01)
No files were found with the provided path: codeception/_output/. No artifacts will be uploaded.
dockerbuild (ubuntu-24.04, 8.2, pgsql, admin01)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nanasess/setup-php@bc11abbf4dd060b7bfd20d03edeeb43417ebe245. 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/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L4
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L4
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
dockerbuild (ubuntu-24.04, 8.3, pgsql, admin01)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nanasess/setup-php@bc11abbf4dd060b7bfd20d03edeeb43417ebe245. 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/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L4
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L4
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Artifacts

Produced during runtime
Name Size Digest
EC-CUBE~ec-cube~7KE7XE.dockerbuild
29.6 KB
sha256:c1effbd2dfdc42d93de26685c9d71d0844ce4f653a6c3e01947378a4a390183c
EC-CUBE~ec-cube~8KQPZM.dockerbuild
92 KB
sha256:aa0b911a69e4ebd74b68385731275c28a4347a81b6e9f1fed8c2964a0889cfab
EC-CUBE~ec-cube~KLO5LS.dockerbuild
26.9 KB
sha256:2d30191d4a4d55baa718dbc09a5bd50a58d17a4e26c8b5d663aef3b476fd8e4a
EC-CUBE~ec-cube~L45A30.dockerbuild
90.4 KB
sha256:ceb00f77c2b9fedaf5b7d4d1643c6ad7e9660e5918442fe70fdc52f7ba0685fb