Skip to content

chore(release): v0.1.0 - #28

Open
chaba2-bot[bot] wants to merge 1 commit into
mainfrom
release/next
Open

chore(release): v0.1.0#28
chaba2-bot[bot] wants to merge 1 commit into
mainfrom
release/next

Conversation

@chaba2-bot

@chaba2-bot chaba2-bot Bot commented Aug 8, 2026

Copy link
Copy Markdown

Release

This PR prepares v0.1.0.

  • Commits since last tag: 62
  • Diff: unavailable until the first v* tag exists
  • Source branch: release/next
  • Base branch: main

Notes Preview

[0.1.0] - 2026-08-26

🚀 Features

🐛 Bug Fixes

📚 Documentation

⚙️ Miscellaneous Tasks

🛡️ Security

@github-actions github-actions Bot added the chore label Aug 8, 2026
@chaba2-bot
chaba2-bot Bot force-pushed the release/next branch 2 times, most recently from f7b3c4a to 8edf120 Compare August 9, 2026 01:14
darwin67 added a commit that referenced this pull request Aug 9, 2026
## 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`

---------

Co-authored-by: Darwin D Wu <darwin67@users.noreply.github.com>
@chaba2-bot chaba2-bot Bot changed the title chore(release): v0.2.0 chore(release): v0.1.0 Aug 9, 2026
@chaba2-bot
chaba2-bot Bot force-pushed the release/next branch 18 times, most recently from ef9993b to 42fe3c5 Compare August 15, 2026 07:31
@chaba2-bot
chaba2-bot Bot force-pushed the release/next branch 5 times, most recently from f8f971c to 94a7e57 Compare August 22, 2026 18:25
@chaba2-bot
chaba2-bot Bot force-pushed the release/next branch 3 times, most recently from ecf96a3 to ad91eb4 Compare August 26, 2026 19:18
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.

0 participants