Bump diff from 5.1.0 to 5.2.0 in the npm_and_yarn group across 1 directory

[dependabot]

Bumps the npm_and_yarn group with 1 update in the / directory: diff.

Updates diff from 5.1.0 to 5.2.0

Changelog

Sourced from diff's changelog.

v5.2.0

Commits

• #411 Big performance improvement. Previously an O(n) array-copying operation inside the innermost loop of jsdiff's base diffing code increased the overall worst-case time complexity of computing a diff from O(n²) to O(n³). This is now fixed, bringing the worst-case time complexity down to what it theoretically should be for a Myers diff implementation.
• #448 Performance improvement. Diagonals whose furthest-reaching D-path would go off the edge of the edit graph are now skipped, rather than being pointlessly considered as called for by the original Myers diff algorithm. This dramatically speeds up computing diffs where the new text just appends or truncates content at the end of the old text.
• #351 Importing from the lib folder - e.g. require("diff/lib/diff/word.js") - will work again now. This had been broken for users on the latest version of Node since Node 17.5.0, which changed how Node interprets the exports property in jsdiff's package.json file.
• #344 diffLines, createTwoFilesPatch, and other patch-creation methods now take an optional stripTrailingCr: true option which causes Windows-style \r\n line endings to be replaced with Unix-style \n line endings before calculating the diff, just like GNU diff's --strip-trailing-cr flag.
• #451 Added diff.formatPatch.
• #450 Added diff.reversePatch.
• #478 Added timeout option.

Commits

• 370a9df 5.2.0 release (#483)
• a2f726a Add myself to the list of maintainers (#482)
• dfc6fe4 Add examples to docs of creating and applying patches (importantly including ...
• b5d1cfa Modify node_example.js to support showing added/deleted spaces (#479)
• 533893d Add timeout option (#478)
• 1f1ec96 Replace broken link to Myers's paper in the README with a working one (#476)
• 707fccc Add note to README about setting context to Infinity or MAX_SAFE_INTEGER. (...
• 1c7514c Fix mistake in README (#471)
• ca8718c Bump follow-redirects from 1.14.8 to 1.15.4 (#470)
• 25a14af Migrate to DABH's fork of colors (#469)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by explodingcabbage, a new releaser for diff 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

Note

Updates dependency versions and lockfile.

• Bumps diff from 5.1.0 to 5.2.0 in yarn.lock
• Upgrades glob from ^8.0.3 to ^9.0.0 in tools/validate/package.json, with corresponding yarn.lock changes (e.g., minimatch@^8, minipass@^4, path-scurry)

^{Written by Cursor Bugbot for commit 5767572. This will update automatically on new commits. Configure here.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​glob@​8.0.3 ⏵ 9.3.5	+1		+1	+38

View full report

[socket-security]

Caution

MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Publisher changed: npm diff is now published by explodingcabbage instead of kpdecker New Author: explodingcabbage Previous Author: kpdecker From: ? → npm/remark-parse@10.0.1 → npm/remark-gfm@3.0.1 → npm/diff@5.2.0 ℹ Read more on: This package | This alert | What is new author? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/diff@5.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential code anomaly (AI signal): npm glob is 100.0% likely to have a medium risk anomaly Notes: The analyzed fragment appears to be a standard, non-malicious implementation of a filesystem glob/walker utility. There is no evidence of data exfiltration, hidden backdoors, or malicious behavior within this isolated fragment. The design aligns with expected patterns for building glob matchers and providing sync/async streaming interfaces, assuming the surrounding package maintains secure patterns and proper access controls. Confidence: 1.00 Severity: 0.60 From: tools/validate/package.json → npm/glob@9.3.5 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/glob@9.3.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[cursor]

Glob v9 upgrade breaks promisify-based usage pattern

High Severity

The glob dependency is being upgraded from v8 to v9, which is a breaking change. Glob v9 switched from a callback-based API to a native Promise-based API. The existing code in tools/validate/src/main.ts uses promisify(glob) which works with glob v8's callback API, but will not work correctly with glob v9. When promisify is called on an already-async function, the resulting wrapper never resolves because the callback is never invoked. This will cause the validation tool to hang or fail entirely.