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.
PR Type
🤖 Generated by PR Agent at 8ce07b4
['Bug fix', 'Enhancement']
PR Description
🤖 Generated by PR Agent at 8ce07b4
.goreleaser.yaml
.4.2.34
inlib/version.go
.4.2.34
.PR Walkthrough
version.go
Revert version bump to `4.2.33`
lib/version.go
4.2.34
to4.2.33
..goreleaser.yaml
Fix deprecated property in `.goreleaser.yaml`
.goreleaser.yaml
archives.format
property.archives.formats
array.CHANGELOG.md
Remove changelog for version `4.2.34`
CHANGELOG.md
4.2.34
.Other Information
I guess I was unaware of the destructive changes in goreleaser's update from v5 to v6.
I don't want to create a broken release, so I reverted the commits in the v4.2.34 release PR and removed the git tags. I am not sure if this is the correct way to handle a failed release in tagpr.