The version 0.54.0 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 100.0% when pulling f125ec01f7be7986902fcf8eec7cc30e3f944f39 on greenkeeper/rollup-0.54.0 into 3dc1eafc56156b95ad4cd02eb9310af8da365335 on master.
Coverage remained the same at 100.0% when pulling f125ec01f7be7986902fcf8eec7cc30e3f944f39 on greenkeeper/rollup-0.54.0 into 3dc1eafc56156b95ad4cd02eb9310af8da365335 on master.
Version 0.54.0 of rollup was just published.
The version 0.54.0 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 64 commits.
0a988e0
0.54.0
db0a0fc
Update changelog
d6df037
Merge branch 'kellyselden-unused' into release-0.54.0
d6aea92
Merge branch 'KingHenne-fix-ts-issues' into release-0.54.0
46f273f
Merge branch 'kellyselden-line-collapse' into release-0.54.0
bd45dea
0.53.4
a61840b
Update changelog
238e822
Update changelog
d665a43
chore(build): add
stripInternal
and only emit types fromnode
entry point3fc7662
chore: clean up internal types and install missing
@types
57a527c
Quick fix to enable tree-shaking babel-helpers again.
01d38e8
* Use enum for node types
8270798
fix: use chalk.supportColors rather than isTTY
8ce5592
* Refactor ExecutionPathOptions types
856ff0f
docs: typescripts is always written as a single word
There are 64 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: