ESProfiler Handbook
Platform Ops

Versioning

Our simplified approach to semantic versioning for application releases.

Our approach to semantic versioning is simpler than the traditional model. They are not tied to API versioning or API compatibility guarantees. We choose a version based on the type of release and our judgment of its significance.

Versions follow the format MAJOR.MINOR.PATCH, for example 7.1.2. Release tags include a v prefix, such as v7.1.2.

Patch releases

Use a patch bump only for hotfixes and dependency updates. For example, 7.1.2 becomes 7.1.3.

A hotfix is critical bug fix that requires us pushing it out to production as soon as possible.

Any other updates and new features belong in a minor release, even if the change is small.

Minor releases

Use a minor bump for most releases, including routine updates, improvements, and new features. This is our default for a regular product release.

Increment the minor number and reset the patch number to zero. For example, 7.1.2 becomes 7.2.0.

This is be will be used 99% of the time when updating the versioning.

Major releases

Major bumps follow a "vibes" approach we decide as a team when the changes in a release feel significant enough to warrant a new major version. There is no fixed feature count or API compatibility rule that triggers a major bump.

Increment the major number and reset the minor and patch numbers to zero. For example, 7.1.2 becomes 8.0.0.

Once the version is chosen, follow the release guide to publish and deploy it.

Copyright © 2026