Semantic Version

Maintain a single JSON file on disk that records product version and release entries. No database, no UI — the file is the source of truth for About screens, changelogs, or tooling to consume later.

Faruk Base — when to bump

In Faruk Base (this template repo):

• Do not update docs/release-history.json while editing docs, specs, plans, or code.
• Only bump version when the user invokes /commit-push (or explicitly asks to record a release without that command).
• Pair with caveman-commit in the same /commit-push run.

Canonical file

Path: docs/release-history.json

Create docs/ if missing. Never split history across multiple files.

If the project already has docs/release-history.json, use it. Do not rename or relocate without explicit user request.