released .env file refers to nightly docker tags

[liayn]

Self-Hosted Version

26.2.0

CPU Architecture

...

Docker Version

...

Docker Compose Version

...

Machine Specification

• My system meets the minimum system requirements of Sentry

Installation Type

Upgrade from 26.1 to 26.2

Steps to Reproduce

read https://github.com/getsentry/self-hosted/blame/master/.env#L18

Expected Result

should probably use the docker tag 26.2.0?

Actual Result

:nightly is used

Event ID

No response

[aldy505]

Oh no... this shouldn't happen. Thanks for bringing this up!

[kzakhark]

Tried to upgrade to 26.2.0, got affected by this.

[aldy505]

We'll need to wait for US (San Francisco) to wake up, for the meantime, you can override the value to be 26.2.0. The Docker images are available.

[kzakhark]

We'll need to wait for US (San Francisco) to wake up, for the meantime, you can override the value to be 26.2.0. The Docker images are available.

I wonder if there's a way to go "back" to 26.2.0 release after an instance was upgraded to 26.3 nightly. Perhaps it's better to stick to 26.3 and wait for 26.3.0 release before going back to a proper release.