fix: improve goreleaser tag selection and changelog grouping

[jingxiang-z]

Summary

• pin GoReleaser to the triggering tag in the release workflow
• simplify changelog grouping regexes so conventional commit types match rendered changelog entries with SHA prefixes

Notes

• targets main
• helps prevent RC releases from being overwritten when multiple tags point at the same commit

Summary by CodeRabbit

• Chores
  • Improved release automation configuration to better categorize and organize changelog entries in future releases.

[coderabbitai]

📝 Walkthrough

Walkthrough

Two configuration files updated to enhance the release process: an environment variable added to the GitHub Actions release workflow to pass the current Git tag reference to GoReleaser, and changelog grouping regex patterns in GoReleaser configuration made more permissive to better match conventional commit keywords.

Changes

Cohort / File(s)	Summary
GitHub Actions Release Workflow .github/workflows/release.yml	Added GORELEASER_CURRENT_TAG environment variable set to ${{ github.ref_name }} in the GoReleaser execution step.
GoReleaser Configuration .goreleaser.yaml	Updated changelog group regex patterns for New Features, Bug Fixes, Performance Improvements, Documentation Updates, and Refactors to match keywords anywhere in text with word boundaries, optional scope parentheses, and optional breaking-change (!) indicator.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 With tags now captured and patterns so keen,
Our releases flow through the CI machine,
Conventional commits in perfect array,
GoReleaser groups them the new-fangled way,
Automation hops forward, hooray! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main changes: pinning GoReleaser to the triggering tag and improving changelog grouping regex patterns for conventional commits.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/goreleaser-tag-and-changelog

---

_{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 @.goreleaser.yaml:
- Around line 190-202: The changelog grouping regexes are too permissive (they
use '.*\b...') and can match tokens anywhere in the commit/title; update each
regexp entry (the ones currently set to '.*\bfeat(?:\([^)]+\))?!?:',
'.*\bfix(?:\([^)]+\))?!?:', '.*\bperf(?:\([^)]+\))?!?:',
'.*\bdocs(?:\([^)]+\))?!?:', '.*\brefactor(?:\([^)]+\))?!?:') to anchor to the
start of the string and only allow the conventional prefix format (e.g. begin
with ^ and then feat|fix|perf|docs|refactor with optional scope and optional
breaking mark before the colon) so these tokens are matched only when they are
the actual commit-type prefix.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: daadecd6-85de-4f83-9939-f9992c8ceabc

📥 Commits

Reviewing files that changed from the base of the PR and between 7c5fc96 and 1aaef29.

📒 Files selected for processing (2)

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