fix(release): configure git credentials for homebrew tap push

[mateodelnorte]

Summary

• Adds gh auth setup-git before cloning the homebrew-tap repo in the release workflow
• This configures git's credential helper to use GH_TOKEN, fixing the fatal: could not read Username error on git push
• Root cause: gh repo clone sets up auth for gh CLI but not for raw git commands

Context

The v0.2.13 release completed successfully (builds, GitHub release, crates.io publish) but the homebrew formula update failed: https://github.com/harmony-labs/meta/actions/runs/22258320387

Test plan

• Merge and re-run the release workflow (or trigger a new release) to verify the homebrew tap update succeeds

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Improved release automation infrastructure to ensure more reliable deployment processes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

Walkthrough

Added GitHub CLI authentication via gh auth setup-git step in the Update Homebrew Formula workflow branch, enabling subsequent git operations (clone, commit, push, PR creation) on the homebrew-tap repository to proceed with proper authentication credentials.

Changes

Cohort / File(s)	Summary
Workflow Authentication .github/workflows/release.yml	Added gh auth setup-git step to authenticate GitHub CLI before performing git operations on the homebrew-tap repository.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix: use PR workflow for homebrew tap updates #29: Modifies the same .github/workflows/release.yml file to transition Homebrew tap updates to an authenticated GitHub CLI-based process with PR operations.

Poem

🐰 A token whisper, soft and bright,
GitHub CLI takes flight!
Auth setup first, then clone and push,
Homebrew taps with gentle shush! 🍺✨

🚥 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 describes the main change: adding git credential configuration for the homebrew tap push operation in the release workflow.
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
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/homebrew-tap-auth

---

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

[greptile-apps]

Greptile Summary

Fixes authentication error when pushing to homebrew-tap by adding gh auth setup-git before cloning. This configures git's credential helper to use the GH_TOKEN environment variable for subsequent raw git commands.

• Added single line gh auth setup-git at line 321 before gh repo clone
• Resolves fatal: could not read Username error that occurred during git push in v0.2.13 release
• The gh repo clone command sets up auth for the GitHub CLI but not for raw git operations, requiring explicit credential configuration

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• Single-line fix that directly addresses a documented authentication failure with the standard GitHub CLI solution. The change is minimal, well-tested by GitHub's own tooling, and isolated to the specific failing workflow step
• No files require special attention

Important Files Changed

Filename	Overview
.github/workflows/release.yml	Added gh auth setup-git before cloning homebrew-tap to configure git credentials for push operations

_{Last reviewed commit: c24c5cb}