Skip to content
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

Open
greenkeeper bot opened this issue Jul 13, 2017 · 8 comments
Open

An in-range update of pouchdb is breaking the build 🚨 #21

greenkeeper bot opened this issue Jul 13, 2017 · 8 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented Jul 13, 2017

Version 6.3.0 of pouchdb just got published.

Branch Build failing 🚨
Dependency pouchdb
Current Version 6.2.0
Type devDependency

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
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 6.3.0

Full changelog

New features

  • Stefan du Fresne: #6565 - Replacing uuid function with node-uuid
  • Alex Anderson: #5490 - Include doc ID in conflict errors
  • Hadrien de Cuzey: #6308 - Add option to disable checkpoints
  • Alex Anderson: #6529 - Include doc ID in 404 (not_found) errors for IDB adapter
  • Samuel Zhang: #5832 - Force update
  • Garren Smith: #6452 - Add support for use_index in pouchdb-find
  • Garren Smith: #6495 - Add explain endpoint for pouchdb-find
  • Garren Smith: #6443 - Add $allMatch support for pouchdb-find

Bug fixes and performance improvements

  • Will Holley: #6510 - validate _changes timing parameters
  • Alex Anderson: #6545 - throw Errors, not Strings
  • Adrien Vergé: #6504 - fix possible "EventEmitter memory leak detected"
  • Stéphane Alnet: #5981 - ensure close() doesn't block destroyed events
  • Garren Smith: #6472 - pouchdb-find: don't return design docs with all_docs index
  • Will Holley: #6458 - consistent error handling for mapreduce
Not 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 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Jul 13, 2017

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.

@greenkeeper
Copy link
Author

greenkeeper bot commented Jul 13, 2017

Version 6.3.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes 6.3.1

Fixes bad package dependencies in 6.3.1

@greenkeeper
Copy link
Author

greenkeeper bot commented Jul 14, 2017

Version 6.3.3 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

@greenkeeper
Copy link
Author

greenkeeper bot commented Jul 15, 2017

Version 6.3.4 just got published.

Your tests are still failing with this version. Compare the changes 🚨

@greenkeeper
Copy link
Author

greenkeeper bot commented Dec 17, 2017

Version 6.4.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes 6.4.0

I'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 allDocs() and query()

#6230 - Dale Harders added support for passing update_seq: true to either allDocs() or query() or will return the current databases update_seq.

Add pending pending property

#5710 - Dale also added support for passing through the pending property newly implemented in CouchDB that reports the number of pending documents to replicate.

Use a single transaction for allDocs with keys requests

#6854 - @nename0 implemented an optimisation to use a single transaction in indexedDB and WebSQL for allDocs requests with keys. This seen a huge 8X speedup in Chrome and 2X in Firefox.

Add support to store cookies on Node.js

#6814 - @ptitjes fixed HTTP requests in Node.JS to ensure they use a cookie jar.

Full changelog

Bug fixes and performance improvements

  • #6443 - Support seq_interval for changes and use during replication
  • #6890 - Preventing SecurityError on Firefox
  • #6855 - Cache bust GET requests on IE11
  • #6736 - Fix {binary: true} in db.get() with open_revs and HTTP adapter
  • #6730 - Fix single-sided checkpointing
  • #6766 - Prevent field lookup on undefined value
  • #6793 - Fix incompatibility with pouchdb-wrappers

Get in touch

As always, we welcome feedback from the community and would love to hear what you think of this release as well as PouchDB's future direction. Please don't hesitate to file issues or get in touch. And of course, a big thanks to all of our new and existing contributors!

@greenkeeper
Copy link
Author

greenkeeper bot commented Dec 18, 2017

Version 6.4.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

@greenkeeper
Copy link
Author

greenkeeper bot commented Jan 24, 2018

Version 6.4.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

@greenkeeper
Copy link
Author

greenkeeper bot commented Feb 2, 2018

Version 6.4.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants