Would be great instead of the version change script, that we could also have the option of pulling a singlestore engine version image directly - great for CI/CD too.
Describe the solution you'd like
A github action that on a version bump would use a build matrix to build all the Singlestore engine versions currently supported into separate packages and publish them to GHCR or docker hub.
Describe alternatives you've considered
We can do this in our organisation already, but would be nice if it was done by Singlestore themselves.
Additional context
Not sure how the versioning would work with the image version, maybe a naming convention?
For example, version 8.5.7 of the engine at the current release tag of 0.2.19
Would be great instead of the version change script, that we could also have the option of pulling a singlestore engine version image directly - great for CI/CD too.
Describe the solution you'd like A github action that on a version bump would use a build matrix to build all the Singlestore engine versions currently supported into separate packages and publish them to GHCR or docker hub.
Describe alternatives you've considered We can do this in our organisation already, but would be nice if it was done by Singlestore themselves.
Additional context Not sure how the versioning would work with the image version, maybe a naming convention?
For example, version
8.5.7of the engine at the current release tag of 0.2.19Or just:
In docker-compose.yml.