Skip to main content
Versioning follows 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 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

Follow these recommendations when you upgrade Midaz versions.
  • Minor version upgrades (1.0.0 → 1.1.0) require little effort.
  • Major version upgrades (1.2.0 → 2.0.0) may involve planning and testing.
  • Every major version comes with an upgrade guide.