Skip to content

Add wolfBoot support for STM32G4 #937

Add wolfBoot support for STM32G4

Add wolfBoot support for STM32G4 #937

Triggered via pull request May 12, 2026 17:31
Status Success
Total duration 7m 4s
Artifacts 12

test-build-cmake-windows.yml

on: pull_request
Matrix: Build on Windows
Fit to window
Zoom out
Zoom in

Annotations

12 warnings and 12 notices
Build on Windows (stm32c0)
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/upload-artifact@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 on Windows (stm32h5)
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/upload-artifact@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 on Windows (stm32g0)
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/upload-artifact@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 on Windows (stm32l4)
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/upload-artifact@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 on Windows (stm32l5)
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/upload-artifact@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 on Windows (stm32f1)
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/upload-artifact@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 on Windows (stm32h7)
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/upload-artifact@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 on Windows (stm32l0)
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/upload-artifact@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 on Windows (stm32wb)
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/upload-artifact@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 on Windows (stm32u5)
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/upload-artifact@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 on Windows (stm32f7)
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/upload-artifact@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 on Windows (stm32f4)
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/upload-artifact@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 on Windows (stm32c0)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build on Windows (stm32h5)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build on Windows (stm32g0)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build on Windows (stm32l4)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build on Windows (stm32l5)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build on Windows (stm32f1)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build on Windows (stm32h7)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build on Windows (stm32l0)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build on Windows (stm32wb)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build on Windows (stm32u5)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build on Windows (stm32f7)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build on Windows (stm32f4)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

Artifacts

Produced during runtime
Name Size Digest
wolfboot-stm32c0
158 KB
sha256:d6607690067af414b7b258f6903f6791babcc1b3a0d0ca5594718153cc6634b4
wolfboot-stm32f1
164 KB
sha256:42c1dcf141bf487c60b05b77085b64b82dd250e517967a160fa4786225309193
wolfboot-stm32f4
167 KB
sha256:6573fb92eb02f8219fc1af3deb3089d66a8425dde0bbb87b73042385eb1f1cb4
wolfboot-stm32f7
166 KB
sha256:cf1fe264935e720ebe5c5bcae8702472256e0b853a1957c8eb9db2db6d881913
wolfboot-stm32g0
30.5 KB
sha256:fcffd1a332cc285626c5503b5db65f23b34464d02df83e4f30b7c51b6db1568d
wolfboot-stm32h5
747 KB
sha256:ed9b2bc990811e3033a7e4eebc64759247560738dd24ca8422b55632bad4deff
wolfboot-stm32h7
37.4 KB
sha256:038fdd16af81b826f931c12128cd6dddbafb652a650f185d19bc785b66fad549
wolfboot-stm32l0
35.4 KB
sha256:b4029e8a3dbdc8799b9c03b844e6abbfa9c993002ae4bf104be647ddbdad1e6f
wolfboot-stm32l4
301 KB
sha256:0be19e22194d5b2e0a26bcba43ca08962ac72bd8b7b54dbbc29dde7a4522e9c5
wolfboot-stm32l5
1.96 KB
sha256:b3ee56d72d51618f7225f3a0765683ddb176b19cad369735f209dc2d036ed5cf
wolfboot-stm32u5
36.7 KB
sha256:65cb36ca62d6172133ee808315d0b22032b0a351f78028d08f9284d0bc472794
wolfboot-stm32wb
1.96 KB
sha256:df8319f4d2967abe5227acce8e6abe3df11e9db9e9fc5f17acc640e5407ba3c3