Trigger release
Now that the configuration files have been set up for GoReleaser and GitHub Actions, and the publisher tokens to give access to make changes to the repositories are also created and shared, we are ready to trigger a release with the next step of the workflow: tag and push the code. Before we do so, let’s take a step back and discuss what happens when you trigger the goReleaser job:
- Preparation: GoReleaser checks the configuration files, validates the environment, and sets up the necessary environment variables
- Building: Builds the Go binary and compiles it for multiple platforms (such as Windows, Linux, and macOS)
- Versioning: Generates a new version number based on the existing version and the user’s configuration
- Creating the release artifacts: Generates the release artifacts, such as tarballs, deb/rpm packages, and zip files for each platform
- Creating a Git tag: Creates a new Git tag for the release, which is used to reference...
