← ClaudeAtlas

drift-releaselisted

Complete release workflow: Validate → Version → Changelog → Commit → Tag → Publish. Use after successful code changes to src/drift/. Single command: `python scripts/release_automation.py --full-release`
mick-gsk/drift · ★ 14 · Code & Development · score 68
Install: claude install-skill mick-gsk/drift
# Drift Release Skill (python-semantic-release) Releases are **fully automated** via `python-semantic-release` (PSR) in CI. ## Executive Summary **Agents no longer need to run a manual release command.** Workflow: `.github/workflows/release.yml` runs on every push to `main`. PSR parses conventional commits and handles version bump, changelog, tag, GitHub Release, and PyPI publish. --- ## When to Use This Skill ✅ **Know this after:** - Feature complete (`feat: ...` commit) - Bug fixed (`fix: ...` commit) - Breaking change (`BREAKING: ...` commit) - All tests pass - Code committed + pushed to main The CI release workflow handles everything else automatically. --- ## What Agents Must Do ### Step 1: Use Conventional Commits ``` feat: add new detector for X → MINOR bump (0.X.0) fix: false alarm in signal Y → PATCH bump (0.0.X) BREAKING: remove deprecated API → MAJOR bump (X.0.0) ``` ### Step 2: Run Tests Locally ```bash make test-fast ``` ### Step 3: Commit and Push PSR in CI handles the rest after push to main. --- ## What PSR Does Automatically (in CI) 1. **Commits analyzed** — from last tag to HEAD 2. **Version calculated** — based on commit types (feat → minor, fix → patch, BREAKING → major) 3. **Files updated:** - `pyproject.toml` (version field) - `CHANGELOG.md` (new entry) 4. **Release commit created** — `chore: Release X.Y.Z` 5. **Git tag created** — `vX.Y.Z` 6. **GitHub Release created** 7. **Built and published to PyPI** --- #