Add goreleaser commands to Makefile and create a Github Action to run goreleaser #5908
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.
Tracked in: #5904
What is the purpose of the change
This PR focuses on improving the release process through Goreleaser.
Main changes:
Updated .goreleaser.yml to match the previous release structure.
Added release targets to the Makefile:
release
: This target performs a release using Goreleaser. It expects theGITHUB_TOKEN
as an environment variable. It should never be run manually but always via the GitHub Action.release-dry-run
: This target simulates a release without publishing the artifacts. It allows testing the release process without actually creating a new release.release-snapshot
: This target creates a snapshot release without validation or publishing. It can be useful for quickly generating snapshots for testing purposes.Added a release workflow to create a release by running the
make release
command.Add a release workflow to create a release running the
make release
command.Testing and Verifying
I have used the GitHub action to create a test release in my fork.
You can run:
(requires clean git state)
and
to test the process.
Documentation and Release Note
Unreleased
section ofCHANGELOG.md
?Where is the change documented?
x/{module}/README.md
)