fix: Update goreleaser workflow to fix warnings and artifact generation #726
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.
What this PR does / why we need it:
version.txt
is changed. This fixes the issue where the tag workflow creates the tag, but the release workflow is not triggered - https://github.com/orgs/community/discussions/27028#discussioncomment-3254360 which requires a users to run the workflow dispatch manually to start the release workflowdraft
andprerelease
arguments - this was leaving the release in a draft mode when I tested the workflow https://github.com/clowdhaus/aws-iam-authenticator/releases/tag/untagged-5156821368231e9f9e67go.sum
updates are due to runninggo mod tidy
to pass CI checks - these were introduced in cc68d23Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #720
Fixes #722