fix(ci): prepare initial v0.1.0 release - #31
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
v0.1.0across the Phoenix and Rust manifestsWhy
There are no existing
v*tags or GitHub Releases, so the first release should use the synchronized manifest version rather than skip directly tov0.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/nextand update PR #28 to preparev0.1.0.Verification
mix precommit— 275 tests passedcargo check --workspace0.1.0git diff --check