# Release

> Increment the package version, commit the release, create a matching version tag, and push main plus the tag. Use when releasing this repo, publishing the package, bumping the version, tagging a release, or when the user asks to "release", "bump ver", "tag", or "push tags".

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

---


# Release

Use this workflow to publish a new `@duetso/agent` version through the GitHub release workflow.

## Steps

1. Confirm the working tree and branch:
   - Run `git status --short --branch`.
   - If there are unrelated changes, ask before including them.
   - Release from `main` unless the user explicitly says otherwise.

2. Choose the next version:
   - Read `package.json`.
   - Increment the patch version by default.
   - Use the tag name `v<version>`, for example `v0.1.12`.
   - Check that the tag does not already exist locally or remotely.

3. Update release metadata:
   - Change only `package.json` for a normal version bump.
   - Do not edit `bun.lock` unless the package manager updates it as part of a dependency change.

4. Verify before committing:
   - Run `bun run check-types`.
   - Run `bun run lint`.
   - Run broader tests only when the release includes code changes or the user asks for them.

5. Commit:
   - Stage `package.json`.
   - Commit with `chore: release v<version>`.

6. Tag and push:
   - Create an annotated tag: `git tag -a v<version> -m "v<version>"`.
   - Push `main`: `git push origin main`.
   - Push the tag: `git push origin v<version>`.

7. Report back:
   - Include the new version, commit SHA, tag name, pushed refs, and verification commands.