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

Add goreleaser github action #174

Merged
merged 1 commit into from
Oct 1, 2022
Merged

Conversation

breml
Copy link
Contributor

@breml breml commented Apr 9, 2022

Requested in #171 (comment)

@matryer matryer merged commit e85ff8e into matryer:main Oct 1, 2022
@matryer
Copy link
Owner

matryer commented Oct 1, 2022

@breml thanks for this - how does it work?

@breml breml deleted the goreleaser-gh-action branch October 1, 2022 10:58
@breml
Copy link
Contributor Author

breml commented Oct 1, 2022

@matryer The github action does trigger, when ever a new tag containing v[0-9]* is observed. What I normally do is, I create a new release on github and while doing so, I create the new version tag. This then triggers the release pipeline and uploads all the necessary release binaries as artifacts for the release.

While writing this, I just realized, that the regexp for the tag is maybe not the best one. I guess, something link v[0-9.]+ would be better (or even a more sophisticated regexp, which only triggers on a correct semver).

@breml
Copy link
Contributor Author

breml commented Oct 1, 2022

According to https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#patterns-to-match-branches-and-tags, for semver the pattern would be v[0-9]+.[0-9]+.[0-9]+.

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.

2 participants