chore(deps): improve dependabot config with grouping and schedule #96
KingPinAnnotations
20 warnings and 21 notices
|
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/
|
|
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. 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: 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. 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-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/
|
|
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. 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: 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. 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/
|
|
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. 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.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-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.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. 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: 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. 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-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/
|
|
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. 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-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/
|
|
setup
PR detected — testing PHP 8.4 + 8.2 only (skipping 8.3)
|
|
v1-8.4-fpm-bookworm
✅ Build and tests passed for v1 - php-docker:8.4-fpm-bookworm
|
|
v1-8.4-apache-bookworm
✅ Build and tests passed for v1 - php-docker:8.4-apache-bookworm
|
|
v1-8.2-cli-bookworm
✅ Build and tests passed for v1 - php-docker:8.2-cli-bookworm
|
|
v1-8.4-cli-bookworm
✅ Build and tests passed for v1 - php-docker:8.4-cli-bookworm
|
|
v1-8.2-fpm-bookworm
✅ Build and tests passed for v1 - php-docker:8.2-fpm-bookworm
|
|
v1-8.2-apache-bookworm
✅ Build and tests passed for v1 - php-docker:8.2-apache-bookworm
|
|
v1-8.2-cli-alpine
✅ Build and tests passed for v1 - php-docker:8.2-cli-alpine
|
|
v1-8.4-fpm-alpine
✅ Build and tests passed for v1 - php-docker:8.4-fpm-alpine
|
|
v1-8.2-fpm-alpine
✅ Build and tests passed for v1 - php-docker:8.2-fpm-alpine
|
|
v2-8.2-fpm-trixie
✅ Build and tests passed for v2 - php-docker:8.2-fpm-trixie-v2
|
|
v2-8.2-apache-trixie
✅ Build and tests passed for v2 - php-docker:8.2-apache-trixie-v2
|
|
v2-8.2-cli-alpine
✅ Build and tests passed for v2 - php-docker:8.2-cli-alpine-v2
|
|
v2-8.4-cli-alpine
✅ Build and tests passed for v2 - php-docker:8.4-cli-alpine-v2
|
|
v2-8.2-cli-trixie
✅ Build and tests passed for v2 - php-docker:8.2-cli-trixie-v2
|
|
v2-8.4-cli-trixie
✅ Build and tests passed for v2 - php-docker:8.4-cli-trixie-v2
|
|
v2-8.4-fpm-alpine
✅ Build and tests passed for v2 - php-docker:8.4-fpm-alpine-v2
|
|
v2-8.4-apache-trixie
✅ Build and tests passed for v2 - php-docker:8.4-apache-trixie-v2
|
|
v1-8.4-cli-alpine
✅ Build and tests passed for v1 - php-docker:8.4-cli-alpine
|
|
v2-8.4-fpm-trixie
✅ Build and tests passed for v2 - php-docker:8.4-fpm-trixie-v2
|
|
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~0NMLBJ.dockerbuild
Expired
|
266 KB |
sha256:8948219c02fd1e3996e77a05670dd5dc9be9a81ac0f31e5b7896e6466532ffa6
|
|
|
KingPin~php-docker~2TXYT5.dockerbuild
Expired
|
302 KB |
sha256:b403b343f3afd58a94b9a013f19a4f397410c2548c5085d041d261617dcd87a7
|
|
|
KingPin~php-docker~2YYSEC.dockerbuild
Expired
|
290 KB |
sha256:44777f2dcf6c0deee21bfaadcc2dd0db6a8b0633bb937370e997f8addd3ed53c
|
|
|
KingPin~php-docker~4BX2AL.dockerbuild
Expired
|
297 KB |
sha256:88e0373b93c71043dd159e57d893edb82b128eaa06b8d055b91cafa5d7b65456
|
|
|
KingPin~php-docker~52P3K8.dockerbuild
Expired
|
272 KB |
sha256:ab2f5c463159c74bbe0b21e1353e1eeca7c6efc812480dc40b7cfedbd396e502
|
|
|
KingPin~php-docker~6ZGEB0.dockerbuild
Expired
|
245 KB |
sha256:9b79aa0a8a8a3e530e92e987b691a98a06a23921b338eea4f6f0d5646b4466ba
|
|
|
KingPin~php-docker~7CA9J2.dockerbuild
Expired
|
253 KB |
sha256:a45978843b56f6a47a782d5c943ee5d74a10b31c2c08bd37639fddea39b164e2
|
|
|
KingPin~php-docker~IPZKKB.dockerbuild
Expired
|
291 KB |
sha256:59f6f712cde44b29cfada789d2aa6294c2b379b96f7a2f12148fbe121257cd57
|
|
|
KingPin~php-docker~J5BNJJ.dockerbuild
Expired
|
285 KB |
sha256:94baf3ae0189be16c7953233e371d8c134f2c9cd64e8eb4dfbfceca089067c36
|
|
|
KingPin~php-docker~LAF0ZJ.dockerbuild
Expired
|
38.7 KB |
sha256:4ce50dda904efddcb954de71ceb7f8d28b965855a9ba663b4bd47fef084c8d00
|
|
|
KingPin~php-docker~MBGCNI.dockerbuild
Expired
|
274 KB |
sha256:d844fd8d8e9b961785850b851419e5b61449849313cb54a28198d237ee908ceb
|
|
|
KingPin~php-docker~O8X8KZ.dockerbuild
Expired
|
253 KB |
sha256:b64cb8810ed17d237b81c2b22f9d74defea544c54b58f8ed7e93b3e71588d743
|
|
|
KingPin~php-docker~PV2ZCA.dockerbuild
Expired
|
302 KB |
sha256:a1f3fa44b64c58e4db6578a77baef4fde2e8e2681dd0cf9c3db13c65c6772f31
|
|
|
KingPin~php-docker~S4MM2Z.dockerbuild
Expired
|
327 KB |
sha256:5742562f8bfa728c7631b41c5fdf8204ba65192a42dc69a004a3b5ed8d5eadae
|
|
|
KingPin~php-docker~V2JBMR.dockerbuild
Expired
|
249 KB |
sha256:16f4cdc66c0199fe0b8b4d6634665c2b4804f9f72d6367f3bd2934e6971dab6f
|
|
|
KingPin~php-docker~VYVRUY.dockerbuild
Expired
|
291 KB |
sha256:2497451fff7af97c57b3bfcaa8b810402f29c65f475be2ff463d1818a18e88dd
|
|
|
KingPin~php-docker~WFC2V9.dockerbuild
Expired
|
287 KB |
sha256:10faf17c9b1d391b1c182c4ba0e7c979be50a3cc3c1d7fabdc6b922a525aa4ee
|
|
|
KingPin~php-docker~WGT5W8.dockerbuild
Expired
|
300 KB |
sha256:fcc25c48f5701d61b8eb431423b853c50616208dba8ac30fab53e9f46ec770ee
|
|
|
KingPin~php-docker~WQ04BK.dockerbuild
Expired
|
253 KB |
sha256:590a5e4c052e4f92ed1372aa59f71d2794266cf10331a85b96313850365a9b37
|
|
|
KingPin~php-docker~X5KTDW.dockerbuild
Expired
|
283 KB |
sha256:157791cb2647967009f2b35cbe5f2c0a1834bd67ff63e69eaa7bae4bde557cd2
|
|