Skip to content

Ready for 4.2.3 - #561

Open
rexut wants to merge 11 commits into
v4.2-branchfrom
v4.2-next
Open

rexut wants to merge 11 commits into
v4.2-branchfrom
v4.2-next

Conversation

@rexut

@rexut rexut commented Nov 14, 2026

Copy link
Copy Markdown
Member
  • devcontainer: bump Zephyr CI container to v0.28.4
  • ci: github: update Github actions versions
  • ci: github: qa: disable test report annotation (avoid timed out errors in infrastructure, known and addressed problem)
  • release: add missing dependent modules to notes for 4.2.0 - 4.2.3

Update:

  * Zephyr SDK to 0.17.4

Added:

  * Esptool (>=5.0.2)

Signed-off-by: Stephan Linz <linz@li-pro.net>
Update Github actions to their latest versions:

- actions/checkout@v5 -> actions/checkout@v7
- actions/github-script@v8 -> actions/github-script@v9
- actions/labeler@v6 -> actions/labeler@v7
- actions/stale@v10 -> actions/stale@v11
- actions/upload-artifact@v4 -> actions/upload-artifact@v7
- astral-sh/setup-uv@v6 -> astral-sh/setup-uv@v10.3.3
- jlumbroso/free-disk-space@v1.3.1 -> jlumbroso/free-disk-space@v2.0.0
- mikepenz/action-junit-report@v5 -> mikepenz/action-junit-report@v6
- tiacsys/clean-after-action@v3 -> tiacsys/clean-after-action@v4
- zephyrproject-rtos/action-manifest@main ->
  zephyrproject-rtos/action-manifest@v2.0.0

Signed-off-by: Stephan Linz <linz@li-pro.net>
Due to the rapidly increasing number of tests and samples against all
supported platforms, the underlying build infrastructure is currently
experiencing persistent failures in the GitHub action responsible for
annotating the generated test reports. This is now leading to near
daily false-positive failures of the entire QA test chain due to the
following error message, even at the end of successfully completed
test runs:

    Error: timed out waiting for file … … …

Until a solution can be found, the processing and display of test
results for the samples will be disabled, in the hope that fewer
false alarms will be triggered from now on. The QA test chain should
only fail and trigger an alert in the event of actual errors.

Signed-off-by: Stephan Linz <linz@li-pro.net>
@github-actions

Copy link
Copy Markdown

You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds.

Note: This comment is automatically posted by the Documentation Publishing GitHub Action.

Today, in 2026, the QA integration test on real target (HiL) fails with
an infrastructure error:

   Failed to download and build `capstone==4.0.2`
   The built wheel `capstone-4.0.2-py3-none-manylinux1_aarch64.whl`
   is not compatible with the current Python 3.12 on Linux aarch64

Since Bridle v4.2 is out of support and has only historival relevance,
the test can skip; no longer supported!

Signed-off-by: Stephan Linz <linz@li-pro.net>
Added the dependency on CMSIS 6, Bouffalo Lab and WCH HAL to the
list of modules imported from Zephyr. This entry has been missing
since release v4.2.0.

Signed-off-by: Stephan Linz <linz@li-pro.net>
Added the dependency on CMSIS 6, Bouffalo Lab and WCH HAL to the
list of modules imported from Zephyr. This entry has been missing
since release v4.2.0.

Signed-off-by: Stephan Linz <linz@li-pro.net>
Added the dependency on CMSIS 6, Bouffalo Lab and WCH HAL to the
list of modules imported from Zephyr. This entry has been missing
since release v4.2.0.

Signed-off-by: Stephan Linz <linz@li-pro.net>
Added the dependency on CMSIS 6, Bouffalo Lab and WCH HAL to the
list of modules imported from Zephyr. This entry has been missing
since release v4.2.0.

Signed-off-by: Stephan Linz <linz@li-pro.net>
Add 4.2.3 tag to release list to be shown on documentation side bar.

Signed-off-by: Stephan Linz <linz@li-pro.net>
Provide highlights and changelogs.

Signed-off-by: Stephan Linz <linz@li-pro.net>
Final 4.2.3 tag.

Signed-off-by: Stephan Linz <linz@li-pro.net>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant