Closed greenkeeper[bot] closed 7 years ago
After pinning to 2.2.12 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
Version 2.2.13 of mongodb just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As mongodb is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/mongodb-js/mongodb-top/builds/181883128)Commits
The new version differs by 11 commits .
adbebca
Updated package, history and installation guide
537a5c4
Expose parserType as property on topology objects
b034c83
NODE-889 Fixed issue where legacy killcursor wire protocol messages would not be sent when APM is enableD
3a88709
force build
d18f58e
run tests against local mongodb
0e1801e
disable containers
16f4547
try travis containers again
7f6f65c
force build
4cfa6c3
All test cases passing for bson-ext
1f7b0ff
integrated the new bson parser and mongodb-core 2.1.0
52f3b3c
Update HISTORY.md
See 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: