release-process - Claude MCP Skill

# Release Process

## Creating a New Release

1. **Update pyproject.toml version:**
   - Update the `version = "0.1.1"` field to match the new release

2. **Commit version changes:**
   ```bash
   git add pyproject.toml
   git commit -m "Bump version to 0.X.Y"
   ```

3. **Create and push the git tag:**
   ```bash
   git tag v0.X.Y
   git push origin v0.X.Y
   git push origin main
   ```

4. **GitHub Actions will automatically:**
   - Run tests
   - Generate `cicada/_version_hash.py` with the current tag and commit
   - Build the package
   - Publish to PyPI

5. **Test the installation:**
   ```bash
   uv tool install cicada-mcp
   cicada --version  # Should show version and commit hash
   ```

## Version Management

- Version number is stored in `pyproject.toml`
- Git tag and commit hash are stored in `cicada/_version_hash.py` (auto-generated, not committed)
- `cicada --version` or `cicada -v` displays version, tag, and commit hash
- Version format: `cicada 0.2.0 (v0.2.0-rc0/5ea1134)` - tag/hash format allows tracking RC releases
- **For PyPI installs:** Shows the version, tag, and hash from when the package was built by CI/CD
- **For local development:** The file is generated by `make pre-commit` and falls back to `git describe --tags` and `git rev-parse HEAD` if missing
- The file is in `.gitignore` to avoid merge conflicts while still being included in PyPI releases