Add a tagpr and goreleaser release flow - #11
Merged
Merged
Conversation
Merged
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.
Why
eda has no release process. There are no tags, no changelog, and
go installis the only way in. The binary also cannot say which version it is.What
eda versionsubcommand, backed by a constant inmain.gothat tagpr maintains..tagpr,.goreleaser.ymland a release workflow: tagpr opens the release pull request and tags on merge, then goreleaser publishes linux and darwin binaries for amd64 and arm64.go test ./...in the goreleaser job, since tagpr's release pull request is created withGITHUB_TOKENand never triggers CI.Merging this starts the flow: the next push to main opens a release pull request for v0.0.1.