![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4)
Bumps [debug](https://github.com/debug-js/debug) from 4.1.1 to 4.3.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/debug-js/debug/releases">debug's releases</a>.</em></p> <blockquote> <h2>4.3.4</h2> <h2>What's Changed</h2> <ul> <li>Add section about configuring JS console to show debug messages by <a href="https://github.com/gitname"><code>@gitname</code></a> in <a href="https://redirect.github.com/debug-js/debug/pull/866">debug-js/debug#866</a></li> <li>Replace deprecated String.prototype.substr() by <a href="https://github.com/CommanderRoot"><code>@CommanderRoot</code></a> in <a href="https://redirect.github.com/debug-js/debug/pull/876">debug-js/debug#876</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/gitname"><code>@gitname</code></a> made their first contribution in <a href="https://redirect.github.com/debug-js/debug/pull/866">debug-js/debug#866</a></li> <li><a href="https://github.com/CommanderRoot"><code>@CommanderRoot</code></a> made their first contribution in <a href="https://redirect.github.com/debug-js/debug/pull/876">debug-js/debug#876</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/debug-js/debug/compare/4.3.3...4.3.4">https://github.com/debug-js/debug/compare/4.3.3...4.3.4</a></p> <h2>4.3.3</h2> <h1>Patch Release 4.3.3</h1> <p>This is a documentation-only release. Further, the repository was transferred. Please see notes below.</p> <ul> <li><strong>Migrates repository from <a href="https://github.com/visionmedia/debug">https://github.com/visionmedia/debug</a> to <a href="https://github.com/debug-js/debug">https://github.com/debug-js/debug</a></strong>. Please see notes below as to why this change was made.</li> <li>Updates repository maintainership information</li> <li>Updates the copyright (no license terms change has been made)</li> <li>Removes accidental epizeuxis (<a href="https://redirect.github.com/debug-js/debug/issues/828">#828</a>)</li> <li>Adds README section regarding usage in child procs (<a href="https://redirect.github.com/debug-js/debug/issues/850">#850</a>)</li> </ul> <p>Thank you to <a href="https://github.com/taylor1791"><code>@taylor1791</code></a> and <a href="https://github.com/kristofkalocsai"><code>@kristofkalocsai</code></a> for their contributions.</p> <hr /> <h1>Repository Migration Information</h1> <p>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.</p> <h3>Q: What impact will this have on me?</h3> <p>In most cases, you shouldn't notice any change.</p> <p>The only exception I can think of is if you pull code directly from <a href="https://github.com/visionmedia/debug">https://github.com/visionmedia/debug</a>, e.g. via a <code>"debug": "visionmedia/debug"</code>-type version entry in your package.json - in which case, you should <em>still</em> be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.</p> <h3>Q: What are the security implications of this change?</h3> <p>If you pull code directly from the old URL, you should update the URL to <a href="https://github.com/debug-js/debug">https://github.com/debug-js/debug</a> as soon as possible. The old organization has <em>many</em> 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 (<a href="https://github.com/qix"><code>@qix</code></a>-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.</p> <p>Even in such a case, however, the officially released package on npm (<code>debug</code>) would <em>not</em> be affected. That package is still very much under control (even more than it used to be).</p> <h3>Q: What should I do if I encounter an issue related to the migration?</h3> <p><a href="https://github.com/debug-js/debug/issues?q=label%3Amigration+">Search the issues first</a> to see if someone has already reported it, and <em>then</em> open a new issue if someone has not.</p> <h3>Q: Why was this done as a 'patch' release? Isn't this breaking?</h3> <p>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.</p> <p>Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/debug-js/debug/commit/da66c86c5fd71ef570f36b5b1edfa4472149f1bc"><code>da66c86</code></a> 4.3.4</li> <li><a href="https://github.com/debug-js/debug/commit/9b334123f1331a252bc27c99c33b5c4f199d200f"><code>9b33412</code></a> replace deprecated String.prototype.substr() (<a href="https://redirect.github.com/debug-js/debug/issues/876">#876</a>)</li> <li><a href="https://github.com/debug-js/debug/commit/c0805cc4d3b2c7c987567e99ecaec78840516d7b"><code>c0805cc</code></a> add section about configuring JS console to show debug messages (<a href="https://redirect.github.com/debug-js/debug/issues/866">#866</a>)</li> <li><a href="https://github.com/debug-js/debug/commit/043d3cd17d30af45f71d2beab4ec7abfc9936e9e"><code>043d3cd</code></a> 4.3.3</li> <li><a href="https://github.com/debug-js/debug/commit/4079aae5b5bf1198ecd2e1032609dfd46bec843f"><code>4079aae</code></a> update license and more maintainership information</li> <li><a href="https://github.com/debug-js/debug/commit/19b36c052ab0084f8b1c86d34d3e82190680246a"><code>19b36c0</code></a> update repository location + maintainership information</li> <li><a href="https://github.com/debug-js/debug/commit/f851b00eb006d400e757dca33568773910365519"><code>f851b00</code></a> adds README section regarding usage in child procs (<a href="https://redirect.github.com/debug-js/debug/issues/850">#850</a>)</li> <li><a href="https://github.com/debug-js/debug/commit/d177f2bc36d3b8b8e9b1b006727ef5e04f98eac7"><code>d177f2b</code></a> Remove accidental epizeuxis</li> <li><a href="https://github.com/debug-js/debug/commit/e47f96de3de5921584364b4ac91e2769d22a3b1f"><code>e47f96d</code></a> 4.3.2</li> <li><a href="https://github.com/debug-js/debug/commit/1e9d38c2e6e170abde6cfeaf7b2024d8b456f906"><code>1e9d38c</code></a> cache enabled status per-logger (<a href="https://redirect.github.com/debug-js/debug/issues/799">#799</a>)</li> <li>Additional commits viewable in <a href="https://github.com/debug-js/debug/compare/4.1.1...4.3.4">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~qix">qix</a>, a new releaser for debug since your current version.</p> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 <dependency name> 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/CyberFlameGO/tsconfig-paths/network/alerts). </details>
AI Analysis
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by dependabot[bot] and has received 0 comments.
Add a comment
Comment form would go here