Agent update warning for version N when N+1 has not been released
Problem to solve
GitLab.com version moves to N+1
right after N
has been released, but the GitLab Agent remains at N
until closer to the N+1
release date, when a new release is made. This is a perfectly safe and normal situation for users, but we show a warning.
Proposal
Do not warn when a new version has not been released yet.
-
Look at the KAS version instead of the GitLab version. !87010 (merged) -
On GitLab.com, do not warn if the agent version is N-1
from KAS version, because .com does not always have the same version as theGITLAB_KAS_VERSION
file. Update: Turns out we already allow 1 minor version difference.
Edited by Hordur Freyr Yngvason