Add a CPU architecture
Architectures are explicit target opt-ins. New CPU support needs native hardware, bootstrap compilers, upstream tests and ongoing ownership; it is a separate sponsorship opportunity.
- Add an
architectures.jsonprofile with OCI platform and runner labels. Use native runners; emulation alone does not establish release support. - Verify the base and utility images, source/compiler bootstrap, recipe architecture declarations and dependencies support the CPU. Children require parent support.
- Add the architecture to the intended
packages.jsonentries only. Existing targets must not gain architectures implicitly. - Run
make dev-generate,make dev-check, localbuilder-build,buildandtestwithARCH=<profile>. Check native APK architecture, installation and manifest platform descriptors, then publish/review the real utility digest pin.
Workflow matrices and manifest assembly derive from profiles and target opt-ins; no separate hard-coded CPU list belongs in workflow jobs. Consumer pins should identify the multiarchitecture index containing their platform.