Giters

fastify / fastify-mongodb

Fastify MongoDB connection plugin

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

An in-range update of mongodb is breaking the build 🚨

greenkeeper opened this issue · comments

commented

The dependency mongodb was updated from 3.2.7 to 3.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mongodb is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Commits

The new version differs by 1878 commits ahead by 1878, behind by 7.

  • 8b3c3b0 chore(release): 3.3.0
  • 0d2018c docs(AutoEncryption): adds documentation for extraOptions
  • 3ecda98 docs(autoEncryption): document that autoEncryption is in beta
  • 814a4cc chore(useUnifiedTopology): add deprecation warning for useUnifiedTopology
  • b7308db test: disable some failing tests for later investigation
  • b23e606 test(transactions): disable invalid pinning test
  • 82a7a6e chore(travis): add 4.2 testing to travis
  • 392f5a6 fix(topology): add new error for retryWrites on MMAPv1
  • 2ef8f2c chore(ci): update evergreen config to test Ubuntu 18.04 on mongodb >= 4.2
  • ae729f8 refactor(change-stream): use AggregateOperation for stream cursor
  • 831968d refactor(cursor): return operation readPreference with priority
  • 1ffe9b7 refactor(client): provide default namespace and read preference
  • 778928f refactor(command): support full response as command op option
  • 6acef6d refactor(find): use FindOperation for finds
  • 0f88582 refactor(cursor): modernize and deduplicate cursor classes

There are 250 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

commented

After pinning to 3.2.7 your tests are passing again. Downgrade this dependency 📌.

commented

This is not a flaky test