088279abbd
fix: return shrinkwrapdir to avoid crash ( #1621 )
2018-03-08 15:59:52 +01:00
c2f0a46d9a
feat: npm shrinkwrap
...
Adds support for npm-shrinkwrap.json files.
Closes #67
2018-03-08 09:46:08 +01:00
862998c2b4
fix: don’t validate empty config
2018-03-08 08:00:12 +01:00
ef828be054
refactor: log content before validation
2018-03-08 07:32:09 +01:00
21a5af01c7
fix: add try/catch logging to migrate and validate code
...
This reverts commit 97ea483f7e
2018-03-08 07:28:06 +01:00
47bf45019d
fix: better serialize content fields
2018-03-08 07:22:06 +01:00
97ea483f7e
fix: Revert "fix: add try/catch logging to migrate and validate code"
...
This reverts commit 9b44e34fa7
2018-03-08 07:12:31 +01:00
9b44e34fa7
fix: add try/catch logging to migrate and validate code
2018-03-08 06:02:16 +01:00
7874188cb5
refactor: better debug migrateAndValidate
2018-03-07 15:13:37 +01:00
c3db85c74e
fix: correct setMeta for validatePrs()
2018-03-07 15:06:57 +01:00
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
a2ef094485
feat: support pinned versions in .travis.yml
...
If the existing version was pinned, or if pinVersions=true, then Renovate will use pinned versions for all the new values.
Closes #1605
2018-03-06 22:18:13 +01:00
e29c2d5aca
fix: detect quotation mark in .travis.yml
2018-03-06 22:18:13 +01:00
d9f9e4692f
docs(node): improve documentation clarity ( #1606 )
2018-03-06 21:42:47 +01:00
d237c6c670
feat: add comment to PRs if config validation fails
2018-03-06 20:00:10 +01:00
a186a4b091
chore: downgrade PR log to debug
2018-03-06 19:31:02 +01:00
e7c325e6f0
fix: validate based on branchPrefix, not branchName
2018-03-06 16:12:59 +01:00
453ce13278
fix: Revert "refactor: array concatenation ( #1601 )"
...
This reverts commit dd26a018c5
2018-03-06 15:54:39 +01:00
96835410d8
feat: validate renovate config PRs ( #1602 )
...
feat: validate renovate config PRs
2018-03-06 15:21:17 +01:00
dd26a018c5
refactor: array concatenation ( #1601 )
...
Refactors all instances of .concat() to use array spread operators instead
Closes #1459
2018-03-06 12:34:39 +01:00
4104e81005
Revert "chore: remove unused getPrFiles functions"
...
This reverts commit d5984a3cad
2018-03-06 12:18:35 +01:00
a924ad3715
fix: add package.json > engines > node to “node.js” group
...
This is so that the upgrade is combined with travis and nvm
2018-03-06 11:15:04 +01:00
46e2e95b32
fix: pr dep filter use manager in duplicate key
...
To ensure we list both nvm and engines when upgrading node
2018-03-06 11:14:32 +01:00
621badb964
fix(allow-failure): enabled automerge when allowed failures occur
...
Closes : #1586
Signed-off-by: Adam Moss <adam.moss@bcs.org.uk >
2018-03-05 21:18:51 +01:00
d5984a3cad
chore: remove unused getPrFiles functions
2018-03-05 15:50:34 +01:00
7ca9918c3c
fix: don’t detect disabled managers
2018-03-05 14:56:21 +01:00
e2f067faba
Revert "fix: skip pruning for multiple baseBranches"
...
This reverts commit 81c722473f
2018-03-05 13:53:37 +01:00
3877b87c36
fix: delete branchList if repository has looped
2018-03-05 13:53:04 +01:00
daba8ba560
fix: add travis content filter
2018-03-05 13:50:54 +01:00
81c722473f
fix: skip pruning for multiple baseBranches
2018-03-05 13:19:39 +01:00
7021a073aa
fix: clean up multiple baseBranches correctly
...
Re-enables branch cleanup for multiple baseBranches
2018-03-05 12:27:10 +01:00
3d65e3a48e
fix: disable branch pruning when multiple basebranches in use
2018-03-05 12:12:46 +01:00
6530480410
refactor: simplify detectPackageFiles
2018-03-04 20:03:52 +01:00
80dbeaa563
refactor: use filePattern to detect package files
2018-03-04 16:34:55 +01:00
5e3822d0cc
refactor: use filePattern for each manager
2018-03-04 16:09:12 +01:00
dde5756488
feat: .nvmrc files ( #1582 )
...
Adds initial support for `.nvmrc` renovation. If the existing value is a fully-specified semver version then it will be upgraded, otherwise left alone.
Closes #1270
2018-03-04 15:52:06 +01:00
f398fa19aa
fix: Revert "refactor: improve migration scripts"
...
This reverts commit c6be31543dCloses #1584
2018-03-04 14:36:45 +01:00
74a7242081
fix: node-travis migration
2018-03-04 14:20:04 +01:00
c6be31543d
refactor: improve migration scripts
2018-03-04 07:35:18 +01:00
a2c4ecefda
fix: delete empty errors and warnings from migrated config
2018-03-04 07:12:02 +01:00
dae287b62b
refactor: node-travis definitions ( #1583 )
...
Retains the "node" configuration object but moves enabling/disabling to "travis". Also removes the default `supportPolicy` from config.
2018-03-04 07:08:19 +01:00
33bcbdd91d
fix: add repositoryUrl to travis results
2018-03-03 22:25:27 +01:00
05c8af7e55
fix: add depType to group prBody
2018-03-03 22:25:06 +01:00
faa4cc6171
fix: travis metadata and formatting
...
Updates travis config and logic to use same variables as for other managers. This fixes the onboarding PR.
Fixes #1551
2018-03-03 20:53:54 +01:00
cd9218444d
refactor: move node package lookup to node helper
2018-03-03 17:36:45 +01:00
886a3d05bf
refactor: rename ‘node’ manager to ‘travis’
2018-03-03 15:35:43 +01:00
3c56f8aeb6
refactor: move manager-specific code under lib/manager ( #1573 )
...
Refactors all non-npm code to live inside lib/manager/*
2018-03-03 14:39:39 +01:00
7f9d73a318
feat: allowedVersions
...
A semver range defining allowed versions for dependencies
| name | value |
| ---- | ------ |
| type | string |
Use this - usually within a packageRule - to limit how far to upgrade a dependency. For example, if you wish to upgrade to angular v1.5 but not to `angular` v1.6 or higher, you could defined this to be `<= 1.5` or `< 1.6.0`:
```
"packageRules": [{
"packageNames": ["angular"],
"allowedVersions": "<=1.5"
}]
```
2018-03-03 06:35:11 +01:00
7db4951722
fix: use commonConfig branchPrefix only if set
2018-03-01 21:58:34 +01:00
e9eba859ea
fix: use original branchPrefix when pruning baseBranches
2018-03-01 21:34:27 +01:00
eMerzh