← ClaudeAtlas

releaselisted

Cut a ccdrift release. Bumps __version__ to match the tag, verifies, tags and pushes, then drafts the GitHub Release notes. Takes the target version as an argument, for example /release 0.11.0.
rkolesnichenko/ccdrift · ★ 0 · DevOps & Infrastructure · score 73
Install: claude install-skill rkolesnichenko/ccdrift
Target version: $ARGUMENTS Publishing is tag-triggered Trusted Publishing over OIDC. The tag is the trigger and it cannot be taken back cleanly, so every check happens before the push. ## 1. Preflight Confirm and report each: ``` git status --porcelain git rev-parse --abbrev-ref HEAD git remote -v git tag --list 'v*' | tail -5 git diff --stat v<previous>..HEAD -- src tests lab docs/findings.md README.md LICENSE pyproject.toml ``` - Working tree clean, on `main`. - `origin` must point at `https://github.com/rkolesnichenko/ccdrift.git`. If `git remote -v` is empty or names anything else, stop and ask before going further. - The target tag must not already exist. - Something must actually ship. That last command's paths are a copy of `only-include` in pyproject.toml, which is the whole of the sdist, so they are the only diff a release can carry; change one and change the other. An empty result means the distributions would differ from the last one by the version string alone: stop, say so, and let me decide, since a PyPI version can never be reused. Work on `.claude/`, `.github/` and CLAUDE.md never reaches the package and is finished once it is on `main`. If no version was given in the argument, ask for it. Do not infer one. ## 2. Bump the version Set `__version__` in src/ccdrift/__init__.py to the target, with no leading `v`. The workflow installs the wheel and the sdist in isolation and fails unless each reports `ccdrift <tag>` exactly, so a mismatch burns the tag. #