As of the point of writing this, v0.8.1 is the latest Scrutiny version.
As I'm manually updating my images and not using something like "latest", I have to change the image tag every new release. It would be nice if I wouldn't have to do that for patch releases (minor releases too).
Currently these tags are provided:
v0.8.1 - Version 0.8.1
v0.8.0 - Version 0.8.0
v0.7.3 - Version 0.7.3
latest - Version 0.8.1
Desired Behavior
I would propose a tag system like this:
v0.8.1 - Version 0.8.1
v0.8.0 - Version 0.8.0
v0.8 - Version 0.8.1
v0 - Version 0.8.1
latest - Version 0.8.1
This would allow pinning to specific version and allows the user to choose which semver types they are okay with auto updating.
I for example would have pinned to v0 and would have automatically gotten the update up to 0.8.1.
However I won't get the update to a new major version like "v1.x" which would be desired for me.
Description
As of the point of writing this,
v0.8.1is the latest Scrutiny version. As I'm manually updating my images and not using something like "latest", I have to change the image tag every new release. It would be nice if I wouldn't have to do that for patch releases (minor releases too).Currently these tags are provided:
v0.8.1- Version 0.8.1v0.8.0- Version 0.8.0v0.7.3- Version 0.7.3latest- Version 0.8.1Desired Behavior
I would propose a tag system like this:
v0.8.1- Version 0.8.1v0.8.0- Version 0.8.0v0.8- Version 0.8.1v0- Version 0.8.1latest- Version 0.8.1This would allow pinning to specific version and allows the user to choose which semver types they are okay with auto updating. I for example would have pinned to
v0and would have automatically gotten the update up to0.8.1. However I won't get the update to a new major version like "v1.x" which would be desired for me.