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.

Sign up for GitHub

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

Jump to bottom

Update dependency debug to v4 #12

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update dependency debug to v4 #12

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 27, 2018 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
debug 3.2.6 -> 4.3.7 age adoption passing confidence

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

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.

  • 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 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.
  • 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.
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

  • Caches enabled statuses on a per-logger basis to speed up .enabled checks (#​799)

Thank you @​omg!

v4.3.1

Compare Source

Patch release 4.3.1

v4.3.0

Compare Source

Minor release

  • Deprecated debugInstance.destroy(). Future major versions will not have this method; please remove it from your codebases as it currently does nothing.
  • Fixed quoted percent sign
  • Fixed memory leak within debug instances that are created dynamically

v4.2.0

Compare Source

Minor Release

  • 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 console.debug in the browser only when it is available (#​600)
  • Copied custom logger to namespace extension (#​646)
  • Added issue and pull request templates
  • Added "engines" key to package.json
  • Added ability to control selectColor (#​747)
  • Updated dependencies
  • Marked supports-color as an optional peer dependency

v4.1.1

Compare Source

This backport fixes a bug in coveralls configuration as well as the .extend() function.

Patches

v4.1.0

Compare Source

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.

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
Minor Changes
Patches
Credits

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

v3.2.7

Compare Source

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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants