Notes:
Preparing CPaaS to update release.yml and rename a directory under versions.
1. Bump a corresponding release branch (based on the new release) - for instance https://gitlab.cee.redhat.com/cpaas-products/openshift-secondary-scheduler-operator/-/tree/main/versions. E.g. 1.1.1 will require to bump release-1.1.1 branch into release 1.1.2. E.g. https://gitlab.cee.redhat.com/cpaas-products/openshift-secondary-scheduler-operator/-/commit/7a519ee30a202a0278ed430d8d1bea75f83ea19c
2. Remove advisory_map.yml file under the corresponding release branch so a new advisory gets automatically created (later in the workflow). If not removed the CPaaS will try to update an already existing advisory for the previous release. E.g. https://gitlab.cee.redhat.com/cpaas-products/openshift-secondary-scheduler-operator/-/commit/abf83b2b3d08f8df1cf2c8ba9e4d96efeee247b2
3. Update release.yml under the corresponding branch (bump z-stream versions for the advisory text and change the release jira card (fixed field) to the current one). E.g. https://gitlab.cee.redhat.com/cpaas-products/openshift-secondary-scheduler-operator/-/commit/a7b05ce6cb6973722bb5513f2abc97bcf3ae59a5
4. Rerun pipeline-seed job to regenerate the jobs for the new release. The newly regenerated jobs will trigger poll-upstream-sources jobs for all available branches/releases.

Alternatively, you can also review how other team might configure z-stream in different way: https://docs.google.com/document/d/1AS2v_zD-y9xdr__tlYv1x-eEVrogfRT7BxUXZMtzQ_A/edit

Resources:
https://docs.google.com/document/d/1Y3q5VqBKwF2X5gV-KfcSRSTLnoeUlHHHhpDbEpntzFQ/edit#heading=h.ums8y4xz2t13
Google space to ask questions: CPaaS Users

Responsible: Engineering