cutting-releases

Automating git tagging and GitHub releases involves creating git tags, building binaries with GoReleaser, and generating the corresponding GitHub release entries. This Skill streamlines that continuous integration workflow by handling these steps automatically.

Managing semantic versioning for software releases requires applying correct version tags to your git history. This Skill provides versioning guidance according to semantic versioning principles to ensure your release tags are formatted correctly before building binaries.

Yes, a GoReleaser setup is required to automate the software release process. The Skill relies on GoReleaser to build release binaries from your git tags, and it also requires git and GitHub access to fully automate the workflow.

You can verify software release integrity by executing post-flight checks after the release is created. This Skill runs a set of post-flight verifications to ensure release integrity and will notify you if any issues are detected.

This release automation works with your continuous integration workflow by managing the end-to-end release pipeline. It handles git tagging, binary building via GoReleaser, and GitHub release creation directly within your established CI process.

Cutting a software release requires both git and GitHub access because the process spans local and remote environments. Git manages the foundational version tags, while GitHub hosts the public release entries and distributes the built GoReleaser binaries.