You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: