This version 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 loopback-connector-ioredis.
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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Coverage remained the same at 87.805% when pulling 69ed5a716bbf72d5dc5496611a839866ee64b445 on greenkeeper-loopback-connector-ioredis-0.2.0 into f8ff4ac635a84755f32518c4d512b7136867e5c8 on master.
Coverage remained the same at 87.805% when pulling 69ed5a716bbf72d5dc5496611a839866ee64b445 on greenkeeper-loopback-connector-ioredis-0.2.0 into f8ff4ac635a84755f32518c4d512b7136867e5c8 on master.
Coverage remained the same at 87.805% when pulling 69ed5a716bbf72d5dc5496611a839866ee64b445 on greenkeeper-loopback-connector-ioredis-0.2.0 into f8ff4ac635a84755f32518c4d512b7136867e5c8 on master.
Hello lovely humans,
loopback-connector-ioredis just published its new version 0.2.0.
This version 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 loopback-connector-ioredis. 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 18 commits .
8016422
Release 0.2.0
bda7993
Reimplemented based on
loopback-connector-nosql
.5bf1585
Release 0.1.5
fb362f8
Updated modules.
3900350
Lock the ID before really create, and conflict if there's a lock already.
dd2d406
Release 0.1.4
74a7bd5
Coding style changes: use
Promise.bind()
, changemodel
tomodelName
.7cfeef4
Fixed tests for
find()
with no arguments.f5c1b24
Release 0.1.3
032c28f
Merge pull request #6 from BoLaMN/master
d243e9e
add .find()
a7711ea
Release 0.1.2
a4d9796
Merge pull request #5 from Wiredcraft/removeEs6-shim
6400b70
remove es6-shim, remove CI build for node 0.12
31ec835
Release 0.1.1
There are 18 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade