fix: packageRules.paths definition

lib/config/definitions.js

@@ -309,15 +309,6 @@ const options = [
     stage: 'repository',
     default: ['**/node_modules/**', '**/bower_components/**'],
   },
-  {
-    name: 'paths',
-    description:
-      'List of strings or glob patterns to match against package files. Applicable inside packageRules only',
-    type: 'list',
-    stage: 'repository',
-    cli: false,
-    env: false,
-  },
   {
     name: 'engines',
     description: 'Configuration specifically for `package.json`>`engines`',
@@ -437,6 +428,16 @@ const options = [
     cli: false,
     env: false,
   },
+  {
+    name: 'paths',
+    description:
+      'List of strings or glob patterns to match against package files. Applicable inside packageRules only',
+    type: 'list',
+    stage: 'repository',
+    parent: 'packageRules',
+    cli: false,
+    env: false,
+  },
   // Version behaviour
   {
     name: 'allowedVersions',

website/docs/configuration-options.md

@@ -508,6 +508,8 @@ Use this field if you want to have one or more package names patterns in your pa
 
 The above will set `rangeStrategy` to `replace` for any package starting with `angular`.
 
+### paths
+
 ### updateTypes
 
 Use this field to match rules against types of updates. For example to apply a special label for Major updates:
@@ -523,8 +525,6 @@ Use this field to match rules against types of updates. For example to apply a s
 
 Add to this object if you wish to define rules that apply only to patch updates. See also `major` and `minor` configuration options.
 
-## paths
-
 ## php
 
 Warning: PHP Composer support is in alpha stage so you probably only want to run this if you are helping get it feature-ready.