Few weeks ago, the MicroShift errata publication workflow has changed. New process is described here: https://spaces.redhat.com/pages/viewpage.action?spaceKey=PLUG&title=USHIFT+Publishing+Errata 

The summary is that now we need to manually check every week for every OCP advisory if there are any security fix (CVE) or MicroShift change we want or need to release. In that case, we have to request ART team to publish a new MicroShift version.

The goal of this spike is to investigate if and how we can automate the process outlined in the previous paragraph.

The output of this task should be task/s to automate the checks to decide if we need to request new MicroShift advisory publication.