atmos follows the Semantic Versioning (SemVer) convention:
Incompatible changes increment the
major version, adding backwards-compatible functionality increments the
and backwards-compatible bug fixes increment the
A major release will be published when there is a breaking change introduced in
Several release candidates will be published prior to a major release in order to get feedback before the final release.
An outline of what is changing and why will be included with the release candidates.
A minor release will be published when a new feature is added or changes that are non-breaking are introduced. We will heavily test any changes so that we are confident with the release, but with new code comes the potential for new issues.
A patch release will be published when bug fixes were included, but no breaking changes were introduced. To ensure patch releases can fix existing code without introducing new issues from the new features, patch releases will always be published prior to a minor release.
To see a list of all notable changes to
atmos please refer to
It contains an ordered list of all bug fixes and new features under each release.