Skip to content

Add wolfBoot support for STM32G4 #938

Add wolfBoot support for STM32G4

Add wolfBoot support for STM32G4 #938

Triggered via pull request May 12, 2026 17:58
Status Success
Total duration 17m 11s
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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (stm32g0)
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 (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 (stm32l5)
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 (stm32f1)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build on Windows (stm32c0)
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 (stm32l4)
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
Build on Windows (stm32f7)
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:f1fbca2a200367f87a7bb56d7e9b4fcced9a5fe725a7703d8802b99d8c335c95
wolfboot-stm32f1
164 KB
sha256:4e4a802989f9d6da6a92a27d18b0191cd24758cce5a0687f7a84147d89687ff5
wolfboot-stm32f4
167 KB
sha256:0a5c3a30c7d1bdaeba986b3abbcc939b3cae4d33cce6ef60f4678955ffacc7be
wolfboot-stm32f7
166 KB
sha256:4ca433bba9e72c0e59be9d16b5b4a90755e53457a40357b278b8cde4d289cda3
wolfboot-stm32g0
30.5 KB
sha256:4350c14b9d3251cf4f71e3cda212943bcd0508e6f7671ac87f478ea8c7c0d3d4
wolfboot-stm32h5
747 KB
sha256:172550c50830c91c0a9448be80c165fe15f81afc5eaec01cff02eeeb002ebab4
wolfboot-stm32h7
37.4 KB
sha256:b58defa1d2bc1de98fcb7d8b9f39e12be20d75339cd893806555038328d6cc52
wolfboot-stm32l0
35.4 KB
sha256:5202287d924d357cc2dc09a2db359b7deea16a2cb2dd67d2c7e2988339b418f7
wolfboot-stm32l4
301 KB
sha256:0164760b41ab85f2fc45a99b951ad3d5babbed60de9b88da4bf2a7f9bb8ef791
wolfboot-stm32l5
1.96 KB
sha256:80b87c0bb0dee4f40ead8263fb343f8838238b2308fdd496d5b966be7d973e47
wolfboot-stm32u5
36.6 KB
sha256:30451d03c2cd56e6c3452f7c911976123fdd129b08253210609cc63058cc8f0a
wolfboot-stm32wb
1.96 KB
sha256:f0c126152352353b59f9cf530fe53af9bee42da519db5f9938208d649320f244