Repository navigation
Release binaries named fmsg, and fmsg --version - #17
Merged
Merged
Conversation
Publishing a release builds fmsg for Linux, macOS and Windows on amd64 and arm64 and attaches the archives (fmsg_<os>_<arch>.tar.gz / .zip, flat, stable names so releases/latest/download links work) with checksums.txt. It can also be run by hand for an existing tag. The release build stamps the tag into cmd.version for --version; other builds fall back to the module version, then "dev".
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.
Users get an
fmsgcommand from a download instead of building from source (go installwould name itfmsg-cli)..github/workflows/release.yml: when a release is published, buildsfmsgfor linux/darwin/windows × amd64/arm64 (static,-trimpath -s -w) and uploadsfmsg_<os>_<arch>.tar.gz(.zipfor Windows) pluschecksums.txtto it. The archives are flat and their names don't include the version, sohttps://github.com/markmnl/fmsg-cli/releases/latest/download/fmsg_linux_amd64.tar.gzalways gets the newest. It can also be run by hand (Actions → Release → Run workflow) with a tag to build an existing release.fmsg --version: the release build sets it to the tag; other builds use the module version (go install …@v0.3.1) or the VCS stamp, thendev.Tested locally: the workflow's build step produces all six archives with the binary at the top level;
go vetandgo testpass.After merging, publish v0.3.1 and its binaries are built automatically. (Running the workflow for v0.3.0 also works, but those binaries won't have
--version, which isn't in that tag.)🤖 Generated with Claude Code