Update mongodb to version 2.2.20 🚀 #3352
Closed
Conversation
This file contains 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
|
@greenkeeperio-bot updated the pull request - view changes |
|
@acinader I bevlieve I found the reason of the errors with latest mongodb versions. We were setting back the schemas local cache to {} before the promise resolves, multiple subsequent calls would probably race into it, making it empty. |
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.20.
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 94 commits .
25b2fcaUpdated mongodb-core to 2.1.5 to include bson 1.0.4 and bson-ext 1.0.4 due to Buffer.from being broken in early node 4.x versions. Updated driver to V2.2.20825214aMerge pull request #1452 from ovvn/2.2c847e45Merge pull request #1450 from aurium/patch-1de05643Merge pull request #1460 from vkarpov15/patch-1e411de7Merge pull request #1461 from jeffycyang/2.21a3c7f5Merge pull request #1462 from steveren/DOCS-9742c43dc20DOCS-9742: fix aggregation example6a28429Fix typo in test commentsfa43d82docs(collection): document ordered option for insertManyae67052fix corrupt npm releasef89bed0Updated mongodb-core to 2.1.4 to fix bson ObjectId toString issue with utils.inspect messing with toString parameters in node 6. Updated version to 2.2.182bb9a7bTest fixes and upgraded topology manager8f768efupdated createCollection doc options and linked to create command897dabcMade some tests more robustbcaf5c7moved test to generator test case fileThere are 94 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade