From 275ef417d8e68e54a4317f8416af7dc87e229e4b Mon Sep 17 00:00:00 2001 From: Colin O'Dell <colinodell@gmail.com> Date: Wed, 17 Aug 2022 05:07:39 -0400 Subject: [PATCH] docs: `versioning` should not be combined with `matchUpdateTypes` (#17220) Co-authored-by: Rhys Arkins <rhys@arkins.net> --- docs/usage/modules/versioning.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/usage/modules/versioning.md b/docs/usage/modules/versioning.md index 9b4b98c526..75832b1360 100644 --- a/docs/usage/modules/versioning.md +++ b/docs/usage/modules/versioning.md @@ -22,7 +22,8 @@ Configuring or overriding the default `versioning` can be particularly helpful f - Although you can reconfigure versioning per-manager or per-datasource, it's unlikely that such a broad change would ever be needed - More commonly you would need to configure `versioning` for individual packages or potentially package patterns -- The best way to do this is with `packageRules`, with a combination of `matchManagers`, `matchDatasources`, `matchPackageNames` and `matchPackagePatterns` +- The best way to do this is with `packageRules`, with a combination of `matchManagers`, `matchDatasources`, `matchPackageNames` and `matchPackagePatterns`. + Avoid configuring `versioning` in a rule that also uses `matchUpdateTypes`, as the update types aren't known at the time the `versioning` is applied. ## Examples of versioning overrides -- GitLab