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.
This version was pushed to npm by heroku-front-end, a new releaser for heroku since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/brownplt/code.pyret.org/network/alerts).
Bumps debug to 4.3.4 and updates ancestor dependency heroku. These dependencies need to be updated together.
Updates
debugfrom 4.1.1 to 4.3.4Release notes
Sourced from debug's releases.
... (truncated)
Commits
da66c864.3.49b33412replace deprecated String.prototype.substr() (#876)c0805ccadd section about configuring JS console to show debug messages (#866)043d3cd4.3.34079aaeupdate license and more maintainership information19b36c0update repository location + maintainership informationf851b00adds README section regarding usage in child procs (#850)d177f2bRemove accidental epizeuxise47f96d4.3.21e9d38ccache enabled status per-logger (#799)Maintainer changes
This version was pushed to npm by qix, a new releaser for debug since your current version.
Updates
herokufrom 7.69.1 to 8.11.5Release notes
Sourced from heroku's releases.
... (truncated)
Changelog
Sourced from heroku's changelog.
... (truncated)
Commits
df5cd30release v8.11.5 (#2850)c5128a7chore(auth): update warning copy (#2842)49c52d0fix: add quotation marks around public key in sign/deb script (#2849)c8fa033chore: update opentelemetry/instrumentation to 0.50.0 and improve integration...501330brelease v8.11.4 (#2811)697df38chore(telemetry): add environment variable to optionally disable telemetry (#...1541dfcrelease v8.11.3 (#2807)33f8aacfix(authorizations): surface api warnings in temporary fix (#2804)381575fBump heroku-color (#2797)6a1a730release v8.11.2 (#2793)Maintainer changes
This version was pushed to npm by heroku-front-end, a new releaser for heroku since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show