The version 4.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of @hoodie/connection-status.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 4.0.0 of @hoodie/connection-status just got published.
The version 4.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of @hoodie/connection-status. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v4.0.04.0.0 (2016-12-23)
Features
Breaking Changes
connectionStatus.isChecking
is now a property (as described in README). It was implemented as function beforeBREAKING CHANGE:
connectionStatus.ok
does not return false if a connection error was persisted before untilconnectionStatus.ready
resolvedBREAKING CHANGE:
new ConnectionStatus(options)
:options.cache.timeout
is nowoptions.cacheTimeout
(5f54be45)
Commits
The new version differs by 7 commits .
5f54be4
feat: drop localStorage usage
7d76539
test: drop localStorage usage
c10e178
chore(package): -lie, +async-get-set-store
17d8188
docs(README):
connectionStatus.ready
2a48115
chore(package): -humble-localstorage
857cc64
docs(README): add
.isChecking
to API list16236b0
new code coverage status URL
See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: