diff --git a/website/docs/_posts/2017-10-05-configuration-options.md b/website/docs/_posts/2017-10-05-configuration-options.md index b26149b3d3d1f78052340826bc72f9da458a7aac..c5355e5c38d061344af4d0c0eccaa89e32445ba6 100644 --- a/website/docs/_posts/2017-10-05-configuration-options.md +++ b/website/docs/_posts/2017-10-05-configuration-options.md @@ -434,7 +434,7 @@ Configuration for lock file maintenance. | name | value | | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | type | configuration object | -| default | {% raw %}{<br /> "enabled": true,<br /> "recreateClosed": true,<br /> "branchName": "renovate/lock-files",<br /> "commitMessage": "{{semanticPrefix}}Update lock file",<br /> "prTitle": "{{semanticPrefix}}Lock file maintenance",<br /> "prBody": "This PR regenerates lock files to keep them up-to-date.",<br /> "schedule": ["before 5am on monday"]<br />}{% endraw %} | +| default | {% raw %}{<br /> "enabled": false,<br /> "recreateClosed": true,<br /> "schedule": ["before 5am on monday"]<br />}{% endraw %} | By setting enabled=true, this means that the default behaviour is to "maintain" lock files for each `package.json` if they exist already. "Maintaining" a lock file means recreating it to get an up-to-date version and committing that. Supported lock files include `package-lock.json` (npm >= 5) and `yarn.lock` (yarn).