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).
greenkeeper[bot]
commented
7 years ago
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.isCheckingis now a property (as described in README). It was implemented as function beforeBREAKING CHANGE:
connectionStatus.okdoes not return false if a connection error was persisted before untilconnectionStatus.readyresolvedBREAKING CHANGE:
new ConnectionStatus(options):options.cache.timeoutis nowoptions.cacheTimeout(5f54be45)
Commits
The new version differs by 7 commits .
5f54be4feat: drop localStorage usage7d76539test: drop localStorage usagec10e178chore(package): -lie, +async-get-set-store17d8188docs(README):connectionStatus.ready2a48115chore(package): -humble-localstorage857cc64docs(README): add.isCheckingto API list16236b0new code coverage status URLSee 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: