fix: manually generate release candidate tag #105
Merged
Conversation
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
Signed-off-by: matttrach <matt.trachier@suse.com>
This was referenced Aug 27, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Aug 27, 2025
Signed-off-by: matttrach <matt.trachier@suse.com> (cherry picked from commit 5d83b0d)
matttrach
added a commit
that referenced
this pull request
Aug 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Related Issue
Addresses #5
Description
Release-please needs a PR and manual intervention, which undermines the automatic generation of release candidates so we are not going to use release-please for this. Goreleaser needs a tag to generate a release, which would normally be handled by release-please, instead we are generating the RC tag manually in this change.
Testing
actionlint
Not a breaking change.