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 browserify is breaking the build 🚨 #42

Closed
greenkeeper bot opened this issue Apr 11, 2018 · 2 comments
Closed

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

greenkeeper bot opened this issue Apr 11, 2018 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Apr 11, 2018

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 16.2.0 of browserify was just published.

Branch Build failing 🚨
Dependency browserify
Current Version 16.1.1
Type devDependency

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

browserify 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

Release Notes v16.2.0

update the browser versions of vm-browserify and string_decoder.

string_decoder updates to the Node 8+ API.
vm-browserify replaces an unlicensed dependency by an MIT one.

#1829

Commits

The new version differs by 5 commits.

  • 00cc377 16.2.0
  • 7005b6e Merge pull request #1829 from browserify/deps
  • e333b14 Merge pull request #1827 from browserify/fix-cert
  • 03ffac9 ci: Disable certificate check for very old npm
  • 9345e21 Update string_decoder and vm builtin modules

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
Contributor Author

greenkeeper bot commented Apr 11, 2018

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

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 9, 2018

Version 16.2.1 just got published.

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

Release Notes v16.2.1

Fix relative --external paths on Windows. (@Shingyx)

#1704

Fix tests to work on Windows, and add Appveyor CI for Windows testing.

#1819

Commits

The new version differs by 8 commits.

  • 36d7c9a 16.2.1
  • e34599a Merge pull request #1819 from goto-bus-stop/appveyor
  • 8e7cb87 Skip flaky test on Windows w old Node
  • 3703154 Disable invalid json chars test in node 10
  • e39d609 Skip failing test on old Node on Windows
  • c428f0c Fix external relative paths on Windows
  • c5120b7 Fix tests on Windows.
  • 2d896a9 Try adding appveyor

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

1 participant