Skip to content

Bump debug and mocha - #62

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Open

Bump debug and mocha#62
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/debug-and-mocha-4.3.4

Conversation

@dependabot

@dependabotdependabotBot commented on behalf of githubJan 11, 2023

Copy link
Copy Markdown

Bumps debug to 4.3.4 and updates ancestor dependency mocha. These dependencies need to be updated together.

Updates debug from 2.2.0 to 4.3.4

Release notes

Sourced from debug's releases.

4.3.4

What's Changed

New Contributors

Full Changelog: debug-js/debug@4.3.3...4.3.4

4.3.3

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.

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by qix, a new releaser for debug since your current version.


Updates mocha from 2.5.3 to 10.2.0

Release notes

Sourced from mocha's releases.

v10.2.0

10.2.0 / 2022-12-11

🎉 Enhancements

  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)

🐛 Fixes

📖 Documentation

v10.1.0

10.1.0 / 2022-10-16

🎉 Enhancements

🔩 Other

v10.0.0

10.0.0 / 2022-05-01

💥 Breaking Changes

🔩 Other

... (truncated)

Changelog

Sourced from mocha's changelog.

10.2.0 / 2022-12-11

🎉 Enhancements

  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)

🐛 Fixes

📖 Documentation

10.1.0 / 2022-10-16

🎉 Enhancements

🔩 Other

10.0.0 / 2022-05-01

💥 Breaking Changes

🔩 Other

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by juergba, a new releaser for mocha 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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
Bump debug and mocha
b968f3f
Bumps [debug](https://github.com/debug-js/debug) to 4.3.4 and updates ancestor dependency [mocha](https://github.com/mochajs/mocha). These dependencies need to be updated together.
Updates `debug` from 2.2.0 to 4.3.4
- [Release notes](https://github.com/debug-js/debug/releases)
- [Commits](debug-js/debug@2.2.0...4.3.4)
Updates `mocha` from 2.5.3 to 10.2.0
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md)
- [Commits](mochajs/mocha@v2.5.3...v10.2.0)
---
updated-dependencies:
- dependency-name: debug
dependency-type: indirect
- dependency-name: mocha
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
@dependabotdependabotBot added the dependencies Pull requests that update a dependency file label Jan 11, 2023
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependenciesPull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Bump debug and mocha by dependabot[bot] · Pull Request #62 · Trumid/node-quickfix · GitHub
Skip to content
Bump debug and mocha - #62
Open
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Open
Bump debug and mocha#62
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Conversation
@dependabot
@dependabotdependabotBot
commented
on behalf of githubJan 11, 2023

Copy link


Copy Markdown

Bumps debug to 4.3.4 and updates ancestor dependency mocha. These dependencies need to be updated together.
Updates debug from 2.2.0 to 4.3.4
Release notes
Sourced from debug's releases.
4.3.4
What's Changed
New Contributors
Full Changelog: debug-js/debug@4.3.3...4.3.4
4.3.3
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.
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by qix, a new releaser for debug since your current version.

Updates mocha from 2.5.3 to 10.2.0
Release notes
Sourced from mocha's releases.
v10.2.0
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
v10.1.0
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
v10.0.0
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Changelog
Sourced from mocha's changelog.
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by juergba, a new releaser for mocha 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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
@dependabot
Bump debug and mocha
b968f3f
Bumps [debug](https://github.com/debug-js/debug) to 4.3.4 and updates ancestor dependency [mocha](https://github.com/mochajs/mocha). These dependencies need to be updated together.
Updates `debug` from 2.2.0 to 4.3.4
- [Release notes](https://github.com/debug-js/debug/releases)
- [Commits](debug-js/debug@2.2.0...4.3.4)
Updates `mocha` from 2.5.3 to 10.2.0
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md)
- [Commits](mochajs/mocha@v2.5.3...v10.2.0)
---
updated-dependencies:
- dependency-name: debug
dependency-type: indirect
- dependency-name: mocha
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
@dependabotdependabotBot
added
the 
dependencies
Pull requests that update a dependency file
label
Jan 11, 2023
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

dependenciesPull requests that update a dependency file

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Bump debug and mocha by dependabot[bot] · Pull Request #62 · Trumid/node-quickfix · GitHub
Skip to content
Bump debug and mocha - #62
Open
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Open
Bump debug and mocha#62
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Conversation
@dependabot
@dependabotdependabotBot
commented
on behalf of githubJan 11, 2023

Copy link


Copy Markdown

Bumps debug to 4.3.4 and updates ancestor dependency mocha. These dependencies need to be updated together.
Updates debug from 2.2.0 to 4.3.4
Release notes
Sourced from debug's releases.
4.3.4
What's Changed
New Contributors
Full Changelog: debug-js/debug@4.3.3...4.3.4
4.3.3
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.
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by qix, a new releaser for debug since your current version.

Updates mocha from 2.5.3 to 10.2.0
Release notes
Sourced from mocha's releases.
v10.2.0
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
v10.1.0
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
v10.0.0
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Changelog
Sourced from mocha's changelog.
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by juergba, a new releaser for mocha 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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
@dependabot
Bump debug and mocha
b968f3f
Bumps [debug](https://github.com/debug-js/debug) to 4.3.4 and updates ancestor dependency [mocha](https://github.com/mochajs/mocha). These dependencies need to be updated together.
Updates `debug` from 2.2.0 to 4.3.4
- [Release notes](https://github.com/debug-js/debug/releases)
- [Commits](debug-js/debug@2.2.0...4.3.4)
Updates `mocha` from 2.5.3 to 10.2.0
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md)
- [Commits](mochajs/mocha@v2.5.3...v10.2.0)
---
updated-dependencies:
- dependency-name: debug
dependency-type: indirect
- dependency-name: mocha
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
@dependabotdependabotBot
added
the 
dependencies
Pull requests that update a dependency file
label
Jan 11, 2023
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

dependenciesPull requests that update a dependency file

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Bump debug and mocha by dependabot[bot] · Pull Request #62 · Trumid/node-quickfix · GitHub
Skip to content
Bump debug and mocha - #62
Open
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Open
Bump debug and mocha#62
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Conversation
@dependabot
@dependabotdependabotBot
commented
on behalf of githubJan 11, 2023

Copy link


Copy Markdown

Bumps debug to 4.3.4 and updates ancestor dependency mocha. These dependencies need to be updated together.
Updates debug from 2.2.0 to 4.3.4
Release notes
Sourced from debug's releases.
4.3.4
What's Changed
New Contributors
Full Changelog: debug-js/debug@4.3.3...4.3.4
4.3.3
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.
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by qix, a new releaser for debug since your current version.

Updates mocha from 2.5.3 to 10.2.0
Release notes
Sourced from mocha's releases.
v10.2.0
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
v10.1.0
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
v10.0.0
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Changelog
Sourced from mocha's changelog.
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by juergba, a new releaser for mocha 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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
@dependabot
Bump debug and mocha
b968f3f
Bumps [debug](https://github.com/debug-js/debug) to 4.3.4 and updates ancestor dependency [mocha](https://github.com/mochajs/mocha). These dependencies need to be updated together.
Updates `debug` from 2.2.0 to 4.3.4
- [Release notes](https://github.com/debug-js/debug/releases)
- [Commits](debug-js/debug@2.2.0...4.3.4)
Updates `mocha` from 2.5.3 to 10.2.0
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md)
- [Commits](mochajs/mocha@v2.5.3...v10.2.0)
---
updated-dependencies:
- dependency-name: debug
dependency-type: indirect
- dependency-name: mocha
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
@dependabotdependabotBot
added
the 
dependencies
Pull requests that update a dependency file
label
Jan 11, 2023
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

dependenciesPull requests that update a dependency file

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
Bump debug and mocha by dependabot[bot] · Pull Request #62 · Trumid/node-quickfix · GitHub
Skip to content
Bump debug and mocha - #62
Open
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Open
Bump debug and mocha#62
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Conversation
@dependabot
@dependabotdependabotBot
commented
on behalf of githubJan 11, 2023

Copy link


Copy Markdown

Bumps debug to 4.3.4 and updates ancestor dependency mocha. These dependencies need to be updated together.
Updates debug from 2.2.0 to 4.3.4
Release notes
Sourced from debug's releases.
4.3.4
What's Changed
New Contributors
Full Changelog: debug-js/debug@4.3.3...4.3.4
4.3.3
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.
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by qix, a new releaser for debug since your current version.

Updates mocha from 2.5.3 to 10.2.0
Release notes
Sourced from mocha's releases.
v10.2.0
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
v10.1.0
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
v10.0.0
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Changelog
Sourced from mocha's changelog.
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by juergba, a new releaser for mocha 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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
@dependabot
Bump debug and mocha
b968f3f
Bumps [debug](https://github.com/debug-js/debug) to 4.3.4 and updates ancestor dependency [mocha](https://github.com/mochajs/mocha). These dependencies need to be updated together.
Updates `debug` from 2.2.0 to 4.3.4
- [Release notes](https://github.com/debug-js/debug/releases)
- [Commits](debug-js/debug@2.2.0...4.3.4)
Updates `mocha` from 2.5.3 to 10.2.0
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md)
- [Commits](mochajs/mocha@v2.5.3...v10.2.0)
---
updated-dependencies:
- dependency-name: debug
dependency-type: indirect
- dependency-name: mocha
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
@dependabotdependabotBot
added
the 
dependencies
Pull requests that update a dependency file
label
Jan 11, 2023
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

dependenciesPull requests that update a dependency file

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Bump debug and mocha by dependabot[bot] · Pull Request #62 · Trumid/node-quickfix · GitHub
Skip to content
Bump debug and mocha - #62
Open
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Open
Bump debug and mocha#62
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Conversation
@dependabot
@dependabotdependabotBot
commented
on behalf of githubJan 11, 2023

Copy link


Copy Markdown

Bumps debug to 4.3.4 and updates ancestor dependency mocha. These dependencies need to be updated together.
Updates debug from 2.2.0 to 4.3.4
Release notes
Sourced from debug's releases.
4.3.4
What's Changed
New Contributors
Full Changelog: debug-js/debug@4.3.3...4.3.4
4.3.3
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.
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by qix, a new releaser for debug since your current version.

Updates mocha from 2.5.3 to 10.2.0
Release notes
Sourced from mocha's releases.
v10.2.0
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
v10.1.0
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
v10.0.0
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Changelog
Sourced from mocha's changelog.
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by juergba, a new releaser for mocha 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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
@dependabot
Bump debug and mocha
b968f3f
Bumps [debug](https://github.com/debug-js/debug) to 4.3.4 and updates ancestor dependency [mocha](https://github.com/mochajs/mocha). These dependencies need to be updated together.
Updates `debug` from 2.2.0 to 4.3.4
- [Release notes](https://github.com/debug-js/debug/releases)
- [Commits](debug-js/debug@2.2.0...4.3.4)
Updates `mocha` from 2.5.3 to 10.2.0
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md)
- [Commits](mochajs/mocha@v2.5.3...v10.2.0)
---
updated-dependencies:
- dependency-name: debug
dependency-type: indirect
- dependency-name: mocha
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
@dependabotdependabotBot
added
the 
dependencies
Pull requests that update a dependency file
label
Jan 11, 2023
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

dependenciesPull requests that update a dependency file

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Bump debug and mocha by dependabot[bot] · Pull Request #62 · Trumid/node-quickfix · GitHub
Skip to content
Bump debug and mocha - #62
Open
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Open
Bump debug and mocha#62
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Conversation
@dependabot
@dependabotdependabotBot
commented
on behalf of githubJan 11, 2023

Copy link


Copy Markdown

Bumps debug to 4.3.4 and updates ancestor dependency mocha. These dependencies need to be updated together.
Updates debug from 2.2.0 to 4.3.4
Release notes
Sourced from debug's releases.
4.3.4
What's Changed
New Contributors
Full Changelog: debug-js/debug@4.3.3...4.3.4
4.3.3
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.
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by qix, a new releaser for debug since your current version.

Updates mocha from 2.5.3 to 10.2.0
Release notes
Sourced from mocha's releases.
v10.2.0
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
v10.1.0
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
v10.0.0
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Changelog
Sourced from mocha's changelog.
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by juergba, a new releaser for mocha 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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
@dependabot
Bump debug and mocha
b968f3f
Bumps [debug](https://github.com/debug-js/debug) to 4.3.4 and updates ancestor dependency [mocha](https://github.com/mochajs/mocha). These dependencies need to be updated together.
Updates `debug` from 2.2.0 to 4.3.4
- [Release notes](https://github.com/debug-js/debug/releases)
- [Commits](debug-js/debug@2.2.0...4.3.4)
Updates `mocha` from 2.5.3 to 10.2.0
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md)
- [Commits](mochajs/mocha@v2.5.3...v10.2.0)
---
updated-dependencies:
- dependency-name: debug
dependency-type: indirect
- dependency-name: mocha
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
@dependabotdependabotBot
added
the 
dependencies
Pull requests that update a dependency file
label
Jan 11, 2023
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

dependenciesPull requests that update a dependency file

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
Bump debug and mocha by dependabot[bot] · Pull Request #62 · Trumid/node-quickfix · GitHub
Skip to content
Bump debug and mocha - #62
Open
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Open
Bump debug and mocha#62
dependabot[bot] wants to merge 1 commit into
masterfrom 
dependabot/npm_and_yarn/debug-and-mocha-4.3.4
Conversation
@dependabot
@dependabotdependabotBot
commented
on behalf of githubJan 11, 2023

Copy link


Copy Markdown

Bumps debug to 4.3.4 and updates ancestor dependency mocha. These dependencies need to be updated together.
Updates debug from 2.2.0 to 4.3.4
Release notes
Sourced from debug's releases.
4.3.4
What's Changed
New Contributors
Full Changelog: debug-js/debug@4.3.3...4.3.4
4.3.3
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.
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by qix, a new releaser for debug since your current version.

Updates mocha from 2.5.3 to 10.2.0
Release notes
Sourced from mocha's releases.
v10.2.0
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
v10.1.0
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
v10.0.0
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Changelog
Sourced from mocha's changelog.
10.2.0 / 2022-12-11
🎉 Enhancements
  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)
🐛 Fixes
📖 Documentation
10.1.0 / 2022-10-16
🎉 Enhancements
🔩 Other
10.0.0 / 2022-05-01
💥 Breaking Changes
🔩 Other
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by juergba, a new releaser for mocha 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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
@dependabot
Bump debug and mocha
b968f3f
Bumps [debug](https://github.com/debug-js/debug) to 4.3.4 and updates ancestor dependency [mocha](https://github.com/mochajs/mocha). These dependencies need to be updated together.
Updates `debug` from 2.2.0 to 4.3.4
- [Release notes](https://github.com/debug-js/debug/releases)
- [Commits](debug-js/debug@2.2.0...4.3.4)
Updates `mocha` from 2.5.3 to 10.2.0
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md)
- [Commits](mochajs/mocha@v2.5.3...v10.2.0)
---
updated-dependencies:
- dependency-name: debug
dependency-type: indirect
- dependency-name: mocha
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
@dependabotdependabotBot
added
the 
dependencies
Pull requests that update a dependency file
label
Jan 11, 2023
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

dependenciesPull requests that update a dependency file

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants