This repository was archived by the owner on Sep 4, 2026. It is now read-only.
Repository navigation
chore: convert to push-button release workflow - #471
Merged
Merged
Conversation
1 task
ocobles
reviewed
Jul 8, 2024
| with: | ||
| version: latest | ||
| args: release --rm-dist | ||
| semantic_version: 19.0.5 |
Contributor
There was a problem hiding this comment.
what's the reason to keep 19.0.5? https://github.com/semantic-release/semantic-release/releases/tag/v24.0.0
Contributor
Author
There was a problem hiding this comment.
There's no reason any more. I bumped this version and the conventional commits changelog plugin version.
displague
approved these changes
Jul 10, 2024
|
This issue has been resolved in version 0.23.1 🎉 |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This updates the existing release workflow so that it is run by pushing a button in the GitHub UI rather than creating a tag locally and pushing that tag up to GitHub.
The push-button workflow looks up the previous release and uses Conventional Commit tags to determine the correct next version for the new release. As before, it uses GoReleaser to build the CLI and upload the binaries to the GitHub release.
I have confirmed on my fork that this works up through the GoReleaser step.
Closes #364