-
Notifications
You must be signed in to change notification settings - Fork 18
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
Fix goreleaser & revamp CI & repo in general #402
Conversation
- name: Setup Go | ||
uses: actions/setup-go@v3 | ||
- uses: actions/checkout@v3 | ||
- uses: actions/setup-go@v4 | ||
with: | ||
go-version: 1.17 |
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.
1.17 is getting old, could we either bump this one or matrix (like we for os) it to test more modern go versions as well maybe?
1. Create a tag with the format `vX.Y.Z` | ||
|
||
You might be tempted to create a release through GitHub to create the tag. | ||
Don't do that. We have a GitHub workflow in place that will create a release |
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.
oof that's what I always did 😅 I think it just updates the release if it exists, but I'm not going to be the workflow breaker.
The release is all broken because goreleaser was updated but we didn't migrate the config.
At least that's how it started. I realized that this repo was in need of some love so I did the following:
goreleaser
to publish the releases it creates. Having to publish it manually is easy to forget and plain old busywork.goreleaser
to the CIgoreleaser release ... --rm-dist
togoreleaser relrease ... --clean
actions/setup-go
to v4 (we get caching for free 🎉)