Ensure reliability of the release check command
The release check command reported a faulty result:
Chatops job log: https://ops.gitlab.net/gitlab-com/chatops/-/jobs/19172228
It stated gitlab-org/gitlab!195228 (merged) hasn't been deployed to production, when in fact, the merge request was deployed to production on June 23rd
This created confusion among GitLab engineers as they were uncertain about proceeding with other actions that relied on having the MR on production.
The purpose of this issue is to understand why the command returned the wrong output and make the necessary adjustments to prevent this situation from recurring.
Findings
Edited by Reuben Pereira