Web Tools DocGuides

How to use Changelog Generator

Get the best out of Changelog Generator: every option explained, a worked example, and what to check when the output is not what you expected.

Updated July 31, 2026

What it does

Generate release-ready changelog sections with Added, Changed, and Fixed blocks. It runs entirely in your browser — your input never leaves your device.

Options

Every setting this tool exposes, straight from the code that validates it.

OptionTypeDefaultWhat it does
projectNametext
versiontextRelease version, e.g. 2.6.0. Required.
datetextRelease date. Required.
summarytext
addedtextAdded items, one per line.
changedtext
fixedtext

Worked example

Run these settings on the tool page:

  • version: example
  • date: example

You get:

# Changelog

## [example] - example

Getting the result you want

Most of the control here is in the options above. If the output is not what you expected, the setting to check first is projectName and summary — those change the shape of the output rather than the input it accepts.

Troubleshooting

  • Nothing happens / the output stays empty. version, date are required — the tool waits until you provide them.
  • It is slow on very large input. Everything runs in your browser, so speed depends on your device. Very large inputs are best split up, or run through the API where the work happens on our servers.

Automating it

The same logic is available as a REST endpoint, so you can run it from a script, a CI job or your own app.

Bash
curl "https://api.toolsxpo.com/v1/changelog-generator" \
  -H "Authorization: Bearer $TOOLSXPO_KEY"

It costs 1 credit per successful call. See the full endpoint reference, or try it in the playground.

Tools covered here

Changelog Generator

Writing

writing

Related