Versioning process

Understand how versioning works in Lerian, what to expect between releases, how semantic versioning is automated, and how to plan upgrades with clear guidance for every major version.

Versioning is not just a naming convention; it’s an automated process that ensures consistency across releases. This section explains how automation drives version generation, how support timelines are defined, and what to expect when moving between versions.

Versioning automation

---

To ensure an automated and predictable versioning process, we follow semantic versioning principles.

How it works

---

1. Identifies commits made since the last version.

2. Determines the new version based on predefined rules.

3. Automatically generates and publishes the new version.

Version support timeline

---

Midaz follows a clear support policy that defines what you can expect from each version throughout its lifecycle.

• Active support (current major version): includes feature enhancements, bug fixes, and security patches.
• Security support (post-active support): limited to critical security patches only.

Older versions do not receive further updates or support.

Upgrade path recommendations”

---

Upgrading Midaz versions follows clear recommendations to keep the process predictable and safe.

• Minor version upgrades (1.0.0 → 1.1.0) are simple and require little effort.
• Major version upgrades (1.2.0 → 2.0.0) may involve planning and testing.
• Every major version comes with a clear upgrade guide to support the transition.