Commit 02e3ac05 authored by James Ramsay's avatar James Ramsay 🇮🇶 Committed by James Ramsay

Add specific version and date

parent 0b3b0f78
......@@ -4,10 +4,10 @@ author: James Ramsay
author_gitlab: jramsay
author_twitter: jamesramsay
categories: GitLab API
description: "With the removal of deprecated GitLab API v3, requests to the API v3 will fail."
description: "With the removal of deprecated GitLab API v3 in GitLab 11.0, requests to the API v3 will fail."
---
In an upcoming release, **integrations using the API v3 will not be able to
In GitLab 11.0, **integrations using the API v3 will not be able to
communicate with GitLab anymore**, since the old version of the API will be
removed. All integrations using the API v4 will continue to work as usual
without any modification. We encourage all of our users who are still using the
......@@ -20,9 +20,6 @@ In the GitLab 8.17 release post, we announced the [deprecation of API v3](
/2017/02/22/gitlab-8-17-released/#api-v3-deprecation), and that support for API
v3 would be dropped in a future release.
**We are still seeing a high volume of traffic on GitLab.com using API v3
requests.**
Please ensure that you upgrade any integrations to API v4 to avoid any
downtime. Documentation is available for [CE](
https://docs.gitlab.com/ce/api/v3_to_v4.html) and [EE](
......@@ -30,8 +27,8 @@ https://docs.gitlab.com/ee/api/v3_to_v4.html).
## When will this happen?
The API v3 will be removed in the next major release after 22 March, 2018.
The API v3 will be removed in GitLab 11.0 on 22 June, 2018.
Please consider that integrations using API v3 connected to GitLab.com will
stop working as soon as the first RC is deployed to production, and this will
happen around April, 2018. **Be sure that you update all integrations before
happen around 4 June, 2018. **Be sure that you update all integrations before
this date**.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment