2022-01-31 18:18:10 +00:00
|
|
|
- name: "REST API Runner will not accept `status` filter values of `active` or `paused`"
|
|
|
|
announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated.
|
|
|
|
announcement_date: "2022-02-22"
|
2022-02-16 15:14:05 +00:00
|
|
|
removal_milestone: "16.0"
|
|
|
|
removal_date: "2023-04-22"
|
2022-01-31 18:18:10 +00:00
|
|
|
breaking_change: true
|
|
|
|
body: | # Do not modify this line, instead modify the lines below.
|
2022-02-16 15:14:05 +00:00
|
|
|
The GitLab Runner REST endpoints will stop accepting `paused` or `active` as a status value in GitLab 16.0.
|
2022-01-31 18:18:10 +00:00
|
|
|
|
|
|
|
A runner's status will only relate to runner contact status, such as: `online`, `offline`.
|
|
|
|
Status values `paused` or `active` will no longer be accepted and will be replaced by the `paused` query parameter.
|
|
|
|
|
|
|
|
When checking for paused runners, API users are advised to specify `paused=true` as the query parameter.
|
|
|
|
When checking for active runners, specify `paused=false`.
|
|
|
|
stage: Verify
|
|
|
|
tiers: [Core, Premium, Ultimate]
|
|
|
|
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/351109
|
|
|
|
documentation_url: https://docs.gitlab.com/ee/api/runners.html
|