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 mongodb.
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 104 commits .
7c1846cupdated mongodb-core to 2.0.9 and updated version to 2.2.7
fef9899Merge pull request #1391 from mongodb/greenkeeper-update-all
a63de1bNODE-799 Allow passing in servername for TLS connections for SNI support.
9380a91If only a single mongos is provided in the seedlist, fix issue where it would be assigned as single standalone server instead of mongos topology (Issue #130).
Hello lovely humans,
mongodb just published its new version 2.2.7.
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 mongodb. 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 104 commits .
7c1846cupdated mongodb-core to 2.0.9 and updated version to 2.2.7fef9899Merge pull request #1391 from mongodb/greenkeeper-update-alla63de1bNODE-799 Allow passing in servername for TLS connections for SNI support.c475758Added create collection view test68ae28aNODE-797 Added test coverage showing woring createCollection for views4dd8997chore(package): update dependencies9380a91If only a single mongos is provided in the seedlist, fix issue where it would be assigned as single standalone server instead of mongos topology (Issue #130).46404e2minor cleanup9dd5f7bremoved any test files from git and npmea8736eremoved non expected files81a21e7minor test fixes, updated version to 2.2.6 and mongodb-core to 2.0.88d5b50cminor test fixesb066c03test fixb88dbd4Handle store execution based on readPreferenceb6b8290Merge pull request #1388 from danielsan/patch-1There are 104 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade