fix release workflow #635
Merged
fix release workflow #635
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
The release workflow for the latest release has failed, because goreleaser got updated to 2.x, and --skip-validate has been removed in that version (see https://goreleaser.com/deprecations/#-skip). We could pin the goreleaser version, but we might as well just update it since it seems a straightforward fix.
tgummerer
commented
Jun 11, 2025
| @@ -0,0 +1,6 @@ | |||
| component: build | |||
| kind: bug-fixes | |||
| body: Fix release process | |||
There was a problem hiding this comment.
This probably doesn't deserve a changelog, but it's going to be useful to release a .1 release that hopefully succeeds.
justinvp
approved these changes
Jun 11, 2025
julienp
approved these changes
Jun 11, 2025
Merged
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jun 11, 2025
To be merged after #635 merges.
tgummerer
added a commit
that referenced
this pull request
Jun 12, 2025
The first attempt at this was in #635, but it didn't fix it completely. I think this brings the .goreleaser.yml to the correct state, but only release CI will tell if I'm right.
tgummerer
added a commit
that referenced
this pull request
Jun 12, 2025
The first attempt at this was in #635, but it didn't fix it completely. I think this brings the .goreleaser.yml to the correct state, but only release CI will tell if I'm right.
tgummerer
added a commit
that referenced
this pull request
Jun 12, 2025
The first attempt at this was in #635, but it didn't fix it completely. I think this brings the .goreleaser.yml to the correct state, but only release CI will tell if I'm right.
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jun 12, 2025
The first attempt at this was in #635, but it didn't fix it completely. I think this brings the .goreleaser.yml to the correct state, but only release CI will tell if I'm right.
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.
The release workflow for the latest release has failed, because goreleaser got updated to 2.x, and --skip-validate has been removed in that version (see https://goreleaser.com/deprecations/#-skip).
We could pin the goreleaser version, but we might as well just update it since it seems a straightforward fix.
Fixes #632