Skip to content

Fix wrong removal milestone in comment

What does this MR do and why?

Describe in detail what your merge request does and why.

This MR corrects the removal milestone for the active property and the active and paused status values from the Runners API, from %15.0 to %16.0, to allow for 6 milestones of advance warning, as mentioned in the GraphQL deprecation documentation. That had been already an MR to fix this (!81919 (merged)) but it missed these 2 comments, as pointed out by #344918 (comment 889867706).

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Pedro Pombeiro

Merge request reports

Loading