ci: add release pipeline, remove goreleaser config

[fank]

Summary

• Add GitHub Actions release workflow triggered on v* tags
• Builds cross-platform binaries (linux/darwin/windows, amd64/arm64)
• Generates changelog grouped by conventional commit type (feat, fix, perf, docs, refactor, other)
• Creates GitHub Release with install instructions and checksums
• Remove .goreleaser.yml (replaced by self-contained workflow)

Adapted from the atl-cli release pipeline.

Test plan

• CI passes on this PR
• Create a test tag to verify the release workflow

[gemini-code-assist]

Summary of Changes

Hello @fank, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a comprehensive GitHub Actions-based release pipeline, replacing the previous .goreleaser.yml configuration. The new workflow automates the entire release process, from building cross-platform binaries and generating changelogs to creating official GitHub Releases with associated assets and instructions, streamlining the delivery of new versions.

Highlights

• Release Workflow: Implemented a new GitHub Actions workflow for automated releases, triggered by v* tags.
• Binary Builds: Configured the workflow to build cross-platform binaries for Linux, macOS, and Windows across amd64 and arm64 architectures.
• Changelog Generation: Integrated automatic changelog generation from git history between release tags.
• GitHub Releases: Enabled the creation of GitHub Releases, including installation instructions and checksums for built artifacts.
• Configuration Removal: Removed the .goreleaser.yml file, as its functionality is now self-contained within the new GitHub Actions workflow.

Changelog

• .goreleaser.yml
  • Removed the GoReleaser configuration file, as its functionality has been migrated to a GitHub Actions workflow.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/release.yml

Activity

• The author has outlined a test plan to ensure the new CI pipeline functions correctly, including verifying CI passes on this PR and creating a test tag to validate the release workflow.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request replaces the GoReleaser configuration with a new GitHub Actions workflow for releases. The change involves removing the .goreleaser.yml file. This is a logical step for the migration. My review focuses on ensuring that critical functionality from the previous release process is not lost. I have added a comment regarding the version injection, which is essential for the version command to work correctly in released binaries. Assuming all functionality from the GoReleaser configuration is successfully migrated to the new workflow, this change is an improvement.