prepare-release

Prepare release

Prepare a kprun release locally. No LLM calls in CI — all changelog writing happens here in the IDE.

Invocation

User runs /prepare-release X.Y.Z where X.Y.Z is semver without the v prefix (e.g. 0.2.0).

Mandatory checklist (follow in order)

1. Resolve commit range

git fetch --tags
PREV=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
if [ -z "$PREV" ]; then
  RANGE="first commit..HEAD"
else
  RANGE="${PREV}..HEAD"
fi
git log $RANGE --oneline
git log $RANGE --format="%s"

If range is empty (no commits since last tag), stop and ask the user to confirm before writing an empty changelog.

2. Classify commits

Group git log subjects by Conventional Commits type:

Type	Keep a Changelog section
feat	Added
fix	Fixed
perf	Changed
refactor	Changed
docs	Changed (or omit if internal-only)
ci, build, chore	omit unless user-facing
feat!, fix!, footer BREAKING CHANGE:	Changed + breaking note

Write user-facing bullets in English. No raw SHAs in bullet text. Optional <details> footer with full commit list.

3. Write per-version file

Create docs/changelogs/vX.Y.Z.md:

• Format: Keep a Changelog 1.1.0
• Title/header includes version and date (UTC: YYYY-MM-DD from date -u +%Y-%m-%d)
• Sections (omit empty): Added, Changed, Deprecated, Removed, Fixed, Security
• Reference prior file docs/changelogs/v0.1.0.md for tone and structure

4. Update root CHANGELOG.md

Prepend a new section at the top (after the intro paragraphs):

## [X.Y.Z] - YYYY-MM-DD

See [docs/changelogs/vX.Y.Z.md](docs/changelogs/vX.Y.Z.md) for details.

### Added
- (short summary bullets)

Keep root entries as summaries; full detail stays in per-version file.

5. Version bump

Update all three locations to X.Y.Z:

1. [workspace.package].version in root Cargo.toml
2. crates/kprun/Cargo.toml — uses version.workspace = true (verify, do not duplicate)
3. crates/kprun-core/Cargo.toml — uses version.workspace = true (verify)