Skip to main content
This page covers how we communicate changes, how we manage dependencies, and our long-term commitment to backward compatibility.

​
Communication of changes

We communicate every change so teams can prepare.
  • 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.
  • We share pre-release announcements in advance for major versions.

​
Versioning of dependencies

We version dependencies with the same principles to ensure stability and compatibility.
  • Internal dependencies follow the same versioning scheme as Midaz.
  • We manage external dependencies to stay compatible throughout a major version lifecycle.

​
Backward compatibility commitment

This versioning policy applies to every new release. We commit to maintaining the defined support windows for all future versions. By preserving backward compatibility, we reduce the risk of breaking changes and let you plan upgrades on your own schedule.
For details about timelines and schedules, see the Release cycle page.