build release binaries for linux, macos and windows - #40
Merged
Merged
Conversation
CanReader
force-pushed
the
ci/release-binaries
branch
from
October 1, 2026 14:22
9652591 to
bebe91c
Compare
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 this changes
Tagging a release now also builds the example programs and attaches them to the GitHub release:
Each archive has the examples plus README and LICENSE, there is a
SHA256SUMSnext to them, and every archive gets a build provenance attestation. Release notes are now grouped by PR label (.github/release.yml).Why
So people can try FastNN without installing Rust, and so a release looks like a release.
Any PR touching
release.ymlruns the whole pipeline minus the publish steps, this one included, so the builds below are the real test.How it was verified