chore: Add Embed Fire and WonderK to Actions build script
What the developer wrote
Authored by odudex
chore: Add Embed Fire and WonderK to Actions build script
What changed, and why it matters
This commit simply adds two new hardware device targets (Embed Fire and WonderK) to the project's automated build script. It is a routine configuration change with no security relevance.
No security action needed. Review as normal CI/CD maintenance if desired.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change extends the GitHub Actions build matrix in .github/workflows/build.yml to include two additional MaixPy device targets: maixpy_embed_fire and maixpy_wonder_k. It adds corresponding build, extract, and upload steps mirroring the existing pattern for other devices. No code logic, dependencies, secrets, permissions, or network exposure is changed.
Changed components
.github/workflows/build.ymlInspect captured patch +49 / −1
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 597a7e1..f773845 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -11,7 +11,7 @@ jobs:
build:
strategy:
matrix:
- device: [maixpy_m5stickv, maixpy_amigo, maixpy_dock, maixpy_yahboom, maixpy_cube, maixpy_wonder_mv, maixpy_tzt]
+ device: [maixpy_m5stickv, maixpy_amigo, maixpy_dock, maixpy_yahboom, maixpy_cube, maixpy_wonder_mv, maixpy_tzt, maixpy_embed_fire, maixpy_wonder_k]
runs-on: ubuntu-latest
services:
registry:
@@ -209,6 +209,54 @@ jobs:
path: ${{ steps.extract-tzt.outputs.destination }}
name: build-tzt
+ - name: Build for Embed Fire
+ if: matrix.device == 'maixpy_embed_fire'
+ uses: docker/build-push-action@v6
+ with:
+ context: .
+ build-args: DEVICE=maixpy_embed_fire
+ push: true
+ tags: localhost:5000/selfcustody/krux-builder-embed-fire:latest
+ cache-from: type=local,src=/tmp/.buildx-cache
+ cache-to: type=local,dest=/tmp/.buildx-cache-new,mode=max
+ - name: Extract firmware for Embed Fire
+ id: extract-embed-fire
+ if: matrix.device == 'maixpy_embed_fire'
+ uses: shrink/actions-docker-extract@v3
+ with:
+ image: localhost:5000/selfcustody/krux-builder-embed-fire:latest
+ path: /src/firmware/Kboot/build/.
+ - name: Upload firmware for Embed Fire
+ if: matrix.device == 'maixpy_embed_fire'
+ uses: actions/upload-artifact@v4
+ with:
+ path: ${{ steps.extract-embed-fire.outputs.destination }}
+ name: build-embed-fire
+
+ - name: Build for WonderK
+ if: matrix.device == 'maixpy_wonder_k'
+ uses: docker/build-push-action@v6
+ with:
+ context: .
+ build-args: DEVICE=maixpy_wonder_k
+ push: true
+ tags: localhost:5000/selfcustody/krux-builder-wonder-k:latest
+ cache-from: type=local,src=/tmp/.buildx-cache
+ cache-to: type=local,dest=/tmp/.buildx-cache-new,mode=max
+ - name: Extract firmware for WonderK
+ id: extract-wonder-k
+ if: matrix.device == 'maixpy_wonder_k'
+ uses: shrink/actions-docker-extract@v3
+ with:
+ image: localhost:5000/selfcustody/krux-builder-wonder-k:latest
+ path: /src/firmware/Kboot/build/.
+ - name: Upload firmware for WonderK
+ if: matrix.device == 'maixpy_wonder_k'
+ uses: actions/upload-artifact@v4
+ with:
+ path: ${{ steps.extract-wonder-k.outputs.destination }}
+ name: build-wonder-k
+
- name: Move cache
run: |
rm -rf /tmp/.buildx-cache
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.