Build release binaries for Linux, macOS and Windows - #6
Merged
Merged
Conversation
Each tag builds five targets, attaches the archives with SHA-256 checksums and build provenance to the GitHub release, and publishes to crates.io only when every target built. install.sh installs a checked binary, and cargo binstall finds the archives. CI also tests on macOS and Windows.
Imports and tests that only Unix uses are gated to it. The README installs release binaries first.
Repository-relative paths are built with / on every platform, so path rules (Next.js routes, Django modules, documentation roles) match on Windows and reports, requests and baselines name a file the same way everywhere. Requests on Unix are unchanged.
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.
What and why
Phase 2 of the roadmap: installing JevGate no longer needs a Rust toolchain.
build.ymlbuildsx86_64/aarch64Linux (static musl),aarch64/x86_64macOS andx86_64Windows, smoke-tests each native binary, and writes a.sha256per archive. It runs on tags throughrelease.yml, and on pull requests that change the build or the dependencies.release.ymlpublishes only when every target built, and attaches the archives,SHA256SUMSand build provenance (gh attestation verify) to the GitHub release. A rerun attaches only missing archives.install.shinstalls a checked binary into~/.local/bin;cargo binstall jevgatefinds the same archives. The README's Install section leads with them.rust-cache./on every platform. Before, Windows builds named filessrc\app.ts, so path rules (Next.js routes, Django modules, documentation roles) missed files there, and reports and baselines differed by platform.How it was checked
install.shand the binstall metadata; the Linux binaries are static-pie.check --rule all --include-tests --dry-run --show-requestsproduces byte-identical request bodies before and after the path change on four unrelated repositories, so answer caches stay valid.install.sh: shellcheck clean.Merge this together with the 0.17.0 release: the README's install commands need a release that has binaries.