Release/9.1 to master - #11861
Conversation
Backport of #11856 (merged to maintenance-10.x) to release/9.1. The PR Test Builds workflow is triggered by workflow_run, which executes from the default branch (master); master is fed from release/9.1, so this must land here (and ride 9.1 -> master) for PR test-build releases to attach .uf2. - ci.yml: upload ./build/*.uf2 alongside *.hex in the firmware matrix and single-target jobs (upload-artifact unions the globs and defaults if-no-files-found: warn, so jobs without a .uf2 are unaffected). - pr-test-builds.yml: attach hexes/*.uf2 to the PR test-build release when present (guarded so PRs with no .uf2 don't pass a literal unmatched glob), and mention it in the release notes. The .uf2 itself is produced by RP2350 targets via the in-tree elf2uf2.py (python3, always on runners); no picotool dependency.
…ets-91 ci: publish .uf2 test builds (RP2350) alongside .hex in PR releases
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
Branch Targeting SuggestionYou've targeted the
If This is an automated suggestion to help route contributions to the appropriate branch. |
PR Summary by QodoPublish UF2 firmware in PR test-build releases
AI Description
Diagram
High-Level Assessment
Files changed (2)
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can add REVIEW.md to your repo root and Qodo follows it on every PR |
No description provided.