An in-range update of debug is breaking the build π¨
Opened this issue Β· 4 comments
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
- β ci/circleci: test: Your tests failed on CircleCI (Details).
Release Notes
3.2.0A 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
- bump vulnerable packages: 853853f
- Fix nwjs support (#569): 207a6a2
- add instance extends feature (#524): e43e5fe
- Add TVMLKit support (#579): 02b9ea9
Patches
- move to XO (closes #397): ba8a424
- 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
- add Node.js 10, remove Node.js 4 (#583): 05b0ceb
- 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
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.
dec4b15
3.2.0
3ca2331
clean up builds
9f4f8f5
remove needless command aliases in makefile
623c08e
no longer checking for BROWSER=1
57cde56
fix tests
62822f1
clean up makefile
833b6f8
fix tests
ba8a424
move to XO (closes #397)
2d2509e
add .editorconfig
853853f
bump vulnerable packages
7e1d5d9
add yarn-error.log to .gitignore
e43e5fe
add instance extends feature (#524)
207a6a2
Fix nwjs support (#569)
05b0ceb
add Node.js 10, remove Node.js 4 (#583)
02b9ea9
Add TVMLKit support (#579)
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 π΄
After pinning to 3.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 3.2.1 just got published.
Your tests are still failing with this version. Compare the changes π¨
Release Notes
3.2.1A 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
Version 3.2.2 just got published.
Your tests are still failing with this version. Compare the changes π¨
Version 3.2.3 just got published.
Your tests are still failing with this version. Compare the changes π¨