Skip to main content
Clear governance keeps the versioning process transparent and reliable. Here we detail how changes are communicated, how dependencies are managed, and our long-term commitment to backward compatibility. This gives you full visibility into how Midaz evolves and how we protect your stability along the way.

​
Communication of changes

We communicate every change clearly so teams can prepare and adapt with confidence.
  • Release notes include new features, improvements, bug fixes, known issues, and breaking changes with migration paths.
  • Documentation updates reflect API changes, new configurations, and updated behaviors.
  • Pre-release announcements are shared in advance for major versions.

​
Versioning of dependencies

Dependencies are versioned with the same principles to ensure stability and compatibility.
  • Internal dependencies follow the same versioning scheme as Midaz.
  • External dependencies are managed to stay compatible throughout a major version lifecycle.

​
Backward compatibility commitment

This versioning policy applies to every new release, ensuring stability across the platform. We commit to maintaining the defined support windows for all future versions, so teams can adopt upgrades with confidence and without unexpected disruptions. By preserving backward compatibility, we reduce the risk of breaking changes and give organizations the flexibility to plan upgrades on their own schedule. This approach keeps integrations stable while allowing Midaz to evolve at a sustainable pace.
For details about timelines and schedules, see the Release cycle page.