feat: add release workflow - #35
Merged
Merged
Conversation
This was referenced Jul 2, 2026
Part of the preparation for a crates.io release.
This will release versions of the tool on GH when tags are pushed, but it will also push it to crates.io if it's not a pre-release (i.e. 0.1.0-rc.1). This also moves the "pointer" of the major version for the version resolution of the future gh action so users can do `uses ptsouchlos\embd@v1` in the future.
ptsouchlos
force-pushed
the
feat/release-workflow
branch
from
July 5, 2026 02:50
df9a8a0 to
d1727c6
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
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.
At a minimum, binaries of this tool must be available on GitHub and crates.io so this PR starts this process by adding a release workflow when tags are pushed. This will build the CLI for all platforms, create a GH release and then upload all the artifacts to the GH release. It will also publish the package on crates.io.
This is part 2 of 3 in a stack made with GitButler: