The version 0.13.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 johnny-five.
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 91ba1b296df9bc3ac6361b20adc0d22c0882bec9 on greenkeeper/johnny-five-0.13.1 into 1cb09b917316f7f7e66fb6b0b8b47c842609295f on master.
Coverage remained the same at 100.0% when pulling 91ba1b296df9bc3ac6361b20adc0d22c0882bec9 on greenkeeper/johnny-five-0.13.1 into 1cb09b917316f7f7e66fb6b0b8b47c842609295f on master.
Version 0.13.1 of johnny-five was just published.
The version 0.13.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 johnny-five.
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 52 commits.
6fa7fae
v0.14.0
0069ab2
Gyro: add MPU6050 and BNO055 devices resolution
e99b14c
Examples: add lsm303c program to tpl/programs.json and regenerate examples list
59bcf34
LSM303C IMU Extra unit tests
578d6af
LSM303C IMU Unit Tests
3f0940b
LSM303C IMU
9a817cd
Hygrometer: add SI7020 resolution and test
df0e70b
Hygrometer: add comment on resolution for TH02 device
904b79d
Hygrometer: add DHT_I2C_NANO_BACKPACK resolution without test
376184a
Hygrometer: add resolution comment on SHT31D
toRelativeHumidity
functionfd0cd0f
Hygrometer: add HIH6130 resolution test
5ae4d0a
Hygrometer: add HTU21D resolution and test
fea5f63
Hygrometer: add test for resolution of SHT31D device
e0ab43c
Accelerometer: whitespace removal
b4f8c1c
Merge branch 'master' of https://github.com/abythell/johnny-five into abythell-master
There are 52 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: