Releasing a new version

Last updated:

|Edit this page

We have sunsetted support for our kubernetes and helm chart managed self-hosted offering. This means we no longer offer support for fixing to specific versions of PostHog. A docker image is pushed for each commit to master. Each of those versions is immediately deployed to PostHog cloud.

The deploy-hobby script allows you to set a POSTHOG_APP_TAG environment variable and fix your docker-compose deployed version of PostHog. Or you can edit your docker-compose file to replace each instance of image: posthog/posthog:$POSTHOG_APP_TAG with a specific tag e.g. image: posthog/posthog:9c68581779c78489cfe737cfa965b73f7fc5503c

Changes to PostHog are listed in our changelog, and in GitHub.


Was this page useful?

Next article

Handling an incident

Incidents are going to happen. When to raise an incident When in doubt, raise an incident. We'd much rather have declared an incident which turned out not to be an incident. Many incidents take too long to get called, or are missed completely because someone didn't ring the alarm when they had a suspicion something was wrong. To declare an incident, type /incident anywhere in Slack. This will create a new channel and send updates. Anyone can declare an incident, including non-engineers. If in…

Read next article