Skip to content

fix(ci): prepare initial v0.1.0 release - #31

Merged
darwin67 merged 2 commits into
mainfrom
pre-release
Aug 9, 2026
Merged

fix(ci): prepare initial v0.1.0 release#31
darwin67 merged 2 commits into
mainfrom
pre-release

Conversation

@darwin67

@darwin67 darwin67 commented Aug 9, 2026

Copy link
Copy Markdown
Member

Summary

  • keep the first published release at v0.1.0 across the Phoenix and Rust manifests
  • run release-container smoke tests on native AMD64 and ARM64 Blacksmith runners
  • remove the unreliable QEMU dependency from the smoke-test matrix

Why

There are no existing v* tags or GitHub Releases, so the first release should use the synchronized manifest version rather than skip directly to v0.2.0.

PR #28's ARM64 image built successfully, but its AMD64 runner could not execute the image after QEMU setup and failed with exec format error. Native per-architecture runners preserve the build, architecture, and version checks without relying on broken emulation registration.

After this PR merges, the release workflow will refresh release/next and update PR #28 to prepare v0.1.0.

Verification

  • mix precommit — 275 tests passed
  • cargo check --workspace
  • production Docker image build
  • production container reports server version 0.1.0
  • git diff --check

@github-actions github-actions Bot added the fix label Aug 9, 2026
@darwin67
darwin67 merged commit a755f6e into main Aug 9, 2026
17 checks passed
@darwin67
darwin67 deleted the pre-release branch August 9, 2026 07:18
@chaba2-bot chaba2-bot Bot mentioned this pull request Aug 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant