perf: optimize CI workflow and Dockerfiles for faster builds #88
KingPinAnnotations
20 warnings and 21 notices
|
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: actions/checkout@v4, 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. 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-apache-bookworm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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. 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: actions/checkout@v4, 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. 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: actions/checkout@v4, 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: actions/checkout@v4, 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: actions/checkout@v4, 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. 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: actions/checkout@v4, 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: actions/checkout@v4, 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-apache-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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: actions/checkout@v4, 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: actions/checkout@v4, 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. 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: actions/checkout@v4, 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: actions/checkout@v4, 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. 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-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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. 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-apache-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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. 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-bookworm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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. 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: actions/checkout@v4, 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. 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: actions/checkout@v4, 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: actions/checkout@v4, 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. 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)
|
|
v1-8.2-apache-bookworm
✅ Build and tests passed for v1 - php-docker:8.2-apache-bookworm
|
|
v1-8.4-apache-bookworm
✅ Build and tests passed for v1 - php-docker:8.4-apache-bookworm
|
|
v2-8.2-cli-trixie
✅ Build and tests passed for v2 - php-docker:8.2-cli-trixie-v2
|
|
v1-8.2-cli-alpine
✅ Build and tests passed for v1 - php-docker:8.2-cli-alpine
|
|
v1-8.2-fpm-alpine
✅ Build and tests passed for v1 - php-docker:8.2-fpm-alpine
|
|
v1-8.4-cli-bookworm
✅ Build and tests passed for v1 - php-docker:8.4-cli-bookworm
|
|
v2-8.4-cli-trixie
✅ Build and tests passed for v2 - php-docker:8.4-cli-trixie-v2
|
|
v2-8.4-fpm-trixie
✅ Build and tests passed for v2 - php-docker:8.4-fpm-trixie-v2
|
|
v2-8.2-apache-trixie
✅ Build and tests passed for v2 - php-docker:8.2-apache-trixie-v2
|
|
v2-8.4-cli-alpine
✅ Build and tests passed for v2 - php-docker:8.4-cli-alpine-v2
|
|
v1-8.4-fpm-alpine
✅ Build and tests passed for v1 - php-docker:8.4-fpm-alpine
|
|
v2-8.2-cli-alpine
✅ Build and tests passed for v2 - php-docker:8.2-cli-alpine-v2
|
|
v2-8.4-fpm-alpine
✅ Build and tests passed for v2 - php-docker:8.4-fpm-alpine-v2
|
|
v1-8.4-cli-alpine
✅ Build and tests passed for v1 - php-docker:8.4-cli-alpine
|
|
v2-8.4-apache-trixie
✅ Build and tests passed for v2 - php-docker:8.4-apache-trixie-v2
|
|
v1-8.2-fpm-bookworm
✅ Build and tests passed for v1 - php-docker:8.2-fpm-bookworm
|
|
v2-8.2-fpm-trixie
✅ Build and tests passed for v2 - php-docker:8.2-fpm-trixie-v2
|
|
v1-8.2-cli-bookworm
✅ Build and tests passed for v1 - php-docker:8.2-cli-bookworm
|
|
v1-8.4-fpm-bookworm
✅ Build and tests passed for v1 - php-docker:8.4-fpm-bookworm
|
|
v2-8.2-fpm-alpine
✅ Build and tests passed for v2 - php-docker:8.2-fpm-alpine-v2
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
KingPin~php-docker~1I0T5U.dockerbuild
|
290 KB |
sha256:6d97da9ec39cff2d6d451041e766cf3103348dbecc9d31ba5897570cbb7482c5
|
|
|
KingPin~php-docker~2TZ3OV.dockerbuild
|
307 KB |
sha256:def7f84c172fcda7226b6966f90df8e1a113bece24a494acf558cddc4fc0a882
|
|
|
KingPin~php-docker~5FBJ9C.dockerbuild
|
270 KB |
sha256:a2e9216c86590af8af1d453f96fdcb87ff2ac55cf7df566b92e243353a9e6b8d
|
|
|
KingPin~php-docker~93E97C.dockerbuild
|
250 KB |
sha256:d0d05c69f170cf42b5de135c5f237cfae3b55638676efec2d6dce3aebb966a21
|
|
|
KingPin~php-docker~JXKZ4W.dockerbuild
|
251 KB |
sha256:e012497b54d305f2c779cd6866d829530f8f08f32fbf1f52ebdd61592ed0632b
|
|
|
KingPin~php-docker~JZ38IA.dockerbuild
|
293 KB |
sha256:d0bea841770412890e4d21bf9e92792c4f33a164b505a223936e8a7684b54bb1
|
|
|
KingPin~php-docker~KOKI62.dockerbuild
|
314 KB |
sha256:f5636086225043438293e0705ce124d00c0b137d7475f44b932678eed84bbfca
|
|
|
KingPin~php-docker~KOKPNU.dockerbuild
|
296 KB |
sha256:73dc8b6cb6d258facbba3bef0bd020eb404f5393fb71ccef5a44a312bf08c733
|
|
|
KingPin~php-docker~LJSZSR.dockerbuild
|
272 KB |
sha256:7fb2f945b895820e9150771ef5c78dcc04cda6d4705311592c0c38e04af371ff
|
|
|
KingPin~php-docker~N4MB55.dockerbuild
|
258 KB |
sha256:a876c935561abe86307335e1602333a92f32776713c2db57a9e815828ce7b47f
|
|
|
KingPin~php-docker~OSDKEC.dockerbuild
|
323 KB |
sha256:e42a33304e0b55405d42a412d0d38416b5030ca5ba3993d26e970015bab33e51
|
|
|
KingPin~php-docker~Q0ZG6R.dockerbuild
|
241 KB |
sha256:fcc012185015eca23472a37d6ffed473b4334dd11f736656f7415fe9cf238b61
|
|
|
KingPin~php-docker~QBOGJR.dockerbuild
|
245 KB |
sha256:56035e123f3ed177edc5d2f48cb7163ed9ef41ef875a85e4366bcfbf4fff6b56
|
|
|
KingPin~php-docker~QC9CHV.dockerbuild
|
286 KB |
sha256:03e040948e5a8a7e3f0680c9558ef5d275e30b492a855d3e1ed74a2c070f38ef
|
|
|
KingPin~php-docker~TNFOHC.dockerbuild
|
316 KB |
sha256:06294027b23931266764ba500808cbbd4c6845bdfe2ec85f65936c44765e55ae
|
|
|
KingPin~php-docker~TRQV54.dockerbuild
|
259 KB |
sha256:82e23f961233667daea1c700b116b8e7663844020ad3bc0d8f20211cc361a977
|
|
|
KingPin~php-docker~UCHSJD.dockerbuild
|
311 KB |
sha256:a0be591a54506af7b80dd6a9cd0cfbeaff9d36385c39fc8049222919199e7400
|
|
|
KingPin~php-docker~YEXVGR.dockerbuild
|
290 KB |
sha256:9c873c4efa245e02cf8148d93737bf83459f7fa862da8c595daf71aa1e997970
|
|
|
KingPin~php-docker~YKC3KF.dockerbuild
|
311 KB |
sha256:0b95ca83ada859c45aba5344e3301c66f7f34c6c571ad175ab408e86035f83a8
|
|
|
KingPin~php-docker~ZDLEOP.dockerbuild
|
291 KB |
sha256:66c4455a38bf042f6289c07cb5b4e8391fc84f19bef91b91dc986aaa326c39df
|
|