Skip to content
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

Merged
merged 8 commits into from
Jul 13, 2023
Merged

Conversation

dotboris
Copy link
Contributor

@dotboris dotboris commented Jul 13, 2023

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:

  • Configure goreleaser to publish the releases it creates. Having to publish it manually is easy to forget and plain old busywork.
  • Add goreleaser to the CI
  • Clean up existing workflows (simplify names & remove redundant bits)
  • Migrate from goreleaser release ... --rm-dist to goreleaser relrease ... --clean
  • Update actions/setup-go to v4 (we get caching for free 🎉)
  • Use the official action for setting up aws creds (includes a bump to v2). We don't need our fork anymore.
  • Document the release process
  • Add @coveooss/dev-tooling as code owners of the repo

@dotboris dotboris changed the title Fix goreleaser Fix goreleaser & revamp CI & repo in general Jul 13, 2023
@dotboris dotboris marked this pull request as ready for review July 13, 2023 13:21
@dotboris dotboris requested a review from a team July 13, 2023 13:22
- name: Setup Go
uses: actions/setup-go@v3
- uses: actions/checkout@v3
- uses: actions/setup-go@v4
with:
go-version: 1.17
Copy link
Contributor

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
Copy link
Contributor

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.

@dotboris dotboris merged commit c3fecbc into master Jul 13, 2023
@dotboris dotboris deleted the fix-goreleaser branch July 13, 2023 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants