Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
~2.6.9
->~4.3.0
Release Notes
debug-js/debug (debug)
v4.3.7
Compare Source
What's Changed
Full Changelog: debug-js/debug@4.3.6...4.3.7
v4.3.6
Compare Source
What's Changed
New Contributors
Full Changelog: debug-js/debug@4.3.5...4.3.6
v4.3.5
Compare Source
Patch
cac39b1
Fix/debug depth (#926)Thank you @calvintwr for the fix.
v4.3.4
Compare Source
What's Changed
New Contributors
Full Changelog: debug-js/debug@4.3.3...4.3.4
v4.3.3
Compare Source
Patch Release 4.3.3
This is a documentation-only release. Further, the repository was transferred. Please see notes below.
Thank you to @taylor1791 and @kristofkalocsai for their contributions.
Repository Migration Information
I've formatted this as a FAQ, please feel free to open an issue for any additional question and I'll add the response here.
Q: What impact will this have on me?
In most cases, you shouldn't notice any change.
The only exception I can think of is if you pull code directly from https://github.com/visionmedia/debug, e.g. via a
"debug": "visionmedia/debug"
-type version entry in your package.json - in which case, you should still be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.Q: What are the security implications of this change?
If you pull code directly from the old URL, you should update the URL to https://github.com/debug-js/debug as soon as possible. The old organization has many approved owners and thus a new repository could (in theory) be created at the old URL, circumventing Github's automatic redirect that is in place now and serving malicious code. I (@qix-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.
Even in such a case, however, the officially released package on npm (
debug
) would not be affected. That package is still very much under control (even more than it used to be).Q: What should I do if I encounter an issue related to the migration?
Search the issues first to see if someone has already reported it, and then open a new issue if someone has not.
Q: Why was this done as a 'patch' release? Isn't this breaking?
No, it shouldn't be breaking. The package on npm shouldn't be affected (aside from this patch release) and any references to the old repository should automatically redirect.
Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.
I understand there are a lot of edge cases so please open issues as needed so I can assist in any way necessary.
Q: Why was the repository transferred?
I'll just list them off in no particular order.
debug
ecosystem intends to grow beyond a single package, and since new packages could not be created in the old org (nor did it make sense for them to live there), a new org made the most sense - especially from a security point of view.Q: Was this approved?
Yes.[archive]
Q: Do I need to worry about another migration sometime in the future?
No.
v4.3.2
Compare Source
Patch release 4.3.2
.enabled
checks (#799)Thank you @omg!
v4.3.1
Compare Source
Patch release 4.3.1
v4.3.0
Compare Source
Minor release
debugInstance.destroy()
. Future major versions will not have this method; please remove it from your codebases as it currently does nothing.v4.2.0
Compare Source
Minor Release
console.debug
in the browser only when it is available (#600)"engines"
key to package.jsonselectColor
(#747)supports-color
as an optional peer dependencyv4.1.1
Compare Source
This backport fixes a bug in coveralls configuration as well as the
.extend()
function.Patches
d0e498f
)57ef085
)v4.1.0
Compare Source
Minor Changes
4236585
)7ef8b41
)Massive thank you to @mblarsen and @outsideris for knocking out two long-awaited changes.
v4.0.1
Compare Source
v4.0.0
Compare Source
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 and 5 in alignment with the Node.js LTS Release Schedule.
Major Changes
ba8a424
05b0ceb
Minor Changes
853853f
207a6a2
e43e5fe
02b9ea9
Patches
3ca2331
9f4f8f5
623c08e
57cde56
62822f1
833b6f8
2d2509e
7e1d5d9
1ad1e4a
chrome.storage
(or make the storage backend pluggable):71d2aa7
225c66f
22f9932
a5ca7a2
supports-color@5
:285dfe1
enable()
(#517):ab5083f
7116906
da51af8
b3f8f8e
Credits
Huge thanks to @DanielRuf, @EirikBirkeland, @KyleStay, @Qix-, @abenhamdine, @alexey-pelykh, @DiegoRBaquero, @febbraro, @kwolfy, and @TooTallNate for their help!
v3.2.7
Compare Source
v3.2.6
Compare Source
v3.2.5
Compare Source
v3.2.4
Compare Source
v3.2.3
Compare Source
v3.2.2
Compare Source
This release mitigated the breaking changes introduced in
3.2.0
where ES6 features were being used on users of Node 4, causing crashes upon inclusion.It employed a temporary Babel pass on the entire codebase in lieu of a hard reversion (so this version is, effectively, a backport of the fixes and features ultimately introduced in
4.0.0
).v3.2.1
Compare Source
v3.2.0
Compare Source
This release was intended to be the next release of Debug but introduced breaking changes that were overlooked at the time of release. As such it has been deprecated on npm and should not be used.
This release, along with
3.2.1
, were subsequently released together as4.0.0
(a major bump). You can review the included changes in that release's details.v3.1.0
Compare Source
Minor Changes
e7e568a
component.json
:47747f3
bdb7e01
DEBUG_HIDE_DATE
env var: #486Patches
daf1a7c
7cd9e53
fdfa0f5
%o
formatter: #504Credits
Huge thanks to @amejiarosario and @zhuangya for their help!
v3.0.1
Compare Source
v3.0.0
Compare Source
Featuring pretty new colors!
Major Changes
DEBUG_FD
: #406Date#toISOString()
instead toDate#toUTCString()
when output is not a TTY: #418enabled()
updates existing debug instances: #440Minor Changes
destroy()
function: #440enabled
flag: #465826fd94
87880f6
31f3343
25eb545
8b5c438
f178d86
Patches
d2dd80a
Credits
Huge thanks to @gtjoseph, @timruffles and @FantasticFiasco for their help!
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.