This page describes the release process for Thanos project.
NOTE: As Semantic Versioning states all 0.y.z releases can contain breaking changes in API (flags, grpc API, any backward compatibility)
We aim for at least 1 release per 6 weeks. However, no strict dates are planned.
No release candidates are required until major version.
Additionally we aim for
master branch being stable.
Process of cutting a new minor Thanos release:
Add PR on branch
release-<major>.<minor> that will start minor release branch and prepare changes to cut release.
Bump VERSION file
Update CHANGELOG file
CHANGELOG.md should only document changes relevant to users of Prometheus, including external API changes, performance improvements, and new features. Do not document changes of internal interfaces, code refactorings and clean-ups, changes to the build process, etc. People interested in these are asked to refer to the git history.
Format is described in
Double check backward compatibility:
In case of version after
v1+.y.z, double check if none of the changes break API compatibility. This should be done in PR review process, but double check is good to have.
In case of
v0.y.z, document all incompatibilities in changelog.
After review, merge the PR and immediately after this create a
<ver> release on GitHub
release page. Describe release and post relevant entry from changelog. Click
Save Draft. This will trigger CircleCI that builds artifacts. Once tarballs are published on release page, you can click
Publish and release is complete. Announce
#thanos slack channel.
We use Semantic Versioning.
NOTE: We have a separate branch for each minor release, named
release-0.2. but they are
NOT maintained as we don’t have major version yet.
The following changes to the above procedures apply:
-rc.0to the version (with the corresponding changes to the tag name, the release name etc.).
This is a pre-releasebox when drafting the release in the Github UI.
CHANGELOG.md, but when you cut the final release later, merge all the changes from the pre-releases into the one final update.