Early branch: Adjust the verify stable branch on the final RC
When tagging the final release candidate, a job is executed to review the status of the stable branches and guarantee they're ready to be tagged (green)
When testing the release candidate automation on #21327 (closed), it was noticed the verify_stable_branch is not compatible with the stable_branch_check_release_environments_only feature flag. This feature flag makes the stable branch review only accounts for release environments. However, for monthly releases the canonical path is used and this one doesn't have release environments (those are present on security)
I noticed this by exploring the log output of a failed job https://ops.gitlab.net/gitlab-org/release/tools/-/jobs/19324764
2025-07-15 20:33:32.244749 I ReleaseTools::Services::ComponentStatusService -- Checking component pipeline status -- {project: "gitlab-ee", project_path: "gitlab-org/gitlab", branch: "18-2-stable-ee", status: nil}Notice how the status says nil for gitlab-ee. I temporarily disabled the FF and the job succeeded after that https://ops.gitlab.net/gitlab-org/release/tools/-/jobs/19324766
2025-07-15 20:34:53.934395 I ReleaseTools::Services::ComponentStatusService -- Checking component pipeline status -- {project: "gitlab-ee", project_path: "gitlab-org/gitlab", branch: "18-2-stable-ee", status: "success"}.We need to either:
- Adjust the logic to not review RE on monthly
- Use security paths for monthly releases (preferred)