summaryrefslogtreecommitdiff
path: root/data/deprecations/15-6-deprecate-merge_status-api-field.yml
diff options
context:
space:
mode:
Diffstat (limited to 'data/deprecations/15-6-deprecate-merge_status-api-field.yml')
-rw-r--r--data/deprecations/15-6-deprecate-merge_status-api-field.yml2
1 files changed, 0 insertions, 2 deletions
diff --git a/data/deprecations/15-6-deprecate-merge_status-api-field.yml b/data/deprecations/15-6-deprecate-merge_status-api-field.yml
index 7d7b160d6bd..48b7824a13d 100644
--- a/data/deprecations/15-6-deprecate-merge_status-api-field.yml
+++ b/data/deprecations/15-6-deprecate-merge_status-api-field.yml
@@ -1,8 +1,6 @@
- title: "merge_status API field"
announcement_milestone: "15.6"
- announcement_date: "2022-11-22"
removal_milestone: "16.0"
- removal_date: "2023-05-22"
breaking_change: true
body: |
The `merge_status` field in the [merge request API](https://docs.gitlab.com/ee/api/merge_requests.html#merge-status) has been deprecated in favor of the `detailed_merge_status` field which more correctly identifies all of the potential statuses that a merge request can be in. API users are encouraged to use the new `detailed_merge_status` field instead. The `merge_status` field will be removed in v5 of the GitLab REST API.