Skip to content

Release workflow: deliver per-platform binaries - #4

Merged
adolfousier merged 1 commit into
mainfrom
ci/release-binaries
Sep 21, 2026
Merged

adolfousier merged 1 commit into
mainfrom
ci/release-binaries

Conversation

@adolfousier

Copy link
Copy Markdown
Owner

Releases v0.1.11..v0.1.15 shipped source tarballs only, no binaries.

Matrix: linux amd64/arm64 + windows amd64 on hosted runners; both darwin targets on the new self-hosted mac-studio-ratifact runner (macOS bills 10x hosted; the Mac builds them free and natively). Pattern mirrors the opencrabs release workflow: tag-on-main verification, self-hosted rustup isolation guard, SHA256SUMS, changelog-extracted notes, idempotent --clobber upload. Dropped for this repo: crates.io publish (not on the registry), RTK bundling.

Caveat called out inline: no --locked because Cargo.lock is gitignored. Tracking the lockfile is the natural follow-up.

Config only; no Rust code touched. Binaries ship at the next v* tag.

Releases v0.1.11..v0.1.15 shipped source tarballs only. This
builds ratifact for linux amd64/arm64 and windows amd64 on
hosted runners, and both darwin targets on the self-hosted
mac-studio-ratifact runner (macOS minutes bill 10x hosted).

Modeled on the opencrabs release workflow: main-branch tag
verification, the self-hosted rustup isolation guard, sha256
checksums, changelog-extracted release notes, idempotent
upload via --clobber. Omitted for this repo: crates.io publish
(ratifact is not on the registry) and RTK bundling.

No --locked: Cargo.lock is gitignored here; noted inline as a
follow-up.
@adolfousier
adolfousier merged commit cd3a764 into main Sep 21, 2026
1 check 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