Remove GraphQL and API deprecations from Deprecations and removals by version
Issue Description
Per our guidelines for deprecations and removals, there is a separate process for GraphQL and REST API docs.
As applicable, the GraphQL and REST API deprecations should be removed from the main deprecations page (Deprecations and removals by version) in data/deprecations and added to the relevant doc instead.
For example, this probably shouldn't be in the deprecations page: https://new.docs.gitlab.com/update/deprecations/#graphql-api-runner-status-will-not-return-paused
Files that are likely misplaced
| File | In GraphQL/Rest deprecation docs? |
|---|---|
| 14-5-runner-api-status-does-contain-paused.yml | Yes and Yes |
| 14-8-graphql-runner-active.yml | Yes |
| 15-2-job_age-deprecation.yml | Keep, true breaking change, no waiting for REST v5. |
| 15-8-deprecate-disabled-with-override-runner-setting-value.yml | Yes |
| 15-9-deprecate-runner-setup-instructions-api.yml | Yes |
| 15-9-deprecate-take-schedule-ownership-field.yml | Yes |
| 16-0-graphql-RunnerMembershipFilter-renamed.yml | Yes |
| 16-2-cirunner_fields.yml | Yes and Yes |
| 17-5-deprecate-ciUsedMinutes-graphql-field.yml |
Yes, and deprecation doc incorrect anyways: ciUsedMinutes != ciMinutesUsed
|
| 17-5-deprecate-merge-train-graphql-fields.yml | Yes |
| 18-0-graphql-removal.yml | Yes |
Files that are potentially misplaced
Edited by Marcel Amirault