Repository navigation
ci: release with release-please and GoReleaser - #14
Merged
Merged
Conversation
release-please now runs on main and creates the tag and GitHub release. GoReleaser runs on the published release and uploads the binaries.
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
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.
release-please.yml: on pushes tomainit opens release PRs and, once one is merged, creates the tag and GitHub release.publish-release.ymlruns GoReleaser when a release is published, instead of on tag pushes. GoReleaser is pinned to v2.release-please-config.json: stable versions (versioning: default,prerelease: false).After this merges, release-please picks up the already-merged
release: 0.6.0(#12), still labelledautorelease: pending, and publishes v0.6.0.