Update mongodb to version 2.2.10 🚀 #2714
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
added
the
drew-gross
force-pushed
the
greenkeeper-mongodb-2.2.10
branch
from
a28e990 to
8303a00
Compare
Current coverage is 92.24% (diff: 100%)@@ master #2714 diff @@
==========================================
Files 102 102
Lines 12446 12446
Methods 1559 1559
Messages 0 0
Branches 2039 2039
==========================================
- Hits 11484 11481 -3
- Misses 962 965 +3
Partials 0 0
|
|
@greenkeeperio-bot updated the pull request - view changes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
mongodb just published its new version 2.2.10.
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 ✨
You rock!
🌴
The new version differs by 15 commits .
e9fe643tagged proxy test as ignore for travis461c76eUpdated version and history to V2.2.1064d53eeNODE-811 Added more explicit encodeURIComponent example and explanation393f6b0Minor fixes to how write concern is handled with the 3.4 serverd17978aMerge pull request #1403 from SirR4T/patch-1cb55d63Fix the explanation text.4c38431Merge pull request #1402 from mongodb/greenkeeper-bluebird-3.4.654d0036chore(package): update bluebird to version 3.4.6052b2e3NODE-808 merged PR from valeri and added testcase to index_tests.js8783596Merge pull request #1398 from vkarpov15/patch-6a26fe5ffix(db): don't fall back to insert if 'IndexOptionsConflict' erroreb85233Merge pull request #1393 from mongodb/greenkeeper-mongodb-extended-json-1.7.179ae4ccMerge pull request #1396 from mongodb/greenkeeper-bluebird-3.4.39bf7351chore(package): update bluebird to version 3.4.39940946chore(package): update mongodb-extended-json to version 1.7.1See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade