renovate/test
Rhys Arkins 308ed432db
feat: upgradeInRange (#1608)
Upgrade ranges to latest version even if latest version satisfies existing range.

| name    | value   |
| ------- | ------- |
| type    | boolean |
| default | false   |

By default, Renovate assumes that if you are using ranges then it's because you want them to be wide/open. As such, Renovate won't deliberately "narrow" the range by increasing the semver value inside.

For example, if your `package.json` specifies a value for `left-pad` of `^1.0.0` and the latest version on npmjs is `1.2.0`, then Renovate won't change anything. If instead you'd prefer to be updated to `^1.2.0` in cases like this, then set `upgradeInRange` to `true` in your Renovate config.

This feature supports simple caret (`^`) and tilde (`~`) ranges only, like `^1.0.0` and `~1.0.0`. It is not compatible with `pinVersions=true`.

Closes #1607
2018-03-07 07:41:10 +01:00
..
_fixtures feat: parse CHANGELOG.md in source repositories (#1491) 2018-02-06 18:53:36 +01:00
config fix: Revert "refactor: improve migration scripts" 2018-03-04 14:36:45 +01:00
datasource refactor: move docker registry to datasource 2018-02-27 10:28:31 +01:00
logger fix: refactor logger addStream and depType logging (#1117) 2017-11-08 09:59:32 +01:00
manager feat: support pinned versions in .travis.yml 2018-03-06 22:18:13 +01:00
platform Revert "chore: remove unused getPrFiles functions" 2018-03-06 12:18:35 +01:00
workers feat: upgradeInRange (#1608) 2018-03-07 07:41:10 +01:00
.eslintrc.js refactor: remove config.api and use platform dispatcher (#1114) 2017-11-07 11:46:10 +01:00
chai.js Refactor config 2017-01-20 14:03:18 +01:00
globals.js refactor: use global logger (#1116) 2017-11-08 06:44:03 +01:00
renovate.spec.js refactor: use platform global (#1115) 2017-11-07 13:31:34 +01:00
website-docs.spec.js docs: correlate website configuration documentation with source code 2017-12-26 05:40:14 +01:00