22.9.0

IMPORTANT CHANGES

We want to catch errors in self-hosted faster, so we introduced monitoring. In this update you will see a prompt which asks you if you would like to opt in or out. Please read the section of our README for more information and details about what we collect. For now, if you are running under automation, you are opted out by default.

However, in the next release (22.10.0) we will require everyone to select to opt in or out of monitoring of their self-hosted installation.

Various fixes & improvements

• Fix traceback hash for error monitoring (#1700) by @hubertdeng123
• Add section about error monitoring to the README (#1699) by @ethanhs
• Switch from .reporterrors file to flag + envvar (#1697) by @chadwhitacre
• Rename flag to --skip-user-creation (#1696) by @chadwhitacre
• Default to not sending data to Sentry for now (#1695) by @chadwhitacre
• fix(e2e tests): Pull branch that initially triggers gcp build for PRs (#1694) by @hubertdeng123
• fix(e2e tests): Add .reporterrors file for GCP run of e2e tests (#1691) by @hubertdeng123
• Error monitoring of the self-hosted installer (#1679) by @ethanhs
• added docker commands in the description (#1673) by @victorelec14
• Use docker-compose 2.7.0 instead of 2.2.3 in CI (#1591) by @aminvakil

22.8.0

• No documented changes.

Components

• sentry
• snuba
• relay

22.7.0

Various fixes & improvements

• ref: use sort -V to check minimum versions (#1553) by @ethanhs
• Get more data from users in issue templates (#1497) by @aminvakil
• Add ARM support (#1538) by @chadwhitacre
• do not use gosu for snuba-transactions-cleanup and snuba-cleanup (#1564) by @goganchic
• ref: Replace regex with --short flag to get compose version (#1551) by @ethanhs
• Improve installation through proxy (#1543) by @goganchic
• Cleanup .env{,.custom} handling (#1539) by @chadwhitacre
• Bump nginx:1.22.0-alpine (#1506) by @aminvakil
• Run release a new version job only on getsentry (#1529) by @aminvakil

22.6.0

Various fixes & improvements

• fix "services.web.healthcheck.retries must be a number" (#1482) by @yuval1986
• Add volume for nginx cache (#1511) by @glensc
• snuba: New subscriptions infrastucture rollout (#1507) by @lynnagara
• Ease modification of base image (#1479) by @spawnia

22.5.0

Various fixes & improvements

• ref: reset user to root for installation (#1469) by @asottile-sentry
• Document From email display name (#1446) by @chadwhitacre
• Bring in CLA Lite (#1439) by @chadwhitacre
• fix: replace git.io links with redirect targets (#1430) by @asottile-sentry

22.4.0

Heads up: CI is breaking under Docker Compose v1 and we can't figure out why, it doesn't seem to be anything we did. If you're still on Docker Compose v1 and you run into problems, please let us know. Thanks!

Various fixes & improvements

• Use better API key when available (#1408) by @chadwhitacre
• Use a custom action (#1407) by @chadwhitacre
• Add some debug logging (#1340) by @chadwhitacre
• meta(gha): Deploy workflow enforce-license-compliance.yml (#1388) by @chadwhitacre
• Turn off containers under old name as well (#1384) by @chadwhitacre

22.3.0

Gotcha

If you're upgrading from < 21.12.0 then be sure to stop your old containers with this command before installing:

COMPOSE_PROJECT_NAME=sentry_onpremise docker compose down --rmi local --remove-orphans

Without this you may run into errors about snuba-api being unhealthy. This is because of we finished renaming from onpremise to self-hosted in 21.12.0 including the project name. We put the above code under install.sh in #1384, but it didn't make it into 22.3.0, sorry. 😕 It will be in 22.4.0.

Various fixes & improvements

• Run CI every night (#1334) by @aminvakil
• Docker-Compose: Avoid setting hostname to '' (#1365) by @glensc
• meta(gha): Deploy workflow enforce-license-compliance.yml (#1375) by @chadwhitacre
• ci: Change stale GitHub workflow to run once a day (#1371) by @kamilogorek
• ci: Temporary fix for interactive prompt on createuser (#1370) by @BYK
• meta(gha): Deploy workflow enforce-license-compliance.yml (#1347) by @chadwhitacre
• Add SaaS nudge to README (#1327) by @chadwhitacre

22.2.0

Various fixes & improvements

• fix: unbound variable _group in reset/dc-detect-version script (#1283) (#1284) by @lovetodream
• Remove routing helper (#1323) by @chadwhitacre
• Bump nginx:1.21.6-alpine (#1319) by @aminvakil
• Add a cloudbuild.yaml for GCB (#1315) by @chadwhitacre
• Update set-up-and-migrate-database.sh (#1308) by @drmrbrewer
• Pull relay explicitly to avoid garbage in creds (#1301) by @chadwhitacre
• Improve logging of docker versions and relay creds (#1298) by @chadwhitacre
• Remove file again (#1299) by @chadwhitacre
• Clean up relay credentials generation (#1289) by @chadwhitacre
• Add CI compose version 1.29.2 / 2.0.1 / 2.2.3 (#1290) by @chadwhitacre
• Revert "Add CI compose version 1.29.2 / 2.0.1 / 2.2.3 (#1251)" (#1272) by @chadwhitacre
• Add CI compose version 1.29.2 / 2.0.1 / 2.2.3 (#1251) by @aminvakil

22.1.0

Postgres 10

If you are running on AWS RDS then you should be aware that they are forcing upgrades to Postgres 10 starting now-ish. Sentry support for Postgres 10 should be considered experimental.

Various fixes & improvements

• Make healthcheck variables configurable in .env (#1248) by @aminvakil
• Take some actions to avoid unhealthy containers (#1241) by @chadwhitacre
• Install: setup umask (#1222) by @glensc
• Deprecated /docker-entrypoint.sh call (#1218) by @marcinroman
• Bump nginx:1.21.5-alpine (#1230) by @aminvakil
• Fix reset.sh docker-compose call (#1215) by @aminvakil
• Set worker_processes to auto (#1207) by @aminvakil

Components

• Sentry
• Snuba
• Relay

21.12.0

Gotchas

• Make sure you docker compose down before running install.sh, to avoid this issue related to Docker volumes and the "self-hosted" rename (see below).

Support Docker Compose v2 (ongoing)

Self-hosted Sentry mostly works with Docker Compose v2 (in addition to v1 >= 1.28.0). There is one more bug we are trying to squash.

By: @chadwhitacre (#1179)

Prevent Component Drift

When a user runs the install.sh script, they get the latest version of the Sentry, Snuba, Relay and Symbolicator projects. However there is no guarantee they have pulled the latest self-hosted version first, and running an old one may cause problems. To mitigate this, we now perform a check during installation that the user is on the latest commit if they are on the master branch. You can disable this check with --skip-commit-check.

By: @chadwhitacre (#1191), @aminvakil (#1186)

React to log4shell

Self-hosted Sentry is not vulnerable to the log4shell vulnerability.

By: @chadwhitacre (#1203)

Forum → Issues

In the interest of reducing sources of truth, providing better support, and restarting the fire of the self-hosted Sentry community, we deprecated the Discourse forum in favor of GitHub Issues.

By: @chadwhitacre (#1167, #1160, #1159)

Rename onpremise to self-hosted (ongoing)

In the beginning we used the term "on-premise" and over time we introduced the term "self-hosted." In an effort to regain some consistency for both branding and developer mental overhead purposes, we are standardizing on the term "self-hosted." This release includes a fair portion of the work towards this across multiple repos, hopefully a future release will include the remainder. Some orphaned containers / volumes / networks are expected. You may clean them up with docker-compose down --remove-orphans.

By: @chadwhitacre (#1169)

Add support for custom DotEnv file

There are several ways to configure self-hosted Sentry and one of them is the .env file. In this release we add support for a .env.custom file that is git-ignored to make it easier for you to override keys configured this way with custom values. Thanks to @Sebi94nbg for the contribution!

By: @Sebi94nbg (#1113)

Various fixes & improvements

• Revert "Rename onpremise to self-hosted" (5495fe2) by @chadwhitacre
• Rename onpremise to self-hosted (9ad05d8) by @chadwhitacre