Skip to content

chore(release): prepare v0.1.0 - #214

Merged
tupe12334 merged 1 commit into
mainfrom
release/v0.1.0
Sep 24, 2026
Merged

tupe12334 merged 1 commit into
mainfrom
release/v0.1.0

Conversation

@tupe12334

Copy link
Copy Markdown
Member

Summary

Prep for the first published release, v0.1.0. Cargo.toml is already at 0.1.0, and nothing has been tagged or published before.

  • CHANGELOG: the [Unreleased] entries become [0.1.0] - 2026-09-24, merged with the old [0.1.0] - Initial release list, which was never tagged. A fresh, empty [Unreleased] section stays on top.
  • release.yml: x86_64-apple-darwin now builds on macos-latest instead of macos-13. macos-13 was GitHub's last Intel macOS runner and is retired. That matrix job could never start, and because release and publish depend on the whole build matrix, a tag would have produced no release at all. The arm64 runner cross-builds Intel; the job already installs the target through targets: ${{ matrix.target }}.

After this merges, the release is git tag v0.1.0 && git push origin v0.1.0, which triggers a version check, then the five binary builds, the GitHub release with checksums, and cargo publish.

Blocker for the publish job: the repo has no CARGO_REGISTRY_TOKEN secret (none at repo or org level). It must be set before tagging, or the GitHub release is created and the crates.io publish fails.

Test plan

  • cargo publish --dry-run --locked packages 38 files and verifies
  • cargo build --release --locked --target x86_64-apple-darwin on an arm64 Mac produces a Mach-O 64-bit executable x86_64
  • CI green

🤖 Generated with Claude Code

- CHANGELOG: cut the Unreleased entries as 0.1.0 (2026-09-24), merged
  with the never-tagged "0.1.0 - Initial release" list.
- release.yml: build x86_64-apple-darwin on macos-latest. macos-13, the
  last Intel runner, is retired, so that matrix job could never start and
  would have blocked the GitHub release and crates.io publish.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@tupe12334
tupe12334 marked this pull request as ready for review September 24, 2026 10:51
@tupe12334
tupe12334 merged commit 691b49c into main Sep 24, 2026
13 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