ci(release): add goreleaser config and GitHub Actions workflow

[MarsKubeX]

Enable automated cross-platform binary releases triggered by version tags, so consumers can download pre-built
binaries instead of building from source.

• Add .goreleaser.yaml to cross-compile kortex-cli for 6 targets: linux/darwin/windows x amd64/arm64
• Add .github/workflows/release.yml triggered on v* tags to automate GitHub Releases with goreleaser
• Version is injected at build time via ldflags into pkg/version.Version
• Archives are .tar.gz for linux/macOS and .zip for Windows, with SHA-256 checksums

Closes #21

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2768986a-010d-4e1c-a8fc-5cc688621af5

📥 Commits

Reviewing files that changed from the base of the PR and between f5ddef2 and cc5ee70.

📒 Files selected for processing (2)

• .github/workflows/release.yml
• .goreleaser.yaml

✅ Files skipped from review due to trivial changes (2)

• .goreleaser.yaml
• .github/workflows/release.yml

---

📝 Walkthrough

Walkthrough

Adds automated release infrastructure: a tag-triggered GitHub Actions workflow (.github/workflows/release.yml) and a GoReleaser configuration (.goreleaser.yaml) to build, archive, and publish kortex-cli binaries for multiple OS/architectures.

Changes

Cohort / File(s)	Summary
Release workflow ./.github/workflows/release.yml	New GitHub Actions workflow triggered on tag pushes matching v*; checks out full repo history, sets repository permissions, installs Go using go.mod, and runs GoReleaser action (goreleaser/goreleaser-action ~> v2.14) with release --clean using secrets.GITHUB_TOKEN.
GoReleaser config ./.goreleaser.yaml	New GoReleaser configuration: runs go mod tidy, builds kortex-cli from ./cmd/kortex-cli for linux/darwin/windows on amd64/arm64 with CGO_ENABLED=0, injects version via ldflags, strips symbols, archives as tar.gz (overrides to zip for Windows), sorts/filters changelog, and publishes GitHub releases under kortex-hub/kortex-cli.

Sequence Diagram(s)

sequenceDiagram
  participant Dev as Developer
  participant GH as GitHub (repo)
  participant Runner as Actions Runner
  participant GRA as GoReleaser Action
  participant GHRel as GitHub Releases

  Dev->>GH: push tag (v*)
  GH->>Runner: trigger `release` workflow
  Runner->>Runner: checkout (fetch-depth:0), setup Go
  Runner->>GRA: run goreleaser action (release --clean)
  GRA->>GHRel: create artifacts and publish release (uses GITHUB_TOKEN)
  GHRel-->>Dev: release published

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main changes: adding goreleaser configuration and GitHub Actions workflow for automated releases.
Description check	✅ Passed	The description is directly related to the changeset, explaining the purpose of adding goreleaser config and GitHub Actions workflow for cross-platform binary releases.
Linked Issues check	✅ Passed	The PR fully implements the requirements from issue #21: adopts goreleaser to build binaries for multiple platforms (linux/darwin/windows x amd64/arm64) and provides pre-built cross-platform binaries.
Out of Scope Changes check	✅ Passed	All changes are directly scoped to implementing goreleaser configuration and GitHub Actions workflow for automated releases; no out-of-scope modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/release.yml:
- Around line 46-47: Replace the non-deterministic "version: latest" entry in
the release workflow with a pinned GoReleaser Action version to ensure
reproducible releases; update the workflow step that currently sets "version"
alongside "args: release --clean" to a specific tag (e.g., a concrete vX.Y.Z) or
a stable range like "~> v2" per the goreleaser/goreleaser-action docs so the
action no longer floats to the latest release.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ce2810a0-bcdd-46fb-bf59-0faeb1d471ad

📥 Commits

Reviewing files that changed from the base of the PR and between 262dd0d and 09724d7.

📒 Files selected for processing (2)

• .github/workflows/release.yml
• .goreleaser.yaml

[benoitf]

question: do we need checksums ?

to me it was like old school way of providing checksums but for example on GitHub since last year checksum are provided by default by GitHub release

[MarsKubeX]

I removed it. You're right, GitHub natively provides SHA-256 digests for release assets.

[feloy]

In other project I have these lines in .goreleaser.yaml:

before:
  hooks:
    # You may remove this if you don't use go modules.
    - go mod tidy

This project is using modules, I suppose they are useful (this will check that the modules dependencies are up to date)

[benoitf]

question: why do we need a depth of 0 ?

[MarsKubeX]

Is needed since goreleaser needs the full git history to work properly. https://goreleaser.com/customization/ci/actions/

[benoitf]

not for this PR

but is that goreleaser is offering a way to build release after each commits ?

we often publish our builds after each commit so it's easy to try