From 1e375928438bf70c553c29f440e57aeb59ba5d3c Mon Sep 17 00:00:00 2001
From: Rhys Arkins <rhys@arkins.net>
Date: Thu, 18 Oct 2018 12:46:38 +0200
Subject: [PATCH] docs: fix ignoreUnstable description

Closes #2666
---
 website/docs/configuration-options.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/website/docs/configuration-options.md b/website/docs/configuration-options.md
index 5c73a013a7..006eb110e1 100644
--- a/website/docs/configuration-options.md
+++ b/website/docs/configuration-options.md
@@ -280,7 +280,9 @@ Using this setting, you can selectively ignore package files that you don't want
 
 ## ignoreUnstable
 
-By default, Renovate won't update any packages to unstable versions (e.g. `4.0.0-rc3`) unless the package version was _already_ unstable (e.g. it was already on `4.0.0-rc2`). If for some reason you wish to _force_ unstable updates on Renovate, you can set `ignoreUnstable` to `false`, but this is not recommended for most situations.
+By default, Renovate won't update any package versions to unstable versions (e.g. `4.0.0-rc3`) unless the current version has the same major.minor.patch and was _already_ unstable (e.g. it was already on `4.0.0-rc2`). Renovate will not "jump" unstable versions automatically, e.g. if you are on `4.0.0-rc2` and newer versions `4.0.0` and `4.1.0-alpha.1` exist then Renovate will upate you to `4.0.0` only. If you need to force permanent unstable updates for a package, you can add a package rule setting `ignoreUnstable` to `false`.
+
+Also check out the `followTag` configuration option above if you wish Renovate to keep you pinned to a particular release tag.
 
 ## includePaths
 
-- 
GitLab