Backport to 18.0: Set glab version for release QA tests
What does this MR do and why?
What does this MR do and why?
This backports !194826 (merged) to 18.0.
As part of the backport exception request https://gitlab.com/gitlab-org/release/tasks/-/issues/19613, I noticed that the following tests were failing on !194193 (merged):
1) Verify CI catalog release with glab creates a release with existing tag
2) Verify CI catalog release with glab creates a release with new tag filled with information
Notice the line Please use glab version >= 1.53.0 in the above screenshot.
This test failure was already handled by the Developer Experience team in https://gitlab.com/gitlab-org/gitlab/-/issues/550037. This backport is required, as confirmed by the Developer Experience team in !194189 (comment 2574119043).
References
!194826 (merged) !194193 (merged)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch. -
The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes). -
This MR has a severity label assigned (if applicable). -
Set the milestone of the merge request to match the target backport branch version. -
This MR has been approved by a maintainer (only one approval is required). -
Ensure the e2e:test-on-omnibus-eejob has either succeeded or been approved by a Software Engineer in Test.
Note to the merge request author and maintainer
If you have questions about the patch release process, please:
- Refer to the patch release runbook for engineers and maintainers for guidance.
- Ask questions on the
#releasesSlack channel (internal only).