-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of pouchdb is breaking the build 🚨 #21
Comments
After pinning to 6.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 6.3.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notes6.3.1Fixes bad package dependencies in 6.3.1 |
Version 6.3.3 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 |
Version 6.3.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 6.4.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notes6.4.0I'm happy to announce the release of PouchDB 6.4.0, bringing in a number of important features and fixes. For a full changelog from 6.3.0 to 6.4.0 please see the releases page. Some of the highlights: Add update_seq option to
|
Version 6.4.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 6.4.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 6.4.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 6.3.0 of pouchdb just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As pouchdb 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 💪
Status Details
Release Notes
6.3.0Full changelog
New features
Bug fixes and performance improvements
close()
doesn't blockdestroyed
eventsall_docs
indexNot sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: