Add release-please automation for releases

[gjtorikian]

Summary

• Replace manual tag-push release workflow with release-please
• On merge to main, release-please maintains a Release PR with version bump and changelog
• When that Release PR merges, GoReleaser builds binaries, creates the GitHub release, and pushes the updated formula directly to homebrew-tap

Changes

• release-please-config.json — Go release type, single package at root
• .release-please-manifest.json — pinned at current version 0.6.0
• .github/workflows/release.yaml — replaced tag-trigger with release-please + chained GoReleaser

Prerequisites

• The SDK bot GitHub App (SDK_BOT_APP_ID / SDK_BOT_PRIVATE_KEY) must be installed on this repo
• Commit messages on main should follow Conventional Commits (feat:, fix:, etc.)

Test plan

• Verify SDK bot app is installed on this repo
• Merge a conventional commit to main and confirm release-please opens a Release PR
• Merge the Release PR and confirm GoReleaser runs and updates the homebrew-tap

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes the release automation and required GitHub permissions/tokens; misconfiguration could block releases or publish incorrectly, but it’s isolated to CI workflow/config files.

Overview
Switches the release pipeline from tag-push triggered releases to release-please automation on merges to main, using a GitHub App token and explicit contents/pull-requests write permissions.

Adds release-please config/manifest to manage versioning (0.6.0) and gates the goreleaser job to run only when release-please actually creates a release, using BREW_REPO_GH_TOKEN for publishing.

^{Written by Cursor Bugbot for commit 77294e0. This will update automatically on new commits. Configure here.}