build: publish a binary when a version tag is pushed - #30
Merged
Conversation
CI checked every change but nothing was ever released, so the only way to run termit was to build it. A tag matching v* now builds on an Apple silicon runner, refuses to go on if the tag and Cargo.toml disagree or the binary is not arm64, and attaches a tarball plus SHA256SUMS to a GitHub release whose notes carry the install steps and the checksum. No Intel slice is published. Every measurement in the docs was taken on arm64 and termit has never been run on an Intel Mac; shipping an untested x86_64 binary would claim more than is known. Source builds still work there. The README install section leads with a Homebrew tap, which also avoids the quarantine flag that an unsigned download carries. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GvMacYD6T9EoWqc7C247Hr
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
1 participant
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.
CI checked every change but nothing was ever released, so the only way to run termit was to build it. This adds the release path for
v0.1.0.What happens on a tag
.github/workflows/release.yml, onpushof av*tag (orworkflow_dispatchwith a tag):Cargo.toml's version disagree.cargo test, thencargo build --releaseon an Apple silicon runner.termit+README.md+LICENSEintotermit-<version>-macos-arm64.tar.gz, writesSHA256SUMS.Decisions
Apple silicon only. Every number in the docs was measured on arm64 and termit has never been run on an Intel Mac. Publishing an untested x86_64 slice would claim more than is known, so Intel users build from source, and the README says exactly that.
Not notarised. No Apple Developer account is involved, so a downloaded copy carries the quarantine flag. The README and the release notes both give the one line that clears it. The Homebrew tap avoids the flag entirely, which is why the install section leads with it.
Next, outside this PR
v0.1.0so this runs.tkc/homebrew-termittap with a formula pointing at the released tarball and its checksum, sobrew install tkc/termit/termitworks as the README says.🤖 Generated with Claude Code
https://claude.ai/code/session_01GvMacYD6T9EoWqc7C247Hr