From 8a2a3984816a25e84a231ccc16726b0c70151a35 Mon Sep 17 00:00:00 2001
From: Rhys Arkins <rhys@arkins.net>
Date: Thu, 29 Aug 2019 16:22:32 +0200
Subject: [PATCH] docs: update-lockfile limitations

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

diff --git a/website/docs/configuration-options.md b/website/docs/configuration-options.md
index 85d8a17dbc..d3d0868912 100644
--- a/website/docs/configuration-options.md
+++ b/website/docs/configuration-options.md
@@ -943,7 +943,7 @@ Behaviour:
 - `bump` = e.g. bump the range even if the new version satisifies the existing range, e.g. `^1.0.0` -> `^1.1.0`
 - `replace` = Replace the range with a newer one if the new version falls outside it, e.g. `^1.0.0` -> `^2.0.0`
 - `widen` = Widen the range with newer one, e.g. `^1.0.0` -> `^1.0.0 || ^2.0.0`
-- `update-lockfile` = Update the lock file when in-range updates are available, otherwise `replace` for updates out of range
+- `update-lockfile` = Update the lock file when in-range updates are available, otherwise `replace` for updates out of range. Works only for `npm` and `yarn` so far.
 
 Renovate's `"auto"` strategy works like this for npm:
 
-- 
GitLab