⚙️ add automated release workflow

[Miyamura80]

Summary

• Added GitHub Actions workflow for automated releases triggered by version tags.
• The workflow runs CI checks, builds the package, and creates a GitHub Release with artifacts and auto-generated notes.
• Updated CLAUDE.md with instructions on how to trigger a release.

[greptile-apps]

Greptile Overview

Greptile Summary

Added automated GitHub Actions release workflow triggered by version tags (v*). The workflow runs CI checks and tests before building and publishing the package with auto-generated release notes.

Key changes:

• Workflow reads Python version from .python-version and uses actions/setup-python@v6 (consistent with existing workflows)
• Uses astral-sh/setup-uv@v5 action for secure uv installation (addresses previous security concern about piping remote scripts)
• Runs make ci and make test to validate code quality before release
• Uses uv build to create distribution artifacts
• Creates GitHub Release with artifacts using softprops/action-gh-release@v2
• Documentation updated with clear 3-step release process instructions

Confidence Score: 5/5

• This PR is safe to merge with no concerns
• The workflow follows GitHub Actions best practices, addresses all previously identified security concerns, uses consistent patterns with existing workflows, and includes proper CI validation before release
• No files require special attention

Important Files Changed

Filename	Overview
.github/workflows/release.yml	Automated release workflow with CI checks, build, and GitHub release creation - previous security concerns have been addressed
CLAUDE.md	Added clear release instructions explaining version tagging workflow

[greptile-apps]

_{2 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}