daviddias / webcrypto

WebCryptoAPI polyfil to work in Node.js in the Browser (so that you don't have to be concerned about moving crypto code between a browser and server side app)
MIT License
24 stars 6 forks source link

An in-range update of crypto-browserify is breaking the build 🚨 #11

Open greenkeeper[bot] opened 7 years ago

greenkeeper[bot] commented 7 years ago

Version 3.11.1 of crypto-browserify just got published.

Branch Build failing 🚨
Dependency crypto-browserify
Current Version 3.11.0
Type dependency

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

crypto-browserify is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/diasdavid/webcrypto/builds/252426187?utm_source=github_status&utm_medium=notification) - ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/diasdavid/webcrypto/15?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)

Commits

The new version differs by 4 commits.

  • acd8789 3.11.1
  • cc6d57e more explicit exports
  • 6cb4e9d crypto.constants are missing #159 (#164)
  • eea13e5 add privateEncrypt/publicDecrypt to README

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:

greenkeeper[bot] commented 7 years ago

After pinning to 3.11.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 6 years ago

Version 3.12.0 just got published.

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