Request for Major Version Docker Tags for Easier Version Management

[hutchic]

Is your proposal related to a problem?

I frequently find myself manually updating Docker tags in my configurations to stay updated with the latest patch version of the Hasura GraphQL Engine. This manual process is prone to delays and errors, impacting the reliability and security of deployments.

Describe the solution you'd like

I suggest publishing Docker images with major version tags (e.g., v2) that automatically track the latest v2.x.z release. This would allow users to always use the latest patch within a major version without manual updates.

Describe alternatives you've considered

An alternative is to continue manually updating to specific versions, but this is less efficient and can lead to missed updates.

[SamirTalwar]

I believe the latest tag will always track the latest version. Does that suit you?

You can see that it's the same as v2.37 here: https://hub.docker.com/r/hasura/graphql-engine/tags

v3 will use different images (and a whole new architecture) so you don't need to worry about accidentally upgrading to a new major version.

[hutchic]

Maybe, latest I assumed would also track major bumps ie it would rugpull to v3 sometime in the near-ish future?

[SamirTalwar]

I've confirmed internally that Hasura will not hijack latest to push a v3 image; it will always be v2.