Skip to content

release: do not build the x86_64 test port - #7

Merged
JohnAmadis merged 1 commit into
mainfrom
claude/dmspi-release-skip-x86
Sep 29, 2026
Merged

JohnAmadis merged 1 commit into
mainfrom
claude/dmspi-release-skip-x86

Conversation

@JohnAmadis

Copy link
Copy Markdown
Contributor

Fixes the failed v0.1 release (run 36579012755, job "Build dmspi for x86_64": dmgpio_types.h: No such file or directory).

Cause

The release matrix builds every family that has a src/port/*/port.c. Since f869762 that includes x86_64, the software-loopback port that CI uses to run test_dmspi. That port is never published.

A full build with DMOD_CPU_FAMILY=x86_64 fetches the dmgpio headers for x86_64, and dmgpio only publishes stm32f4/stm32f7 packages. ci.yml already works around this by building only dmspi_port for x86_64 (see the comment there). release.yml had no such exception, and v0.1 is the first dmspi release, so this is the first time it failed.

Fix

The family discovery in release.yml skips x86_64. The matrix is now ["stm32f4","stm32f7"], and those builds are the same as the CI family jobs that pass on main.

After merging

The v0.1 release has no assets. Either delete the v0.1 release and tag and create it again, or create v0.1.1. Either way, the release has to be created after this is merged, because the release workflow runs from the tagged commit.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TgkwHQKqf6c4DzypSKzZT7


Generated by Claude Code

The release matrix took every src/port/*/port.c, including x86_64 - the
software-loopback stand-in CI uses to run test_dmspi, which is never
published. A full build for it fetches dmgpio headers for x86_64, which
dmgpio does not publish, so the v0.1 release failed. CI already builds
only dmspi_port for x86_64; the release now skips it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TgkwHQKqf6c4DzypSKzZT7
@JohnAmadis
JohnAmadis merged commit 09085f1 into main Sep 29, 2026
5 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.

2 participants