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
{{ message }}
This repository has been archived by the owner on Oct 19, 2024. It is now read-only.
I've just noticed that your CI workflow updates a docker image with the latest tag whenever it runs. But is this the right approach for the docker image versioning?
I think that the latest image tag should be updated only in release workflow and should always include only the latest release version of argocd-notifications.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, everyone!
I've just noticed that your CI workflow updates a docker image with the
latest
tag whenever it runs. But is this the right approach for the docker image versioning?I think that the
latest
image tag should be updated only in release workflow and should always include only the latest release version of argocd-notifications.What do you think?
Beta Was this translation helpful? Give feedback.
All reactions