renovate/test/config/__snapshots__/index.spec.js.snap

// Jest Snapshot v1, https://goo.gl/fbAQLP

exports[`config/index mergeChildConfig(parentConfig, childConfig) merges 1`] = `
Object {
  "branchTopic": "lock-file-maintenance",
  "commitMessageAction": "Lock file maintenance",
  "commitMessageExtra": null,
  "commitMessageTopic": null,
  "enabled": false,
  "groupName": null,
  "rebaseStalePrs": true,
  "recreateClosed": true,
  "schedule": Array [
    "on monday",
  ],
}
`;
feat: schedule support for lock file maintenance This feature now allows a custom schedule to be defined for lock file maintenance. It is now enabled by default but runs only before 5m on Sundays. Closes #399 BREAKING CHANGE: lock file maintenance is enabled by default. Rules will apply to both yarn and npm (npm is yet to be implemented however). Existing mainainYarn* variables are removed and replaced by new lockFileMaintenance object. 2017-07-01 04:44:41 +00:00			`// Jest Snapshot v1, https://goo.gl/fbAQLP`

			exports[`config/index mergeChildConfig(parentConfig, childConfig) merges 1`] = `
			`Object {`
feat: modular branchName/prTitle/commitMessage templating (#1760) This PR refactors `branchName`, `commitMessage` and `prTitle` so that they are more easily editable and hopefully more understandable. By breaking each up into subsections, users can modify one part without needing to copy/paste the entire string. Directly editing any of these fields will now be deprecated and a warning issued. 2018-04-17 06:39:26 +00:00			`"branchTopic": "lock-file-maintenance",`
fix: lock file maintenance commit message and pr title 2018-04-17 10:22:11 +00:00			`"commitMessageAction": "Lock file maintenance",`
			`"commitMessageExtra": null,`
			`"commitMessageTopic": null,`
feat: default lockFileMaintenance to disabled (#1066) Closes #590 BREAKING CHANGE: lock file maintenance is now disabled by default. 2017-11-01 08:45:30 +00:00			`"enabled": false,`
fix: don’t group lockFileMaintenance update (#890) Setting lockFileMaintenance.groupName = null will prevent the case where the user configures a repository groupName like “all” and then that group inherits the schedule of lock file maintenance. Instead, there will be renovate/all and renovate/lock-file-maintenance. Fixes #885 2017-10-05 09:07:15 +00:00			`"groupName": null,`
fix: improve lockfile maintenance deletion logic Set lock file branches to always rebase stale, and delete if there’s no work to do. 2018-03-20 05:48:27 +00:00			`"rebaseStalePrs": true,`
refactor: set recreateClosed in group and lockFileMaintenance 2017-07-02 04:21:24 +00:00			`"recreateClosed": true,`
fix: Schedule should always be an array (#580) Massaging of string to array is done in migration function. 2017-08-02 14:14:09 +00:00			`"schedule": Array [`
			`"on monday",`
			`],`
feat: schedule support for lock file maintenance This feature now allows a custom schedule to be defined for lock file maintenance. It is now enabled by default but runs only before 5m on Sundays. Closes #399 BREAKING CHANGE: lock file maintenance is enabled by default. Rules will apply to both yarn and npm (npm is yet to be implemented however). Existing mainainYarn* variables are removed and replaced by new lockFileMaintenance object. 2017-07-01 04:44:41 +00:00			`}`
			`;