Add latest changes from gitlab-org/gitlab@14-6-stable-eev14.6.0-rc42

1 files changed, 5 insertions, 5 deletions

diff --git a/data/deprecations/14-5-runner-api-status-does-contain-paused.yml b/data/deprecations/14-5-runner-api-status-does-contain-paused.yml
index 8c7cde8a121..5cf7b107354 100644
--- a/data/deprecations/14-5-runner-api-status-does-contain-paused.yml
+++ b/data/deprecations/14-5-runner-api-status-does-contain-paused.yml
@@ -1,15 +1,15 @@
 - name: "REST API Runner will not contain `paused`"
   announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
   removal_milestone: "15.0" # the milestone when this feature is planned to be removed
+  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
   body: | # Do not modify this line, instead modify the lines below.
-    Runner REST API will not return `paused` as a status in GitLab 15.0.
+    The GitLab Runner REST and GraphQL API endpoints will not return `paused` or `active` as a status in GitLab 15.0.
 
-    Paused runners' status will only relate to runner contact status, such as:
-    `online`, `offline`, or `not_connected`. Status `paused` will not appear when the runner is
-    not active.
+    A runner's status will only relate to runner contact status, such as:
+    `online`, `offline`, or `not_connected`. Status `paused` or `active` will no longer appear.
 
     When checking if a runner is `paused`, API users are advised to check the boolean attribute
-    `active` to be `false` instead.
+    `active` to be `false` instead. When checking if a runner is `active`, check if `active` is `true`.
   stage: Verify
   tiers: [Core, Premium, Ultimate]
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/344648