See https://issues.redhat.com/browse/OCPBUGS-42448 for more context.

We should create tags in GitHub for OpenShift releases. Minimally we should create y-stream tags, but ideally we could automate z-stream tags.

Not only would this prevent things from breaking like the bug shows, but would also be convenient for users importing the installer and for browsing the installer in github at a particular version.

Things to consider:

• In order to use a semantic tag that begins with 4, we would need to update our go module to have a 4 suffix, which is probably something we don't want to do. If we change our module in that manner, we MAY need to notify any repos that depend on our code, such as the assisted-installer & hive. So we want to test whether changing our module in that manner would require updates on how the installer is vendored
• For automating Z stream releases, we can read the commits directly out of the release image. A cron job with access to the release repo and the github API should be sufficient to get the job done.
• Despite the bug fix, pulling the installer module at a branch e.g. go get github.com/openshift/installer@release-4.17 remains broken. Backporting the tags may potentially fix this...