Add WARNING headers to API responses that have deprecated features
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
We include deprecation information in documentation, but we can help clients to notice deprecations by using the warning header standard.
Release notes
Problem to solve
Users may write and deploy API integrations, and not notice that some features later get deprecated. It is unrealistic to expect users and developers to keep up-to-date with all deprecation notices.
Proposal
For all API (REST and GraphQL) responses that include a deprecated feature, add an appropriate warning header including a link to the deprecation notice with full details.
Intended users
Feature Usage Metrics
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.