From 13f4b02560280eeee93b70a41923d0d49c0c40b8 Mon Sep 17 00:00:00 2001
From: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Date: Tue, 25 Apr 2023 07:36:49 +0200
Subject: [PATCH] docs(config options): warn about SemVer 0.x packages (#21747)
---
docs/usage/configuration-options.md | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/docs/usage/configuration-options.md b/docs/usage/configuration-options.md
index 910e7353c0..05b089229a 100644
--- a/docs/usage/configuration-options.md
+++ b/docs/usage/configuration-options.md
@@ -2266,8 +2266,8 @@ Here's an example of where you use this to group together all packages from the
### matchUpdateTypes
-Use this field to match rules against types of updates.
-For example to apply a special label for Major updates:
+Use `matchUpdateTypes` to match rules against types of updates.
+For example to apply a special label to `major` updates:
```json
{
@@ -2280,6 +2280,13 @@ For example to apply a special label for Major updates:
}
```
+<!-- prettier-ignore -->
+!!! warning
+ Packages that follow SemVer are allowed to make breaking changes in _any_ `0.x` version, even `patch` and `minor`.
+ Check if you're using any `0.x` package, and see if you need custom `packageRules` for it.
+ When setting up automerge for dependencies, make sure to stop accidental automerges of `0.x` versions.
+ Read the [automerge non-major updates](./key-concepts/automerge.md#automerge-non-major-updates) docs for a config example that blocks `0.x` updates.
+
### matchConfidence
<!-- prettier-ignore -->
--
GitLab