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
It would help in maintenance if Selenoid and Selenoid UI had tagged images for major and major.minor versions.
For example, currently the latest released version is 1.10.7. The exact same image could also be tagged 1.10 and 1.
This would help on autoupdate scenarios, for example, if I assume the project is using semver, I could rely on the fact that there will not be breaking changes with minor version updates in version 1, simply reference aerokube/selenoid-ui:1 and then let Watchtower update the container when a new version is available, without having to manualy change from 1.10.6 to 1.10.7.
It would help in maintenance if Selenoid and Selenoid UI had tagged images for major and major.minor versions.
For example, currently the latest released version is 1.10.7. The exact same image could also be tagged
1.10
and1
.This would help on autoupdate scenarios, for example, if I assume the project is using semver, I could rely on the fact that there will not be breaking changes with minor version updates in version 1, simply reference
aerokube/selenoid-ui:1
and then let Watchtower update the container when a new version is available, without having to manualy change from1.10.6
to1.10.7
.Looking at the github actions release script it seems that updating https://github.com/aerokube/selenoid/blob/master/ci/docker-push.sh to support it would be enough.
Relying on the
latest-release
tag could break the app, as a version2.x
could come out with breaking changes.The text was updated successfully, but these errors were encountered: