Add deprecation post

data/deprecations/14-5-runner-api-status-does-contain-paused.yml

-- name: "REST API Runner will not contain `paused`"
+- name: "REST and GraphQL API Runner status will not return `paused`"
   announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
   announcement_date: "2021-11-22"
   removal_milestone: "15.0" # the milestone when this feature is planned to be removed

data/deprecations/14-8-runner-api-active-field-replaced-with-paused-breaking-change.yml

+- name: "REST and GraphQL API Runner usage of `active` replaced by `paused`"
+  announcement_milestone: "14.8"
+  announcement_date: "2022-02-22"
+  removal_milestone: "15.0"
+  removal_date: "2022-05-22"
+  breaking_change: true
+  reporter: pedropombeiro
+  body: |
+    Occurrences of the `active` identifier in the GitLab Runner REST and GraphQL API endpoints will be
+    renamed to `paused` in GitLab 15.0, namely:
+
+    - GraphQL API:
+      - the `CiRunner` property;
+      - the `RunnerUpdateInput` input type for the `runnerUpdate` mutation;
+      - the `runners` and `Group.runners` queries.
+    - REST API:
+      - endpoints taking or returning `active` properties, such as:
+        - `GET /runners`
+        - `GET /runners/all`
+        - `GET /runners/:id` / `PUT /runners/:id`
+        - `PUT --form "active=false" /runners/:runner_id`
+        - `GET /projects/:id/runners` / `POST /projects/:id/runners`
+        - `GET /groups/:id/runners`
+
+    The 15.0 release of the GitLab Runner will start using the `paused` property when registering runners, and therefore
+    will only be compatible with GitLab 15.0 and later. Until 15.0, GitLab will accept the deprecated `active` flag from
+    existing runners.
+  stage: Verify
+  tiers: [Core, Premium, Ultimate]
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/347211
+  documentation_url: https://docs.gitlab.com/ee/api/runners.html
+  image_url: # (optional) This is a link to a thumbnail image depicting the feature
+  video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg

doc/update/deprecations.md

@@ -226,7 +226,7 @@ In milestone 15.0, we will remove the `pipelines` attribute from the API respons
 
 **Planned removal milestone: 15.0 (2022-05-22)**
 
-### REST API Runner will not contain `paused`
+### REST and GraphQL API Runner status will not return `paused`
 
 WARNING:
 This feature will be changed or removed in 15.0
@@ -717,6 +717,36 @@ The `merged_by` field in the [merge request API](https://docs.gitlab.com/ee/api/
 
 ## 14.8
 
+### REST and GraphQL API Runner usage of `active` replaced by `paused`
+
+WARNING:
+This feature will be changed or removed in 15.0
+as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
+Before updating GitLab, review the details carefully to determine if you need to make any
+changes to your code, settings, or workflow.
+
+Occurrences of the `active` identifier in the GitLab Runner REST and GraphQL API endpoints will be
+renamed to `paused` in GitLab 15.0, namely:
+
+- GraphQL API:
+  - the `CiRunner` property;
+  - the `RunnerUpdateInput` input type for the `runnerUpdate` mutation;
+  - the `runners` and `Group.runners` queries.
+- REST API:
+  - endpoints taking or returning `active` properties, such as:
+    - `GET /runners`
+    - `GET /runners/all`
+    - `GET /runners/:id` / `PUT /runners/:id`
+    - `PUT --form "active=false" /runners/:runner_id`
+    - `GET /projects/:id/runners` / `POST /projects/:id/runners`
+    - `GET /groups/:id/runners`
+
+The 15.0 release of the GitLab Runner will start using the `paused` property when registering runners, and therefore
+will only be compatible with GitLab 15.0 and later. Until 15.0, GitLab will accept the deprecated `active` flag from
+existing runners.
+
+**Planned removal milestone: 15.0 (2022-05-22)**
+
 ### Vulnerability Check
 
 WARNING: