---
title: Choose the next version number
description: Decide major, minor, or patch from what changed for users, not from the size of the diff.
url: https://openplanr.dev/docs/prompts/choose-next-version
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/prompts/write-release-notes.md
  - https://openplanr.dev/docs/prompts/prepare-landing-sequence.md
  - https://openplanr.dev/docs/prompts/ready-to-land.md
---

# Choose the next version number

Decide major, minor, or patch from what changed for users, not from the size of the diff.

## Prompt

Claude Code:

```text
/release Choose the next version for this CLI and explain whether it is a major, minor, or patch release.
```

If /release runs another command, use /planr:release.

Codex:

```text
$release Choose the next version for this CLI and explain whether it is a major, minor, or patch release.
```

With the OpenPlanr plugin for Codex, use $planr:release.

Cursor:

```text
@planr-release Choose the next version for this CLI and explain whether it is a major, minor, or patch release.
```

Cursor applies the planr-release rule when you mention it in chat.

Parts to fill in, shown with their example text:

- The product: this CLI

## Why this works

Release picks the bump from how each change affects users. A CLI or library that others install and pin follows SemVer strictly, and the chosen scheme goes into a release profile so later releases follow it instead of deciding again.

## Make it stick

[OpenPlanr Release](https://openplanr.dev/docs/skills/release.md)