Could you please explain why this version bump and not 3.15.0?

The general idea of it is to indicate what application (supertokens-core) version is bundled, e.g. to be one of versions from https://github.com/supertokens/supertokens-core/releases. I guess I've just mistyped and it should've be 7.0.13.

If it reflects some other version in your case, let me know, since I was unable to find any version that looks like 3.x.x neither in this repo, nor in others.

So one issue with this is that the helm chart could support more than one version of the core since there are core changes that don't affect any of the configs provided to it. In that case, updating the helm chart version is unnecessary. For example, right now, we deployed core version 7.0.14, which didn't have any changes related to the helm chart.

What do you think is the right solution in this case?

The helm chart has two "versions", the version of chart itself and the version of application.
The general rule is:

• chart version is updated whenever there are changes in some chart (e.g. like this one with adding new variable)
• chart appVersion is changed to indicate what version of app is bundled.
  (The comments in helm chart itself describe it in details)

Ideally how the flow should look like:

1. You update something in supertokens-core and publish new version x.y.z
2. New docker image is built with tag x.y.z
3. In helm chart only appVersion is updated to x.y.z. and in values the proper docker image tag is set.

However in this case if you have for example docker image with tag 7.0 which will contain all patch fixes, we can just put something like 7.0.0 into appVersion in order to show users which "major" version is bundled in this chart.

Gotcha! We are planning on making the docker tag x.y.z as well, but until then, what you said about making it 7.0.0 makes sense. Two more questions:

• I noticed the tag in helm-chart/values.yaml was also changed to 7.0.1. What does tag mean?
• Setting the appVersion seems to have nothing to do with the actual docker image being pulled in right? So in this case, it will always pull in the latest image? If so, maybe we should set the image tag to 7.0 as well, since auto pulling latest is a bad idea (since it can auto pull in breaking changes)

The tag was changed in #27. https://github.com/supertokens/supertokens-docker-postgresql/pull/27/files#diff-15210b6a69967e9488632bf12df699fc922b886f3b38d79fdef46502d8bdbd30R5

And tag is just a variable, that's later used in Deployment and basically represents which docker image tag will be pulled.

BTW, this question also related to #30, since now actually there's no 7.0.1 tag in dockerhub registry.

Yea, that's odd. The tag should be changed to 7.0. Which i see that you have done. Thanks!