-
Notifications
You must be signed in to change notification settings - Fork 498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More frequent tagged releases/images #1783
Comments
@umdstu canary tag is published with every main commit you can use it. |
Thank you for your quick response @manugupt1 . I actually did come across that this morning but wasn't sure about the reliability of it or that I could be using a changed version without knowing. Is there a release schedule? When I glanced before it looked loosely like one version per year. Thanks again! |
We currently lack maintainers and current maintainers do not have the bandwidth to support frequent releases and regressions if they come along with it. Please see: #1734 |
Totally understand, just trying to get a better understanding. Thanks for the details! I'll go ahead and close this as it seems like this is all by design. |
Is your feature request related to a problem? Please describe.
Can we get more frequent tagged releases? v0.11.0 is quite far behind. Using the published docker image isn't even an options at this point.
Describe the solution you'd like
More frequent tagged releases / published containers when significant changes are merged into
main
Describe alternatives you've considered
Cloning the repo as a git submodule, and building a new container occasionally.
Additional context
The latter alternative is challenging on offline networks, accessing published docker images is far easier.
The text was updated successfully, but these errors were encountered: