[Snyk] Upgrade debug from 3.2.7 to 4.3.4 #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade debug from 3.2.7 to 4.3.4. See this package in npm: https://www.npmjs.com/package/debug See this project in Snyk: https://app.snyk.io/org/pt/project/f959ad9b-94ec-4bed-a330-6609348f03e1?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade debug from 3.2.7 to 4.3.4.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Warning: This is a major version upgrade, and may be a breaking change.
Release notes
Package name: debug
-
4.3.4 - 2022-03-17
- Add section about configuring JS console to show debug messages by @ gitname in #866
- Replace deprecated String.prototype.substr() by @ CommanderRoot in #876
- @ gitname made their first contribution in #866
- @ CommanderRoot made their first contribution in #876
-
4.3.3 - 2021-11-27
- Migrates repository from https://github.com/visionmedia/debug to https://github.com/debug-js/debug. Please see notes below as to why this change was made.
- Updates repository maintainership information
- Updates the copyright (no license terms change has been made)
- Removes accidental epizeuxis (#828)
- Adds README section regarding usage in child procs (#850)
- The old organization was defunct and abandoned.
- I was not an owner of the old organization and thus could not ban the non-trivial amount of spam users or the few truly abusive users from the org. This hindered my ability to properly maintain this package.
- The
- The old org has way, way too many approved members with push access, for which there was nothing I could do. This presented a pretty sizable security risk given that many packages in recent years have fallen victim to backdoors and the like due to lax security access.
-
4.3.2 - 2020-12-09
- Caches enabled statuses on a per-logger basis to speed up
-
4.3.1 - 2020-11-19
- Fixes a ReDOS regression (#458) - see #797 for details.
-
4.3.0 - 2020-09-19
- Deprecated
- Fixed quoted percent sign
- Fixed memory leak within debug instances that are created dynamically
-
4.2.0 - 2020-05-19
- Replaced phantomJS with chrome backend for browser tests
- Deprecated and later removed Changelog.md in lieu of releases page
- Removed bower.json (#602)
- Removed .eslintrc (since we've switched to XO)
- Removed .coveralls.yml
- Removed the build system that was in place for various alternate package managers
- Removed the examples folder (#650)
- Switched to
- Copied custom logger to namespace extension (#646)
- Added issue and pull request templates
- Added
- Added ability to control
- Updated dependencies
- Marked
-
4.1.1 - 2018-12-22
- test: only run coveralls on travis (#663, #664, d0e498f)
- copy custom logger to namespace extension (#646, 57ef085)
-
4.1.0 - 2018-10-08
- migrate Makefile to npm scripts (4236585)
- feat: Return namespaces string when invoking disable() (7ef8b41)
-
4.0.1 - 2018-09-11
-
4.0.0 - 2018-09-11
-
3.2.7 - 2020-11-19
from debug GitHub release notesWhat's Changed
New Contributors
Full Changelog: 4.3.3...4.3.4
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.
debugecosystem 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.
Patch release 4.3.2
.enabledchecks (#799)Thank you @ omg!
Patch release 4.3.1
Minor release
debugInstance.destroy(). Future major versions will not have this method; please remove it from your codebases as it currently does nothing.Minor Release
console.debugin the browser only when it is available (#600)"engines"key to package.jsonselectColor(#747)supports-coloras an optional peer dependencyThis backport fixes a bug in coveralls configuration as well as the
.extend()function.Patches
Minor Changes
Massive thank you to @ mblarsen and @ outsideris for knocking out two long-awaited changes.
3.2.7
Commit messages
Package name: debug
read-pkg-upoverpkg-up. import-js/eslint-plugin-import#680)Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs