Skip to content

fix: include CH32H* family in metapac gen targets - #41

Merged
andelf merged 1 commit into
mainfrom
fix/gen-include-ch32h4
May 21, 2026
Merged

fix: include CH32H* family in metapac gen targets#41
andelf merged 1 commit into
mainfrom
fix/gen-include-ch32h4

Conversation

@andelf

@andelf andelf commented May 21, 2026

Copy link
Copy Markdown
Contributor

Summary

  • ./d gen enumerates families explicitly when invoking ch32-metapac-gen
  • PR Add CH32H4 family (CH32H417/H416/H415) support #39 added CH32H417/H416/H415 yaml files under data/chips/ but didn't add CH32H* to the gen invocation
  • Result: nightly-publish workflow runs against the H4 merge commit (5e8d693) but emits a ch32-metapac that has no H4 chips
  • One-line fix: pass "CH32H*" alongside the other family globs

Test plan

  • rm -rf build && ./d gen from this branch produces 10 H4 chip directories under build/ch32-metapac/src/chips/ (5 SKUs × V3F/V5F cores)
  • Once merged, the next nightly-publish run should ship H4 chips so downstream consumers (e.g. ch32-hal H4 work) can drop their local [patch."https://github.com/ch32-rs/ch32-metapac"]

PR #39 added CH32H417/H416/H415 chip yaml under data/chips/ but the
`./d gen` invocation enumerates families explicitly and was never updated
to pass `CH32H*`, so the published ch32-metapac is missing H4 chips even
on the tag generated from the H4 merge commit (5e8d693).

Add the glob to match the same pattern used for the other families.
@andelf
andelf merged commit 3374711 into main May 21, 2026
1 check passed
@andelf
andelf deleted the fix/gen-include-ch32h4 branch May 21, 2026 00:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant