Add step to monthly release to update gitlab ci
What does this MR do and why?
Adds a step to the monthly release template to update the gitlab-org/gitlab
CI so the last three stable branches will trigger slack notifications for pipeline failures.
As noted in this comment, it is not yet possible to have logic in workflow:rules
to dynamically determine the last three versions.
For reference, this CI rule was introduced in gitlab!108718 (merged).
In the future if it does not look like the CI will be able to be dynamic here, we may be able to automate the creation of the MR the new step is adding.
Author Check-list
- [-] Has documentation been updated?
Related to gitlab-com/gl-infra/delivery#2775 (closed)
Edited by Steve Abrams