Skip to content
Snippets Groups Projects
  1. Feb 27, 2018
  2. Feb 02, 2018
  3. Jan 23, 2018
    • Rhys Arkins's avatar
      feat: apply package.json renovate config to whole repository (#1419) · 0b7deb54
      Rhys Arkins authored
      Changes the way Renovate treats renovate config inside `package.json` files. Before, config used to be applied only to that particular file, meaning that it was not applied for the rest of a monorepo, or for other package managers like Docker. Now, any `renovate` section inside the repository’s root `package.json` will be applied globally, just the sams as if it were contained within a `renovate.json` file. This means there is no longer any case where you *must* have a `renovate.json` file instead of `package.json`.
      
      Closes #1323
      
      BREAKING CHANGE: renovate config in `./package.json` is now applied to whole repository, and renovate config inside non-root `package.json` files is now ignored.
  4. Jan 21, 2018
  5. Jan 20, 2018
    • Rhys Arkins's avatar
      feat: bumpVersion (#1413) · b72bfdf4
      Rhys Arkins authored
      Adds a new configuration option that allows you to bump the version number in the package.json being updated. e.g. you might configure Renovate to bump a patch every time, or maybe for dependencies only and not devDependencies. e.g. if you configure `"bumpVersion": "patch"` then a Renovate PR updating a `package.json` that used to be version `1.2.1` will now see it updated to `1.2.2` (in addition to the dependency version(s) being updated too). Thanks to @gunar for the feature suggestion.
      
      Closes #861
  6. Jan 15, 2018
  7. Dec 29, 2017
    • Rhys Arkins's avatar
      feat: pathRules · f8a10a9f
      Rhys Arkins authored
      Adds new configuration option “pathRules”. pathRules is an array of path rules. Each rule should contain a “paths” array which uses string or glob matching like the existing ignorePaths. If any of the paths in a rule matches a packageFile then the remaining configuration from the rule is applied to the packageFile.
  8. Dec 18, 2017
  9. Dec 14, 2017
  10. Dec 11, 2017
  11. Dec 07, 2017
  12. Dec 05, 2017
    • Rhys Arkins's avatar
      feat: travis.yml node_js versions support (#1243) · b8dadb71
      Rhys Arkins authored
      This PR adds support for renovating the `node_js` versions in `.travis.yml` configuration files. Important notes:
      - Functionality is disabled by default and hence opt-in via configuration
      - Added a new manager type `node` because it is anticipated to support more than just Travis in future, with mostly unified logic
      - Added the config option "policy" with supported values: lts, active, current, lts_latest and lts_active
      - Policy is actually an array, to allow additive combining, e.g. `["lts_latest", "current"]`
      - Actual node versions are *hardcoded*. There is no perfect metadata source for this and they change infrequently enough that it is definitely not a problem for now (next change will be in April 2018)
      - If node versions need updating, they are listed from newest to oldest
      - Replacing function attempts to detect the indention (spacing) in file and use that
      
      To enable, configure `node.enabled=true` and optionally `node.policy=["<policy>"]` if you want something other than `lts`.
      
      Closes #1208
  13. Nov 24, 2017
  14. Nov 17, 2017
  15. Nov 08, 2017
  16. Nov 07, 2017
  17. Nov 05, 2017
Loading