Changelog

All notable changes to this project will be documented in this file.

This changelog follows the structure of Keep a Changelog, and this project uses Semantic Versioning.

Release tags use the following format:

vMAJOR.MINOR.PATCH

For the full versioning policy, see: Libmemalloc's Versioning Guide.

Each released version must use the following changelog title pattern:

## [vMAJOR.MINOR.PATCH] - YYYY-MM-DD — libmemalloc <fantasy_release_name>

The version must always be linked to the corresponding Git tag at the end of this file:

[v0.2.0]: https://github.com/RafaelVVolkmer/libmemalloc/releases/tag/v0.2.0

The release date must use the ISO 8601 calendar date format:

YYYY-MM-DD

Example:

2026-05-05

Each release must also have a human-readable fantasy name. The release name should be creative, memorable, and related to the main purpose of the release, while keeping the Git tag itself strictly technical and SemVer-compatible.

Examples:

## [v0.1.0] - 2026-05-05 — libmemalloc First Spark

## [v0.2.0] - 2026-06-01 — libmemalloc Runtime Forge

## [v0.3.0] - 2026-07-10 — libmemalloc Arena Bloom

## [v0.4.0] - 2026-08-15 — libmemalloc Collector Awakening

## [v1.0.0] - 2026-12-01 — libmemalloc Stable Flame

See the example below:

Unreleased

Added

To be filled for the next release.

Changed

To be filled for the next release.

Deprecated

To be filled for the next release.

Removed

To be filled for the next release.

Fixed

To be filled for the next release.

Security

To be filled for the next release.

Documentation

To be filled for the next release.

Tooling

To be filled for the next release.

Migration Notes

No migration steps are required yet.