ci: build firmware for all board variants on firmware changes#4
Merged
Conversation
The existing CI validates slice.yaml only - firmware changes merged with no build check at all, which is how a build-breaking change could land silently (the anolis bench campaign's padded-read regression era made the gap visible). Build all four board variants (gen1/gen2 x nano/nanoevery) via PlatformIO on any firmware/ change, with the PlatformIO toolchain cached.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The existing
ci.ymlvalidatesslice.yamlonly — firmware changes merge with no build check (verified: the July firmware fix PRs ran GitGuardian alone). This adds apio runmatrix over all four board variants (gen1/gen2 × nano/nanoevery), path-filtered tofirmware/**, with the PlatformIO toolchain cached. Registry deps (CRUMBS ^0.12.4, bread-crumbs-contracts ^0.4.3) resolve from the published registry — both current versions are live.