Chatwoot helm deployment version issue.

[sumanthgarrix]

Hi @ALL

We have deployed the Chatwoot 3.11.0 application in GKE using Helm. After upgrading to 3.11.1 (docker pull chatwoot/chatwoot
.11.1), the Helm deployment was successful, but the application is still showing version 3.11.0. Can anyone help with this?

Metric | Value -- | -- **Chatwoot version | 3.11.0 Git SHA | 6196a6d**

$ kubectl describe po chatwoot-web-7bbdf9c568-q8q2d -n chatwoot
Name: chatwoot-web-7bbdf9c568-q8q2d
Namespace: chatwoot
Priority: 0
Service Account: chatwoot
Node: gk3-sl-core-auto-gke-uc1-nap-1aaefwnk-adf9c4a7-j340/10.15.0.49
Start Time: Sun, 01 Sep 2024 23:04:40 +0530
Labels: app=chatwoot
pod-template-hash=7bbdf9c568
release=chatwoot
role=web
Annotations: checksum/config: 549308453e84de3bacedd77bc7159dcac27f9aed5abf0718457593fbbf28cf0f
Status: Running
SeccompProfile: RuntimeDefault
IP: 10.35.0.110
IPs:
IP: 10.35.0.110
Controlled By: ReplicaSet/chatwoot-web-7bbdf9c568
Containers:
chatwoot-web:
Container ID: containerd://a180af763077e80e1d30a6ec9dc147817e08401a96432030265c887e3adb8b6c
Image: chatwoot/chatwoot:hotfix-v3.11.1
Image ID: docker.io/chatwoot/chatwoot@sha256:235d55a01c32981ff3527132582d2560ab69d70659690e13b46290e3630d664b
Port: 3000/TCP
Host Port: 0/TCP

$ kubectl get po -n chatwoot

NAME READY STATUS RESTARTS AGE
chatwoot-chatwoot-postgresql-0 1/1 Running 0 43h
chatwoot-chatwoot-redis-master-0 1/1 Running 0 43h
chatwoot-chatwoot-redis-replicas-0 1/1 Running 2 (43h ago) 44h
chatwoot-web-7bbdf9c568-2pnn7 1/1 Running 0 22h
chatwoot-worker-5f674597b4-fxzjs 1/1 Running 0 43h