Upgrade your self-hosted SigNoz instance to get the latest features, improvements, and security fixes.
Upgrade guides are organized by version. A version gets its own guide when that release needs migration steps or contains breaking changes.
How to Upgrade
- Find your upgrade path with the Upgrade Path Tool. It lists every version you must stop at between your current version and your target version.
- Read the upgrade guide for each required stop. Each guide covers the migration steps and the breaking changes for that version.
- Upgrade to one required stop at a time. Pin the target version in the upgrade command instead of taking the latest release. The Standard Upgrade Guide covers Kubernetes, Docker, Docker Swarm, and Linux binary installations.
- Wait until all migrations are complete. Then repeat step 3 for the next stop.
Upgrade commands for Kubernetes, Docker, Docker Swarm, and Linux binary installations
Generate the exact sequence of versions to upgrade through, including all required stops
Required Upgrade Stops
Some releases are required upgrade stops. These releases contain critical schema migrations or breaking changes that later versions depend on.
If you skip a required stop, the upgrade can fail or leave your instance in an inconsistent state.
For example, to upgrade from v0.8.2 to v0.10.0, upgrade to v0.9 first. Wait until that upgrade completes. Then upgrade to v0.10.
Release Cycle
SigNoz follows a regular schedule for new releases, with additional bug fixes and security patches when necessary.
| Release Type | Frequency | Example Versions | Notes |
|---|---|---|---|
| Minor Release | Every Wednesday | v0.87.0, v0.88.0 | Includes new features, improvements, and breaking changes |
| Bug Fix / Patch | As needed (not scheduled) | v0.87.1, v0.87.2 | Released after minor releases for urgent fixes or security patches |
For the complete list of releases, see the SigNoz releases page or the changelog.
