# Release

> Release a stable verifiers version from main to PyPI and GitHub.

- Skill: `primeintellect-ai/release` (Agent Skill)
- Install (CLI): `npx skillmds@latest add primeintellect-ai/release`
- Raw SKILL.md: https://api.skillmd.com/api/skills/primeintellect-ai/release/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: primeintellect-ai (https://skillmd.com/u/primeintellect-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/primeintellect-ai/release

---


# Release Verifiers

Use the next minor version by default. Use a different `vX.Y.Z` version when the
user specifies one. Complete only the release steps that the user authorizes.

## 1. Prepare main

Run the release from the main repository:

```bash
git switch main
git pull --ff-only origin main
git status --short --branch
VERSION=vX.Y.Z
```

Require a clean worktree. Confirm that `$VERSION` is absent from GitHub and
PyPI. Review `pyproject.toml` and require published stable dependency versions.
For example, replace any `.dev`, alpha, beta, or release-candidate version and
update `uv.lock`. Land dependency changes through the normal PR process. Pull
`main` again and require a clean worktree before tagging.

## 2. Tag latest main

```bash
git tag "$VERSION"
git push origin "refs/tags/$VERSION"
```

Confirm that the remote tag points to the current `main` commit.

## 3. Publish

Manually dispatch the stable release workflow:

```bash
gh workflow run publish-verifiers.yml \
  --repo PrimeIntellect-ai/verifiers \
  --ref main \
  -f tag="$VERSION"
```

Monitor the new run through completion with `gh run watch <run-id>
--exit-status`.

## 4. Update the release notes

After the workflow creates the public GitHub Release, read the previous stable
release and use the same release-note format. Describe the changes since that
release, then update the new release:

```bash
gh release edit "$VERSION" \
  --repo PrimeIntellect-ai/verifiers \
  --notes-file <release-notes.md>
```

## 5. Verify

Confirm that:

- PyPI lists `${VERSION#v}` with a wheel and source archive.
- The GitHub Release is public with both files attached.
- The release notes match the prior release format.