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

Update debug to the latest version 🚀 #117

Merged
merged 1 commit into from
Sep 22, 2018
Merged

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Sep 11, 2018

Version 4.0.0 of debug was just published.

Dependency debug
Current Version 3.2.3
Type dependency

The version 4.0.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of debug.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


Release Notes 4.0.0

A long-awaited release to debug is available now: 4.0.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.

This release drops support for Node 4.


Major Changes

Minor Changes

Patches

  • clean up builds: 3ca2331
  • remove needless command aliases in makefile: 9f4f8f5
  • no longer checking for BROWSER=1: 623c08e
  • fix tests: 57cde56
  • clean up makefile: 62822f1
  • fix tests: 833b6f8
  • add .editorconfig: 2d2509e
  • add yarn-error.log to .gitignore: 7e1d5d9
  • Improve usability of Windows notes w/ examples for prompts & npm script (#577): 1ad1e4a
  • Drop usage of chrome.storage (or make the storage backend pluggable): 71d2aa7
  • Detect 'process' package: 225c66f
  • Update ms to 2.1.1 (#539): 22f9932
  • Update .npmignore (#527): a5ca7a2
  • fix colors with supports-color@5: 285dfe1
  • Document enable() (#517): ab5083f
  • refactor to make the common code be a setup function (#507): 7116906
  • Simplify and improve: da51af8
  • use babel-ified distributed source for browsers: b3f8f8e

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 1 commits ahead by 1, behind by 2.

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 🌴

@coveralls
Copy link

Coverage Status

Coverage remained the same at 40.146% when pulling 1c276b7 on greenkeeper/debug-4.0.0 into 07a4954 on master.

greenkeeper bot added a commit that referenced this pull request Sep 12, 2018
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 12, 2018

Version 4.0.1 just got published.

Update to this version instead 🚀

Release Notes 4.0.1

This patch restores browserify functionality as well as keeping the intended functionality with Unpkg.com.

Patches

  • fix browserify and supply alternative unpkg entry point (closes #606): 99c95e3
Commits

The new version differs by 2 commits.

  • 4490cd9 4.0.1
  • 99c95e3 fix browserify and supply alternative unpkg entry point (closes #606)

See the full diff

@bergie bergie merged commit ff16918 into master Sep 22, 2018
@greenkeeper greenkeeper bot deleted the greenkeeper/debug-4.0.0 branch September 22, 2018 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants