announcement_milestone:"15.0"# The milestone when this feature was first announced as deprecated.
announcement_date:"2022-05-22"# The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
removal_milestone:"16.0"# The milestone when this feature is planned to be removed
removal_date:"2023-05-22"# The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
breaking_change:true# If this deprecation is a breaking change, set this value to true
reporter:pedropombeiro # GitLab username of the person reporting the deprecation
body:| # Do not modify this line, instead modify the lines below.
The `legacyMode` argument to the `status` field in `RunnerType` will be rendered non-functional in the 16.0 release
as part of the deprecations details in the [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351109).
In GitLab 16.0 and later, the `status` field will act as if `legacyMode` is null. The `legacyMode` argument will
be present during the 16.x cycle to avoid breaking the API signature, and will be removed altogether in the
