From d2e458ad94ebd0d7f1ef5ee704138d8cd77d6c85 Mon Sep 17 00:00:00 2001
From: James King <james@jamesking56.uk>
Date: Fri, 10 Jan 2020 14:05:01 +0000
Subject: [PATCH] docs: GitLab fixed bug with `merge_when_pipeline_succeeds`
 (#5072)

---
 docs/usage/configuration-options.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/usage/configuration-options.md b/docs/usage/configuration-options.md
index 67249c6ed9..e044922481 100644
--- a/docs/usage/configuration-options.md
+++ b/docs/usage/configuration-options.md
@@ -382,7 +382,7 @@ Beware that Renovate follows tags strictly. For example, if you are following a
 
 ## gitLabAutomerge
 
-Caution: when this option is enabled it is possible due to a bug in GitLab that MRs with failing pipelines might still get merged. This is caused by a race condition in GitLab's Merge Request API - [read the corresponding issue](https://gitlab.com/gitlab-org/gitlab/issues/26293) for details.
+Caution (fixed in GitLab >= 12.7): when this option is enabled it is possible due to a bug in GitLab that MRs with failing pipelines might still get merged. This is caused by a race condition in GitLab's Merge Request API - [read the corresponding issue](https://gitlab.com/gitlab-org/gitlab/issues/26293) for details.
 
 ## github-actions
 
-- 
GitLab