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 node-libs-browser is breaking the build 🚨 #130

Open
greenkeeper bot opened this issue Nov 15, 2017 · 3 comments
Open

An in-range update of node-libs-browser is breaking the build 🚨 #130

greenkeeper bot opened this issue Nov 15, 2017 · 3 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented Nov 15, 2017

Version 2.1.0 of node-libs-browser was just published.

Branch Build failing 🚨
Dependency node-libs-browser
Current Version 2.0.0
Type devDependency

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

node-libs-browser is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 12 commits.

  • 98c49c3 2.1.0
  • ea7a72e Update package.json and package-lock.json
  • 1b67bde Merge pull request #57 from brendo/patch-1
  • 9b3992b Merge branch 'master' into patch-1
  • 53b28da Merge branch 'master' into patch-1
  • 1802afd Merge pull request #56 from mcollina/patch-1
  • d15a6c8 Merge pull request #63 from dignifiedquire/patch-1
  • c0866f5 Merge pull request #71 from bmeurer/patch-1
  • 66da7bd Bump os-browserify dependency to 0.3.0
  • f4880ae bump browserify-zlib to 0.2.0
  • e6ace00 Update https-browserify dependency.
  • 7e37969 Updated string_decoder to v1.0.0

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 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Nov 15, 2017

After pinning to 2.0.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 Jan 17, 2019

Your tests are still failing with this version. Compare changes

Release Notes for v2.2.0
  • Update util to v0.11
  • Update events to v3
Commits

The new version differs by 7 commits.

  • be25189 2.2.0
  • 15758c4 Merge tag 'v2.1.0'
  • 4bdd0d8 Merge pull request #74 from goto-bus-stop/events-2
  • a868380 Merge pull request #80 from goto-bus-stop/util-11
  • aac4d24 Update util to v0.11.0.
  • b91abcb Update events to v3
  • 2b306d0 Update events to v2

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Jun 12, 2019

Your tests are still failing with this version. Compare changes

Release Notes for v2.2.1

Bugfixes

  • mock process will handle args for process.nextTick correctly
  • update path-browserify to 0.0.1 (non-breaking)
  • update vm-browserify to ^1 (licensing issues, non-breaking)
Commits

The new version differs by 10 commits.

  • 214057f 2.2.1
  • fb20a4a Merge pull request #85 from gruns/master
  • fb42a44 add deprecation note
  • c88c6b0 Merge pull request #77 from fahrradflucht/chore/updated-vm-browserify
  • d2c5389 Merge branch 'master' into chore/updated-vm-browserify
  • 97bb2e6 chore: use ^ for vm-browserify dep
  • 6f082c7 Merge pull request #89 from goto-bus-stop/path-0.0.1
  • d1f8983 Update path-browserify to 0.0.1.
  • 34d7d75 Accept arguments to process.nextTick(fn, ...args), just like Node.js's process.nextTick().
  • 1b24f34 chore: upgrade vm-browserify to 1.0.1

See the full diff

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