Choose the next version number for a release

Prompt that sorts changes since the last release, proposes the next version number and drafts upgrade notes. Paste it into an AI tool of your choice, which then proposes the version number.

Topic: Apps & prototypes
Type: Prompt
Level: Intermediate
Time: about 10 min

Results depend on the tool, the model and what you enter.

Result preview

Example: written by our editors, not real AI output.

Fill in

What you type stays in this browser window. We store and send nothing.

ProjectWhat kind of project is it?

ChangesWhich changes are included?

UsersWho uses it?

Your prompt

Help me choose the next version number for a release.
Project: [Project]
Changes: [Changes]
Users: [Users]
Approach: 1. Sort every change into breaking change, new feature, fix or internal. 2. For each possible breaking change, explain what a user's existing code or setup would have to change. 3. Propose the next version number following semantic versioning and name the change that decides it. 4. Flag changes that look small but break users, such as a changed default, a renamed option or a stricter validation. 5. Write a short upgrade note for every breaking change with before and after. 6. List open questions for the maintainers.
Output: table of changes with category and reason, the proposed version number, upgrade notes and open questions.

Take particular care to decide by the most serious change and explain every breaking change with before and after.

Before you answer, check: Are all instructions met? If key information is missing or a placeholder in square brackets is still in the text, ask instead of guessing. Mark assumptions as assumptions.

Help me choose the next version number for a release.
Project: [Project]
Changes: [Changes]
Users: [Users]
Approach: 1. Sort every change into breaking change, new feature, fix or internal. 2. For each possible breaking change, explain what a user's existing code or setup would have to change. 3. Propose the next version number following semantic versioning and name the change that decides it. 4. Flag changes that look small but break users, such as a changed default, a renamed option or a stricter validation. 5. Write a short upgrade note for every breaking change with before and after. 6. List open questions for the maintainers.
Output: table of changes with category and reason, the proposed version number, upgrade notes and open questions.

Take particular care to decide by the most serious change and explain every breaking change with before and after.

Before you answer, check: Are all instructions met? If key information is missing or a placeholder in square brackets is still in the text, ask instead of guessing. Mark assumptions as assumptions.

This is an instruction for an AI, not the result itself.

Where this prompt works

These AI tools are a good fit for this prompt:

How to use it

Fill in the fields or tap a suggestion. Leave out names, addresses and other personal data.
Copy the finished prompt into an AI tool of your choice.
Paste the merged change titles or the commit list since the last tag; descriptions help more than code.

Why does this work?

Version numbers are a promise to users. Deciding by the most serious change, not the most visible one, prevents surprises after an update.

Tips

Check the result against your project's own versioning rules; some projects define stricter rules than semantic versioning.

You may use our prompts freely, including at work. Please do not republish them as your own collection. We give no warranty for AI results; check them yourself. Terms of use

Choose the next version number for a release

Result preview

Fill in

Your prompt

Where this prompt works

How to use it

Why does this work?

Tips

Also a good fit

Choose pagination for an API list New

Write an API reference people can use right away New

Plan a throttled data backfill New