Self-Hosted Releases & Upgrading

Sentry cuts regular releases for self-hosting to keep it as close to sentry.io as possible. We decided to follow a monthly release schedule using the CalVer versioning scheme, with a primary release on the 15th of each month. We don't patch old versions, but if a bug is bad enough we may cut an out-of-cycle point release, which, like our regular monthly releases, is a snapshot of the latest versions of all of our components. You can find the latest release over at the releases section of our self-hosted repository.

Upgrading

We encourage everyone to regularly update their Sentry installations to get the best and the most recent Sentry experience.

To upgrade, all you need to do is download or check out the version of self-hosted repository you want, replace your existing folder's contents with that, and then run ./install.sh.

Before starting the upgrade, we shut down all the services and then run some data migrations, so expect to have some downtime. There is an experimental --minimize-downtime option to reduce the downtime during upgrades. Use this at your own risk and see the pull request it was implemented in for more information.

If you downloaded self-hosted repository using Git clone, the upgrade commands should look like this:

# Assuming your destination upgrade version is 24.3.0
VERSION="24.3.0"
git fetch
git checkout ${VERSION}
sudo ./install.sh

Hard Stops

We have three hards stops that you need to go through in order to pick up significant database changes:

1. If you are coming from a version prior to 9.1.2, you first need to upgrade to 9.1.2 and follow the next steps:
   Text

   Copied

   <your.sentry.version> -> 9.1.2 -> 21.5.0 -> 21.6.3 -> 23.6.2 -> latest

2. If you are coming from 9.1.2, you first need to upgrade to 21.5.0 and follow the next steps:
   Text

   Copied

   <your.sentry.version> -> 21.5.0 -> 21.6.3 -> 23.6.2 -> latest

3. If you are coming from a version prior to 21.6.3, you first need to upgrade to 21.6.3:
   Text

   Copied

   <your.sentry.version> -> 21.6.3 -> 23.6.2 -> latest

4. If you are coming from a version prior to 23.6.2, you first need to upgrade to 23.6.2:
   Text

   Copied

    <your.sentry.version> -> 23.6.2 -> latest

Any other case (23.6.2+), you should be able to upgrade to the latest version directly. We'd recommend you skip 23.7.0 to avoid issues around database migrations and the django 3 upgrade.

Nightly Builds

We provide nightly builds from the master branch of the self-hosted repository for each new commit for Sentry, and all of the supporting projects:

• Snuba
• Relay
• Symbolicator
• Vroom

These builds are usually stable, but you may occasionally hit a broken version as these versions are not guaranteed to be deployed to sentry.io first. There is also no guarantee that you will be able to do a clean upgrade to later versions without losing any data. Use the nightly builds at your own risk.

Breaking Changes

• The 23.11.0 release will remove the sentry run smtp worker process. This worker was not part of the standard self-hosted configuration, but could be used in custom deployments.

• The 24.1.2 release will change the memcached backend from django.core.cache.backends.memcached.MemcachedCache to django.core.cache.backends.memcached.PyMemcacheCache. This will require changing the CACHES setting in your sentry.conf.py file in a manner similar to what is seen here. In particular, the OPTIONS API for PyMemcacheCache is different from that of MemcachedCache, and may require changes depending on how it has been configured.