Install: helm install glitchtip oci://registry.gitlab.com/glitchtip/glitchtip-helm-chart/glitchtip --version 9.2.0 -f your-values.yaml

• Add service.annotations for the web Service, e.g. to configure a cloud load balancer.
  
• The chart is now also published as an OCI artifact: oci://registry.gitlab.com/glitchtip/glitchtip-helm-chart/glitchtip. The README now uses it. The existing chart repository still receives every release, so nothing needs to change.
  
• GlitchTip 7.0.0. Read its release notes before upgrading.
  
• Fix helm diff showing a new random SECRET_KEY on every upgrade when the chart generates the key. A generated key is now written only when its Secret is created (on install, or on an upgrade that finds it missing) instead of on every upgrade, and its restart annotation is set only when an upgrade writes it. The stored key does not change, so nobody is logged out.
  
  • The first helm diff against this version shows <fullname>-secret-key as removed and the checksum/secret-key annotation dropped. Helm does not delete a hook resource it stops rendering, so the Secret and your key stay. Later diffs are clean. The upgrade restarts the web pods once.
    
  • The same one-time "removed" line appears in the first diff after a fresh install, since only the install writes the Secret. Pass --no-hooks to helm diff to leave it out.
    
  • Changing fullnameOverride or nameOverride now keeps the generated key instead of generating a new one.
    
  • An inline glitchtip.secretKey works as before.
    
  • glitchtip.existingSecret is now the recommended way to set your own key. Argo CD and helm template need it (or an inline glitchtip.secretKey), since they render without cluster access and would generate a new key every time. The README shows how to move an existing install to it without changing the key.