The version 1.0.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 color-map.
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 98.75% when pulling 53f8cda7a23882ad0688c4bca8f44c55a577d5c8 on greenkeeper/color-map-1.0.0 into 1917cb0d66f22f9b4f687c5925eb32cf924a7279 on master.
Coverage remained the same at 98.75% when pulling 527fa880fe171823c608eed69b5b16b426df4d79 on greenkeeper/color-map-1.0.0 into 5bbb6c48602eee8b984c0cd74a5c675d09fe936a on master.
Coverage remained the same at 98.75% when pulling 527fa880fe171823c608eed69b5b16b426df4d79 on greenkeeper/color-map-1.0.0 into 5bbb6c48602eee8b984c0cd74a5c675d09fe936a on master.
Coverage remained the same at 98.75% when pulling 527fa880fe171823c608eed69b5b16b426df4d79 on greenkeeper/color-map-1.0.0 into 5bbb6c48602eee8b984c0cd74a5c675d09fe936a on master.
Version 1.0.0 of color-map was just published.
The version 1.0.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 color-map.
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.
Release Notes
v1.0.01.0.0 (2018-01-02)
Chores
BREAKING CHANGES
Commits
The new version differs by 7 commits.
ce7a227
chore: update dev dependencies. (#39)
202f5a3
chore: enable semantic-release (#38)
89cd36a
chore: enable wallaby (#37)
af5fb30
chore(package): update rollup to version 0.53.0 (#36)
79c8c9c
chore(package): update ava to version 0.24.0 (#35)
2346d19
chore(package): update rollup to version 0.52.0 (#34)
55daa67
chore(package): update rollup to version 0.51.0 (#33)
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: