Keep Runner Helm version updated with current release

Problem to solve

The way GitLab Managed Apps define which version of the helm chart to use for the GitLab Runner is checking the version here.

The Helm Chart follows the same process of development as GitLab-ce/ee meaning we have a development period where the feature freeze is the 7th, simply because GitLab Runner follows the same process.

To help explain the problem let's go with the process we have in place right now and what is happening right now:

  1. GitLab %11.11 will get Helm Chart 0.4.1 which means that the user will get a GitLab Runner version 11.10.1 meaning that it's 1 version behind.
  2. We will tag Helm Chart 0.5.0 on the 22nd of May (7th being the feature freeze) which will be 11.11 which then will end up being yet another version behind since that change will land in 12.0.

We need to somehow find a way to update the latest version of Helm, within the same version without having a patch release because it's not really a patch release since it's will be providing new features.

Intended users

Proposal

What does success look like, and how can we measure that?

Users will have GitLab Runner versions in sync with their GitLab instance version

Links / references

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/27096#note_165444024