ci(core): report debuglink/normal artifact sizes separately
What changed, and why it matters
This commit changes a GitHub Actions CI workflow so that firmware artifact sizes are reported separately for 'normal' and 'debuglink' builds instead of being merged into one list. It is purely a reporting/visibility tweak in the build pipeline and does not touch any firmware code, cryptography, or device behavior.
No security action needed. This is a benign CI reporting change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies .github/workflows/core.yml. It replaces a single artifacts download step that merged all core-firmware-* artifacts into core/build with a download into an artifacts/ directory, then loops over build_type values ‘normal’ and ‘debuglink’ and prints per-type file listings into the GitHub step summary. No firmware source, build scripts producing binaries, secrets handling, or access controls are changed.
Changed components
.github/workflows/core.ymlInspect captured patch +9 / −3
diff --git a/.github/workflows/core.yml b/.github/workflows/core.yml
index c6fcd117..e6b9734c 100644
--- a/.github/workflows/core.yml
+++ b/.github/workflows/core.yml
@@ -697,10 +697,16 @@ jobs:
- uses: actions/download-artifact@70fc10c6e5e1ce46ad2ea6f2b72d43f7d47b13c3 # actions/download-artifact@v8.0.0
with:
pattern: core-firmware-*
- path: core/build
- merge-multiple: true
+ path: artifacts
- run: |
- (echo '```'; find core/build/ -name '*-*-*.bin' -printf "%-40f %10s\n" | sort; echo '```') >> $GITHUB_STEP_SUMMARY
+ for build_type in normal debuglink
+ do
+ (echo '##' ${build_type}; \
+ echo '```'; \
+ find artifacts/core-firmware-*-${build_type}/ -name '*-*-*.bin' -printf "%-40f %10s\n" | sort; \
+ echo '```') >> $GITHUB_STEP_SUMMARY
+ done
+
core_ui_comment:
name: Post comment with UI diff URLs
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.