| 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).
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).