The version 0.52.1 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of rollup.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 99.891% when pulling 4a8303521629e6335a5cad3c0b95ed5dc7668f65 on greenkeeper/rollup-0.52.1 into 52ee46b84ee79b2ccd1928975295e99dea253eed on master.
Coverage remained the same at 99.891% when pulling e4af8c2eb4c99b9351471e17076086f18ea8255c on greenkeeper/rollup-0.52.1 into 52ee46b84ee79b2ccd1928975295e99dea253eed on master.
Coverage remained the same at 99.891% when pulling e4af8c2eb4c99b9351471e17076086f18ea8255c on greenkeeper/rollup-0.52.1 into 52ee46b84ee79b2ccd1928975295e99dea253eed on master.
Coverage remained the same at 99.891% when pulling 37794284e002cc6a34be7f41b76d6d72a07a1b4a on greenkeeper/rollup-0.52.1 into 52ee46b84ee79b2ccd1928975295e99dea253eed on master.
Coverage remained the same at 99.891% when pulling 37794284e002cc6a34be7f41b76d6d72a07a1b4a on greenkeeper/rollup-0.52.1 into 52ee46b84ee79b2ccd1928975295e99dea253eed on master.
Coverage remained the same at 99.891% when pulling 37794284e002cc6a34be7f41b76d6d72a07a1b4a on greenkeeper/rollup-0.52.1 into 52ee46b84ee79b2ccd1928975295e99dea253eed on master.
Version 0.52.1 of rollup was just published.
The version 0.52.1 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of rollup.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 43 commits.
d0ba36b
Also lint bin folder
d74be7a
0.52.1
b19762d
Update changelog
a44f75b
Merge pull request #1774 from LostKobrakai/master
eadf109
Merge pull request #1768 from tivac/cli-multiple-envs
e63b11e
Merge pull request #1759 from haraldrudell/master
d92f072
Merge pull request #1747 from adrianheine/master
6e6fcc2
Let process.stdin actually trigger it’s end event
fe4bb17
feat: let --environment be specified multiple times
bcfa1bb
Update changelog
675aabb
Merge pull request #1765 from rollup/improve-some-error-messages
030eef7
* Improve deprecation warnings for some options
24231ce
0.52.0
d2dd8d9
Update changelog
4f5f848
Merge branch 'release-0.52'
There are 43 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: