From ac1716a545e957783bf934bf0d96835271d2ad56 Mon Sep 17 00:00:00 2001
From: Rhys Arkins <rhys@arkins.net>
Date: Tue, 27 Jul 2021 10:24:55 +0200
Subject: [PATCH] docs: clarify constraints
---
docs/usage/configuration-options.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/docs/usage/configuration-options.md b/docs/usage/configuration-options.md
index c3b3717086..e7516bd064 100644
--- a/docs/usage/configuration-options.md
+++ b/docs/usage/configuration-options.md
@@ -344,9 +344,10 @@ Configure this option to `false` if you prefer Renovate to open a new issue when
Constraints are used in package managers which use third party tools to update "artifacts" like lock files or checksum files.
Typically, the constraint is detected automatically by Renovate from files within the repository and there is no need to manually configure it.
+Manually specifying constraints is supported for `ruby`, `bundler`, `composer`, `go`, `npm`, `yarn`, `pnpm`, `python`, `pipenv`, and `poetry`.
Constraints are also used to manually restrict which _datasource_ versions are possible to upgrade to based on their language support.
-For now this only supports `python`, other compatibility restrictions will be added in the future.
+For now this datasource constraint feature only supports `python`, other compatibility restrictions will be added in the future.
```json
{
--
GitLab