Skip to content

Migrate to build-mpy-native-module action - #1

Merged
BrianPugh merged 2 commits into
mainfrom
migrate-to-build-mpy-native-module-action
Jul 13, 2026
Merged

Migrate to build-mpy-native-module action#1
BrianPugh merged 2 commits into
mainfrom
migrate-to-build-mpy-native-module-action

Conversation

@BrianPugh

Copy link
Copy Markdown
Owner

Migrates the template's build workflow to BrianPugh/build-mpy-native-module@v1, following the same migration tamp just completed (BrianPugh/tamp#341). The hand-rolled 42-job matrix (5 MicroPython versions × 9 architectures, manual toolchain installs/caching, static-const sed) becomes a single action invocation: 142 lines deleted, 66 added.

  • Naming change: artifacts are now pythontemplate-<ver>-mpy6.3-armv6m.mpy instead of -mpy1.23- — the mpy subversion + architecture pair is what actually determines device compatibility, and redundant builds (v1.23/1.24/1.25/1.26 all produce identical-compatibility mpy 6.3) collapse to one.
  • Better test coverage: x64 unit tests now run per mpy subversion against the matching MicroPython runtime (v1.22.2 for 6.2, v1.27.0 for 6.3), instead of only against the build's own version.
  • Bug fix: the release tarball previously interpolated env.VERSION in the release_upload job where it was never set, producing pythontemplate-.tar.gz; the version is now computed in that job.
  • Bootstrap-safe: the workflow keeps the literal pythontemplate strings that bootstrap rewrites across *.yaml files.

🤖 Generated with Claude Code

BrianPugh and others added 2 commits July 9, 2026 20:07
Replaces the hand-rolled 42-job matrix (5 MicroPython versions x 9
architectures with manual toolchain setup, caching, and the static
const sed) with a single invocation of
BrianPugh/build-mpy-native-module@v1 building mpy 6.2 and 6.3 for all
architectures.

Artifacts are now named by mpy subversion
(pythontemplate-<ver>-mpy6.3-armv6m.mpy instead of -mpy1.23-), since
the subversion + architecture pair is what determines device
compatibility. x64 unit tests now run per mpy subversion against the
matching MicroPython runtime. Also fixes the release tarball name,
which previously interpolated an unset VERSION in the release job.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@BrianPugh
BrianPugh merged commit f373410 into main Jul 13, 2026
4 checks passed
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