Merge pull request #2803 from pi-hole/fix/import_api_sessions_earlier #7362
build.yml
on: push
smoke-tests
6s
Matrix: build-test-deploy
Annotations
7 warnings
|
build-test-deploy (linux/amd64, pihole-FTL-amd64-clang, ubuntu-24.04, clang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. 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/
|
|
build-test-deploy (linux/arm/v7, pihole-FTL-armv7, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. 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/
|
|
build-test-deploy (linux/386, pihole-FTL-386, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. 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/
|
|
build-test-deploy (linux/amd64, pihole-FTL-amd64, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. 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/
|
|
build-test-deploy (linux/riscv64, pihole-FTL-riscv64, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. 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/
|
|
build-test-deploy (linux/riscv64, pihole-FTL-riscv64, ubuntu-24.04-arm)
Attempt 2 failed. Reason: Timeout of 900000ms hit
|
|
build-test-deploy (linux/riscv64, pihole-FTL-riscv64, ubuntu-24.04-arm)
Attempt 1 failed. Reason: Timeout of 900000ms hit
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
pihole-FTL-386-binary
|
11.2 MB |
sha256:8213222beb8b2aefb1bd022d45ffb89af9245f1496672a13ede420ad490ff029
|
|
|
pihole-FTL-amd64-binary
|
11.7 MB |
sha256:fb639c5e31811baf980034adc10d0fa8cdc48d861b75848d65029f67d1c3b335
|
|
|
pihole-FTL-amd64-clang-binary
|
7.45 MB |
sha256:5ae0371a84ac8c850b2711af766cd9ab1d5f16a8dd3eac44cc3a98e2ade1130e
|
|
|
pihole-FTL-arm64-binary
|
11.9 MB |
sha256:01cc883a12411d580cf18cfb21627f728d89a5ff3e7dc156aad59fde4c507ef2
|
|
|
pihole-FTL-armv6-binary
|
11.6 MB |
sha256:52bb9099b63f9c9abbb6c66777b386513dc23a4bf0303dee0a95a357bfbe8452
|
|
|
pihole-FTL-armv7-binary
|
11.3 MB |
sha256:d88b7bced105f05188de1172a996ca59d8c79920f94134819cbf1bda9f65bd1f
|
|
|
pihole-FTL-riscv64-binary
|
12.7 MB |
sha256:5f53be51ceb12d7a4b91c93920416a3c3d79137d06f025d3df54a4413266b98c
|
|
|
pihole-api-docs
|
341 KB |
sha256:5fa20b72a4051d5936d9fa5684a2b14a890ad30380e8d62b2f2721ced490c9a2
|
|
|
pihole-toml
|
20.8 KB |
sha256:f61fdc81c1951d494488f3b074ea051b46902297ed1737d65f908ea65a0af5ad
|
|