changelog — how to use changelog how to use changelog, what is changelog, changelog alternative, changelog vs git, changelog install, changelog setup guide, automated version tracking, git commit analysis, markdown change log generation

Approach

1. Use git to look for the most recent tagged non-beta version.
2. If the most recent commit doesn't have a tag, use it as the current version.
3. Find the previous version.
4. Inspect the content of any larger commits.
5. Generate a change log for that based on the style of a few of these example change logs down below.
6. Return the results in a markdown code block.

Guidelines

• Don't include verbatim commit messages.
• Write copy for a general audience.
• Only include the "Features" and "Bug Fixes" sections.

Example 1

markdown
1## Features
2
3- **Chat mode** has landed! Switch between building apps and chatting with the agent.
4- **Projects page** with table view - delete, stop, and manage all your projects in one place.
5- Recent projects displayed on new tab.
6- Copy button for pre blocks in Markdown.
7- Use new projects page for eval viewing.
8- Incorporate upstream error messages for multiple matches.
9
10## Bug Fixes
11
12- Full width assistant messages always, and copy button for single line code too.
13- Support navigation API even on root pages like not found.
14- Remove redundant app type in tab title.
15- Remove more markdown in titles.
16- Attempt to avoid race condition during project deletion due to session abort.
17- Make command/ctrl + r work everywhere unless disabled.
18- Disallow creation of session db during entire deletion process.
19- Better handle ripgrep arguments.
20- Animated stop icon in proper places.
21
22## ⛵︎
23
24_72 commits since v1.5.0_
25
26More will follow.

Example 2

markdown
1## 🧬 Features
2
3- Evals have landed!
4- A couple clicks and you can compare rich output from as many models and apps you desire.
5- Built-in prompts for standard eval apps and some goofy ones too.
6- Suport fo custom eval prompts.
7- Dedicated runs page with bulk actions.
8
9## 🩹 Bug Fixes
10
11- Linux: Fixed DBus safe storage issues by setting up direct DBus communication.
12- Workspace: Ensured runtime starts when agent session spawns to prevent missing dependencies.
13- AI Gateway: Fixed handling of `:latest` style model names (e.g., `gpt-oss:latest`).
14- Workspace: Blocked `pnpm dev`, `pnpm start`, and `pnpm run` variants since Quests already manages app lifecycle.
15
16## Water Vehicle
17
18<!-- Image placeholder -->
19
20_23 commits since v1.4.2_