-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: add goreleaser setup and move out changelog reminder #170
Conversation
Hmm any idea why changelog reminder is not happy with the error UPDATE: OK resolved by moving it out following Osmosis' practice. Now ready for review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Maybe we could update RELEASE_PROCESS.md
file to indicate when binaries will be build ? I imagine it would be when tagging release branch ?
Yes this is already mentioned. And you are right this is done upon tagging |
oh I do not see any mentions there, that upon pushing a tag new binaries will be build and published. There is only mention abut backporitng label |
Ah you are right! Added |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work
- -X github.com/cosmos/cosmos-sdk/version.Version={{ .Version }} | ||
- -X github.com/cosmos/cosmos-sdk/version.Commit={{ .Commit }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏 💯
This PR
make release-snapshot