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 debug is breaking the build 🚨 #1500

Closed
greenkeeper bot opened this issue Sep 11, 2018 · 6 comments
Closed

An in-range update of debug is breaking the build 🚨 #1500

greenkeeper bot opened this issue Sep 11, 2018 · 6 comments
Labels

Comments

@greenkeeper
Copy link
Contributor

@greenkeeper greenkeeper bot commented Sep 11, 2018

Version 3.2.0 of debug was just published.

Branch Build failing 🚨
Dependency debug
Current Version 3.1.0
Type dependency

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

debug is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes 3.2.0

A long-awaited release to debug is available now: 3.2.0.

Due to the delay in release and the number of changes made (including bumping dependencies in order to mitigate vulnerabilities), it is highly recommended maintainers update to the latest package version and test thoroughly.


Minor Changes

Patches

Credits

Huge thanks to @DanielRuf, @EirikBirkeland, @KyleStay, @Qix-, @abenhamdine, @alexey-pelykh, @DiegoRBaquero, @febbraro, @kwolfy, and @TooTallNate for their help!

Commits

The new version differs by 25 commits.

There are 25 commits in total.

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 greenkeeper bot added the greenkeeper label Sep 11, 2018
@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

@greenkeeper greenkeeper bot commented Sep 11, 2018

Version 3.2.1 just got published.

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

Release Notes 3.2.1

A quick hotfix to address Browser builds - debug is now compiled down to IE8-compatible code via Babel upon release.

CDNs that honor the "browser": key in package.json should now reflect these changes (previously, they would serve the non-bundled ES6 version).

Patches

  • use babel-ified distributed source for browsers: b3f8f8e
Commits

The new version differs by 2 commits.

  • 84e41d5 3.2.1
  • b3f8f8e use babel-ified distributed source for browsers

See the full diff

@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

@greenkeeper greenkeeper bot commented Sep 11, 2018

After pinning to 3.1.0 your tests are passing again. Downgrade this dependency 📌.

@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

@greenkeeper greenkeeper bot commented Sep 11, 2018

Version 3.2.2 just got published.

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

Commits

The new version differs by 1 commits.

See the full diff

@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

@greenkeeper greenkeeper bot commented Sep 11, 2018

Version 3.2.3 just got published.

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

Commits

The new version differs by 1 commits.

  • 700a010 re-introduce node.js (root file) (ref #603)

See the full diff

@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

@greenkeeper greenkeeper bot commented Oct 8, 2018

  • The dependency debug was updated from 4.0.1 to 4.1.0.

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

Release Notes for 4.1.0

Minor Changes

  • migrate Makefile to npm scripts (4236585)
  • feat: Return namespaces string when invoking disable() (7ef8b41)

Massive thank you to @mblarsen and @outsideris for knocking out two long-awaited changes.

Commits

The new version differs by 6 commits ahead by 6, behind by 2.

  • e30e8fd 4.1.0
  • 7ef8b41 feat: Return namespaces string when invoking disable()
  • 4236585 migrate Makefile to npm scripts
  • 4490cd9 4.0.1
  • 99c95e3 fix browserify and supply alternative unpkg entry point (closes #606)
  • 7fb104b 4.0.0

See the full diff

@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

@greenkeeper greenkeeper bot commented Dec 22, 2018

  • The dependency debug was updated from 4.1.0 to 4.1.1.

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

Commits

The new version differs by 10 commits ahead by 10, behind by 2.

  • 68b4dc8 4.1.1
  • 7571608 remove .coveralls.yaml
  • 57ef085 copy custom logger to namespace extension (fixes #646)
  • d0e498f test: only run coveralls on travis
  • e30e8fd 4.1.0
  • 7ef8b41 feat: Return namespaces string when invoking disable()
  • 4236585 migrate Makefile to npm scripts
  • 4490cd9 4.0.1
  • 99c95e3 fix browserify and supply alternative unpkg entry point (closes #606)
  • 7fb104b 4.0.0

See the full diff

@lock lock bot locked as resolved and limited conversation to collaborators Mar 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.