API Deprecation and Removal Planning for %15.9

Removing unused or duplicate values within a sensible time limit ensures that GitLab's APIs maintain a high level of quality and usability.

The deprecation cycle for our APIs requires a minimum of 6 months of deprecation before removal in a major version release.

This means that any fields we want to change or remove need to be deprecated in or before the %15.6 release.

This issue is a collection point for API items that can be deprecated within this time-frame.

How to take part

Check our REST and GraphQL APIs. If you see a field or object that can be removed, add it directly to the list(s) below (along with any blockers). If you have one you're not sure about, open a discussion.

Deprecation in %15.9
Removal in %16.0 (See #367923 (closed))
Edited by Jan Provaznik