chore(deps): bump the github-actions group across 1 directory with 2 updates #100
dependabot[bot]Annotations
20 errors, 15 warnings, and 9 notices
|
v1-8.4-cli-alpine
Canceling since a higher priority waiting request for docker-ci-refs/pull/35/merge exists
|
|
v1-8.4-apache-bookworm
Canceling since a higher priority waiting request for docker-ci-refs/pull/35/merge exists
|
|
v1-8.2-fpm-bookworm
Canceling since a higher priority waiting request for docker-ci-refs/pull/35/merge exists
|
|
v2-8.2-fpm-trixie
Canceling since a higher priority waiting request for docker-ci-refs/pull/35/merge exists
|
|
v2-8.2-apache-trixie
Canceling since a higher priority waiting request for docker-ci-refs/pull/35/merge exists
|
|
v2-8.4-cli-trixie
Canceling since a higher priority waiting request for docker-ci-refs/pull/35/merge exists
|
|
v2-8.4-cli-trixie
The operation was canceled.
|
|
v1-8.4-cli-bookworm
Canceling since a higher priority waiting request for docker-ci-refs/pull/35/merge exists
|
|
v1-8.4-cli-bookworm
The operation was canceled.
|
|
v2-8.4-fpm-trixie
Canceling since a higher priority waiting request for docker-ci-refs/pull/35/merge exists
|
|
v2-8.4-fpm-trixie
The operation was canceled.
|
|
v1-8.2-cli-alpine
Canceling since a higher priority waiting request for docker-ci-refs/pull/35/merge exists
|
|
v1-8.2-cli-alpine
The operation was canceled.
|
|
v1-8.2-cli-bookworm
Canceling since a higher priority waiting request for docker-ci-refs/pull/35/merge exists
|
|
v1-8.2-cli-bookworm
The operation was canceled.
|
|
v2-8.2-cli-trixie
Canceling since a higher priority waiting request for docker-ci-refs/pull/35/merge exists
|
|
v2-8.2-cli-trixie
The operation was canceled.
|
|
v1-8.4-fpm-alpine
Canceling since a higher priority waiting request for docker-ci-refs/pull/35/merge exists
|
|
v1-8.4-fpm-alpine
The operation was canceled.
|
|
Docker CI (v1 + v2)
Canceling since a higher priority waiting request for docker-ci-refs/pull/35/merge exists
|
|
v2-8.4-apache-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v2-8.4-fpm-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v2-8.2-fpm-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v1-8.4-fpm-bookworm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v1-8.2-fpm-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v1-8.2-apache-bookworm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v2-8.4-cli-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v2-8.2-cli-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v2-8.4-cli-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v1-8.4-cli-bookworm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v2-8.4-fpm-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v1-8.2-cli-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v1-8.2-cli-bookworm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v2-8.2-cli-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
v1-8.4-fpm-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
setup
PR detected — testing PHP 8.4 + 8.2 only (skipping 8.3)
|
|
v2-8.4-apache-trixie
✅ Build and tests passed for v2 - php-docker:8.4-apache-trixie-v2
|
|
v2-8.4-fpm-alpine
✅ Build and tests passed for v2 - php-docker:8.4-fpm-alpine-v2
|
|
v2-8.2-fpm-alpine
✅ Build and tests passed for v2 - php-docker:8.2-fpm-alpine-v2
|
|
v1-8.4-fpm-bookworm
✅ Build and tests passed for v1 - php-docker:8.4-fpm-bookworm
|
|
v1-8.2-fpm-alpine
✅ Build and tests passed for v1 - php-docker:8.2-fpm-alpine
|
|
v1-8.2-apache-bookworm
✅ Build and tests passed for v1 - php-docker:8.2-apache-bookworm
|
|
v2-8.4-cli-alpine
✅ Build and tests passed for v2 - php-docker:8.4-cli-alpine-v2
|
|
v2-8.2-cli-alpine
✅ Build and tests passed for v2 - php-docker:8.2-cli-alpine-v2
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
KingPin~php-docker~DFBXQY.dockerbuild
Expired
|
303 KB |
sha256:4b17b0e7ce35ae5297365743d1d2cae88dafee0fceda1161477a7736bc0a8be4
|
|
|
KingPin~php-docker~LVVYQF.dockerbuild
Expired
|
256 KB |
sha256:21569ddc6c4a13e084303d90cf1857f7e4f3ab0635324fcdc4f4a572efa9cb4c
|
|
|
KingPin~php-docker~ORVNL2.dockerbuild
Expired
|
264 KB |
sha256:e6e236c24a086a15b921d3b3d35b6910eaddea3856450093797d0123c9b512af
|
|
|
KingPin~php-docker~OYN1TP.dockerbuild
Expired
|
251 KB |
sha256:d565ff3454bff9b3e8471ca2a772eaa7fd35b74a2480615e30a3a611cb6ab468
|
|
|
KingPin~php-docker~P51EHB.dockerbuild
Expired
|
332 KB |
sha256:74c97a7bca58739356bd225352efdebc32af8b933aec2650dea7cc066879d214
|
|
|
KingPin~php-docker~XISAXZ.dockerbuild
Expired
|
43.8 KB |
sha256:379b1bb14ef8e19a6a3d3be1d7fb7f30eb2a9d4cfd28689116f11f54d6b77c6c
|
|
|
KingPin~php-docker~Y1LM5Z.dockerbuild
Expired
|
255 KB |
sha256:22b133210a011139a660f6f831b67c267a7447662801c451da7bca7604ab60a6
|
|
|
KingPin~php-docker~Y5KFYM.dockerbuild
Expired
|
273 KB |
sha256:887d4bdb21bc5b78efcac843c250ed15014d96adc8e6dc54f5031d76b0498207
|
|