Skip to content

Introduce functional rebooter #1352

Introduce functional rebooter

Introduce functional rebooter #1352

Triggered via pull request June 4, 2026 08:54
Status Success
Total duration 3m 21s
Artifacts 12

esp32.yml

on: pull_request
Matrix: firmware_build
firmware_release
0s
firmware_release
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
firmware_build (ds-rom-code-scanner, ds-onewire, tendry-lab-, .env/ds_rom_code_scanner_configurat...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
firmware_build (ds18b20-verifier, ds-onewire, tendry-lab-, .env/ds18b20_verifier_configuration, e...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
firmware_build (ds-rom-code-scanner, ds-onewire, tendry-lab-, .env/ds_rom_code_scanner_configurat...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
firmware_build (ds18b20-verifier, ds-onewire, tendry-lab-, .env/ds18b20_verifier_configuration, e...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
firmware_build (sht4x-verifier, sht4x, tendry-lab-, .env/sht4x_verifier_configuration, esp32s2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
firmware_build (sht4x-verifier, sht4x, tendry-lab-, .env/sht4x_verifier_configuration, esp32s3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
firmware_build (ds18b20-verifier, ds-onewire, tendry-lab-, .env/ds18b20_verifier_configuration, e...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
firmware_build (unittest, tests, tendry-lab-, .env/unittest_configuration, esp32s3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
firmware_build (ds-rom-code-scanner, ds-onewire, tendry-lab-, .env/ds_rom_code_scanner_configurat...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
firmware_build (unittest, tests, tendry-lab-, .env/unittest_configuration, esp32s2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
firmware_build (sht4x-verifier, sht4x, tendry-lab-, .env/sht4x_verifier_configuration, esp32)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
firmware_build (unittest, tests, tendry-lab-, .env/unittest_configuration, esp32)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Artifacts

Produced during runtime
Name Size Digest
ds-rom-code-scanner-esp32-0.0.0-9e8eb8cc.26941576376
147 KB
sha256:bd6739de767ba9b478d1538cd39633a39edff23bb10cdc2c99d7a563634b736f
ds-rom-code-scanner-esp32s2-0.0.0-9e8eb8cc.26941576376
143 KB
sha256:a621ef88bf82cb2328e3a1d5b04258ae4692a75c9989be330fe5b631f7fb656b
ds-rom-code-scanner-esp32s3-0.0.0-9e8eb8cc.26941576376
158 KB
sha256:5f2176b9660d8299d812517490f927f9cf2868bacc4e6975cc3f38beaf17b297
ds18b20-verifier-esp32-0.0.0-9e8eb8cc.26941576376
148 KB
sha256:0e9f59a52cbdbd0940049a962be672b107624cd0b0f85c9a19d2f407cefb9f61
ds18b20-verifier-esp32s2-0.0.0-9e8eb8cc.26941576376
144 KB
sha256:86db41cdf96f614edf6b5f4dcf4111dcdc6f160732eb644ff1022d671727a72d
ds18b20-verifier-esp32s3-0.0.0-9e8eb8cc.26941576376
159 KB
sha256:6e97561f30d9355e9b4d8125e98fb3c972c5b995525a1af9206520f709a8a8e2
sht4x-verifier-esp32-0.0.0-9e8eb8cc.26941576376
158 KB
sha256:ffbc25ebfe7fe47bf87098ffe071724e151438928e592cc7a3e65ad68203b214
sht4x-verifier-esp32s2-0.0.0-9e8eb8cc.26941576376
150 KB
sha256:78fb25940314d95f4dd261e01cf3885c2b493d2be41948e65e3ddb38c98ac7a8
sht4x-verifier-esp32s3-0.0.0-9e8eb8cc.26941576376
164 KB
sha256:fef7f7da7bcd97dd2c387ea96c5a95c5deb1ebef5b810b6881189e5b0fd94249
unittest-esp32-0.0.0-9e8eb8cc.26941576376
764 KB
sha256:bcff62a92a00693c26b178c8cfdf23108201816cfcc71ff942ae45fbbd9312cb
unittest-esp32s2-0.0.0-9e8eb8cc.26941576376
738 KB
sha256:0b93ad4e73b345dc29728fa6499010046630bf8282eca1302d661f8b52723a05
unittest-esp32s3-0.0.0-9e8eb8cc.26941576376
749 KB
sha256:8c7666e9aed0e8f0ac9595c52bae35b4c60fb55074cd785ce834824cb956d522