Changelog

ORM++ follows Semantic Versioning and Conventional Commits. Every version tag vX.Y.Z triggers a CI job that generates a changelog from the commit messages since the last tag (git-cliff) and turns it into a GitLab release.

The current, complete history therefore doesn’t live as a static copy in these docs — it lives at the source, where it’s kept up to date automatically:

View releases on GitLab →

Versioning scheme

Prefix	Meaning
feat:	new feature — bumps the minor version
fix:	bug fix — bumps the patch version
refactor:, docs:, test:, ci:, chore:	no functional change to the public API

A break in the public API (see the API reference) bumps the major version and is marked BREAKING CHANGE in the commit. Before v1.0.0 the project wasn’t considered stable; since phase 5 (see Architecture) the entire v1 API is implemented and the test suite runs identically across all three backends.