Return error if calling function will block host task #1155
h2zerobuild.yml
on: pull_request
build_docs
15s
Matrix: build_arduino-esp32
Matrix: build_bt5_arduino-esp32
Matrix: build_bt5_esp_pio_legacy
Matrix: build_bt5_esp_pioarduino
Matrix: build_bt5_n-able-Arduino
Matrix: build_bt5_n-able-pio
Matrix: build_esp_pio_legacy
Matrix: build_esp_pioarduino
Matrix: build_n-able-Arduino
Matrix: build_n-able-pio
Annotations
96 errors and 41 warnings
|
build_bt5_n-able-pio (examples/Bluetooth_5/NimBLE_extended_server)
Process completed with exit code 1.
|
|
build_bt5_n-able-pio (examples/Bluetooth_5/NimBLE_extended_client)
Process completed with exit code 1.
|
|
build_bt5_n-able-Arduino (examples/Bluetooth_5/NimBLE_extended_client, Generic_nRF52840)
Process completed with exit code 1.
|
|
build_bt5_n-able-Arduino (examples/Bluetooth_5/NimBLE_extended_client, Generic_nRF52840)
One or more compilations failed
|
|
|
|
build_bt5_n-able-Arduino (examples/Bluetooth_5/NimBLE_extended_server, Generic_nRF52840)
Process completed with exit code 1.
|
|
build_bt5_n-able-Arduino (examples/Bluetooth_5/NimBLE_extended_server, Generic_nRF52840)
One or more compilations failed
|
|
|
|
build_bt5_esp_pio_legacy (examples/Bluetooth_5/NimBLE_extended_client)
Process completed with exit code 1.
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32)
Process completed with exit code 1.
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32)
One or more compilations failed
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32)
Compilation failed
|
|
build_esp_pio_legacy (examples/NimBLE_Client)
Process completed with exit code 1.
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32c3)
Process completed with exit code 1.
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32c3)
One or more compilations failed
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32c3)
Compilation failed
|
|
build_esp_pio_legacy (examples/NimBLE_Server)
Process completed with exit code 1.
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32s3)
Process completed with exit code 1.
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32s3)
One or more compilations failed
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32s3)
Compilation failed
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32h2)
Process completed with exit code 1.
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32h2)
One or more compilations failed
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32h2)
Compilation failed
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_client, esp32c3)
Process completed with exit code 1.
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_client, esp32c3)
One or more compilations failed
|
|
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32)
Process completed with exit code 1.
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32)
One or more compilations failed
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32)
Compilation failed
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32s3)
Process completed with exit code 1.
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32s3)
One or more compilations failed
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32s3)
Compilation failed
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_server, esp32c3)
Process completed with exit code 1.
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_server, esp32c3)
One or more compilations failed
|
|
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32c6)
Process completed with exit code 1.
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32c6)
One or more compilations failed
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32c6)
Compilation failed
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32c3)
Process completed with exit code 1.
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32c3)
One or more compilations failed
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32c3)
Compilation failed
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_server, esp32h2)
Process completed with exit code 1.
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_server, esp32h2)
One or more compilations failed
|
|
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_server, esp32s3)
Process completed with exit code 1.
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_server, esp32s3)
One or more compilations failed
|
|
|
|
build_bt5_esp_pio_legacy (examples/Bluetooth_5/NimBLE_extended_server)
Process completed with exit code 1.
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF52840)
Process completed with exit code 1.
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF52840)
One or more compilations failed
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF52840)
Compilation failed
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF51822:chip=xxaa)
Process completed with exit code 1.
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF51822:chip=xxaa)
One or more compilations failed
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF51822:chip=xxaa)
Compilation failed
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF52833)
Process completed with exit code 1.
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF52833)
One or more compilations failed
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF52833)
Compilation failed
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF52833)
Process completed with exit code 1.
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF52833)
One or more compilations failed
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF52833)
Compilation failed
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF52832)
Process completed with exit code 1.
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF52832)
One or more compilations failed
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF52832)
Compilation failed
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_server, esp32c6)
Process completed with exit code 1.
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_server, esp32c6)
One or more compilations failed
|
|
|
|
build_n-able-pio (examples/NimBLE_Server)
Process completed with exit code 1.
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF52832)
Process completed with exit code 1.
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF52832)
One or more compilations failed
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF52832)
Compilation failed
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF52840)
Process completed with exit code 1.
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF52840)
One or more compilations failed
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF52840)
Compilation failed
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32h2)
Process completed with exit code 1.
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32h2)
One or more compilations failed
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32h2)
Compilation failed
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_client, esp32s3)
Process completed with exit code 1.
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_client, esp32s3)
One or more compilations failed
|
|
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32c6)
Process completed with exit code 1.
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32c6)
One or more compilations failed
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32c6)
Compilation failed
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_client, esp32h2)
Process completed with exit code 1.
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_client, esp32h2)
One or more compilations failed
|
|
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_client, esp32c6)
Process completed with exit code 1.
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_client, esp32c6)
One or more compilations failed
|
|
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF51822:chip=xxaa)
Process completed with exit code 1.
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF51822:chip=xxaa)
One or more compilations failed
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF51822:chip=xxaa)
Compilation failed
|
|
build_n-able-pio (examples/NimBLE_Client)
Process completed with exit code 1.
|
|
build_bt5_esp_pioarduino (examples/Bluetooth_5/NimBLE_extended_client)
Process completed with exit code 1.
|
|
build_esp_pioarduino (examples/NimBLE_Client)
Process completed with exit code 1.
|
|
build_esp_pioarduino (examples/NimBLE_Server)
Process completed with exit code 1.
|
|
build_bt5_esp_pioarduino (examples/Bluetooth_5/NimBLE_extended_server)
Process completed with exit code 1.
|
|
build_bt5_n-able-pio (examples/Bluetooth_5/NimBLE_extended_server)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
build_bt5_n-able-pio (examples/Bluetooth_5/NimBLE_extended_client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
build_bt5_n-able-Arduino (examples/Bluetooth_5/NimBLE_extended_client, Generic_nRF52840)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_bt5_n-able-Arduino (examples/Bluetooth_5/NimBLE_extended_server, Generic_nRF52840)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_bt5_esp_pio_legacy (examples/Bluetooth_5/NimBLE_extended_client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32c3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_esp_pio_legacy (examples/NimBLE_Client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
build_esp_pio_legacy (examples/NimBLE_Server)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32s3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32h2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_client, esp32c3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32s3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_server, esp32c3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_arduino-esp32 (examples/NimBLE_Client, esp32c6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32c3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_server, esp32h2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_server, esp32s3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_bt5_esp_pio_legacy (examples/Bluetooth_5/NimBLE_extended_server)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF52840)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF51822:chip=xxaa)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF52833)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF52833)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_n-able-Arduino (examples/NimBLE_Client, Generic_nRF52832)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_server, esp32c6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_n-able-pio (examples/NimBLE_Server)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF52832)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF52840)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32h2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_client, esp32s3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_arduino-esp32 (examples/NimBLE_Server, esp32c6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_client, esp32h2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_bt5_arduino-esp32 (examples/Bluetooth_5/NimBLE_extended_client, esp32c6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_n-able-Arduino (examples/NimBLE_Server, Generic_nRF51822:chip=xxaa)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4.5.0. 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/
|
|
build_n-able-pio (examples/NimBLE_Client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
build_bt5_esp_pioarduino (examples/Bluetooth_5/NimBLE_extended_client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
build_esp_pioarduino (examples/NimBLE_Client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
build_esp_pioarduino (examples/NimBLE_Server)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
build_bt5_esp_pioarduino (examples/Bluetooth_5/NimBLE_extended_server)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|