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
Additionally to the tags with the full patch version x.y.z, provide tags that allow to be on the latest release of a certain minor version x.y and tags that allow to be on the latest release of a certain major version x.
So
Tag 1.1 should point to the same image as the latest 1.1.* tag (currently 1.1.0, later maybe 1.1.15, but never 1.2.0).
Tag 1 should point to the same image as the latest 1.*.* tag (currently 1.1.0, later maybe 1.5.42, but never 2.0.0).
Off course this is only really useful if this project uses semantic versioning. But although I didn't see it declared explicitly, I assume that's the case, isn't it?
The text was updated successfully, but these errors were encountered:
Hello @das-g , thanks for opening this issue! The use case is described clearly, and it is a legit request.
We'll see how to implement this behavior, but if you feel ready, do not hesitate to open a PR with a proposal (even as a "draft"), as any help is welcome.
Hello @das-g , thanks for opening this issue! The use case is described clearly, and it is a legit request.
We'll see how to implement this behavior, [...]
Additionally to the tags with the full patch version
x.y.z
, provide tags that allow to be on the latest release of a certain minor versionx.y
and tags that allow to be on the latest release of a certain major versionx
.So
Tag
1.1
should point to the same image as the latest1.1.*
tag (currently1.1.0
, later maybe1.1.15
, but never1.2.0
).Tag
1
should point to the same image as the latest1.*.*
tag (currently1.1.0
, later maybe1.5.42
, but never2.0.0
).Off course this is only really useful if this project uses semantic versioning. But although I didn't see it declared explicitly, I assume that's the case, isn't it?
The text was updated successfully, but these errors were encountered: