Follow-up from "Fix some usages of check_runner_upgrade_status"
The following discussion from !92411 (merged) should be addressed:
-
@morefice started a discussion: (+2 comments) note(not-blocking): I wonder if we should improve our Gitlab::Ci::RunnerUpgradeCheck class to extend it so it's easier to dissociate the status and the suggested status.