Build(deps): bump diff from 4.0.2 to 4.0.4

[dependabot]

Bumps diff from 4.0.2 to 4.0.4.

Commits

• f06f3e4 v4.0.4
• 0179a48 v4.0.3
• 4568cae Backport kpdecker/jsdiff#649
• 4de0ffa Backport kpdecker/jsdiff#647
• See full diff 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 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.

[github-actions]

❌MegaLinter analysis: Error

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ ACTION	actionlint	5		0	0	0.07s
✅ JSON	jsonlint	5		0	0	0.26s
✅ JSON	npm-package-json-lint	yes		no	no	0.51s
✅ JSON	prettier	5		0	0	0.95s
✅ JSON	v8r	5		0	0	7.42s
✅ MARKDOWN	markdownlint	1		0	0	1.22s
✅ REPOSITORY	checkov	yes		no	no	22.02s
✅ REPOSITORY	gitleaks	yes		no	no	1.23s
✅ REPOSITORY	git_diff	yes		no	no	0.07s
❌ REPOSITORY	grype	yes		16	no	47.53s
✅ REPOSITORY	secretlint	yes		no	no	1.02s
✅ REPOSITORY	syft	yes		no	no	8.91s
✅ REPOSITORY	trivy-sbom	yes		no	no	4.64s
✅ REPOSITORY	trufflehog	yes		no	no	30.54s
✅ TYPESCRIPT	prettier	9		0	0	1.05s
✅ YAML	prettier	13		0	0	0.8s
✅ YAML	v8r	13		0	0	8.11s
✅ YAML	yamllint	13		0	0	0.76s

Detailed Issues

❌ REPOSITORY / grype - 16 errors

[0000]  WARN no explicit name and version provided for directory source, deriving artifact ID from the given path (which is not ideal) from=syft
NAME    INSTALLED  FIXED IN          TYPE       VULNERABILITY        SEVERITY  EPSS           RISK   
undici  5.29.0     6.23.0            npm        GHSA-g9mf-h72j-4rw9  Medium    < 0.1% (17th)  < 0.1  
stdlib  go1.23.10  *1.24.8, 1.25.2   go-module  CVE-2025-61723       High      < 0.1% (8th)   < 0.1  
stdlib  go1.23.10  *1.24.8, 1.25.2   go-module  CVE-2025-61725       High      < 0.1% (8th)   < 0.1  
stdlib  go1.23.10  *1.24.8, 1.25.2   go-module  CVE-2025-58185       Medium    < 0.1% (9th)   < 0.1  
stdlib  go1.23.10  *1.24.8, 1.25.2   go-module  CVE-2025-47912       Medium    < 0.1% (9th)   < 0.1  
stdlib  go1.23.10  *1.24.8, 1.25.2   go-module  CVE-2025-58186       Medium    < 0.1% (8th)   < 0.1  
stdlib  go1.23.10  *1.24.8, 1.25.2   go-module  CVE-2025-61724       Medium    < 0.1% (8th)   < 0.1  
stdlib  go1.23.10  *1.24.11, 1.25.5  go-module  CVE-2025-61729       High      < 0.1% (2nd)   < 0.1  
stdlib  go1.23.10  *1.23.12, 1.24.6  go-module  CVE-2025-47907       High      < 0.1% (3rd)   < 0.1  
stdlib  go1.23.10  *1.24.9, 1.25.3   go-module  CVE-2025-58187       High      < 0.1% (2nd)   < 0.1  
stdlib  go1.23.10  *1.24.8, 1.25.2   go-module  CVE-2025-58188       High      < 0.1% (2nd)   < 0.1  
stdlib  go1.23.10  *1.24.8, 1.25.2   go-module  CVE-2025-58189       Medium    < 0.1% (4th)   < 0.1  
stdlib  go1.23.10  *1.23.12, 1.24.6  go-module  CVE-2025-47906       Medium    < 0.1% (2nd)   < 0.1  
stdlib  go1.23.10  *1.24.8, 1.25.2   go-module  CVE-2025-58183       Medium    < 0.1% (2nd)   < 0.1  
stdlib  go1.23.10  *1.23.11, 1.24.5  go-module  CVE-2025-4674        High      < 0.1% (0th)   < 0.1  
stdlib  go1.23.10  *1.24.11, 1.25.5  go-module  CVE-2025-61727       Medium    < 0.1% (0th)   < 0.1
[0047] ERROR discovered vulnerabilities at or above the severity threshold

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@9.3.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,JSON_JSONLINT,JSON_V8R,JSON_PRETTIER,JSON_NPM_PACKAGE_JSON_LINT,MARKDOWN_MARKDOWNLINT,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_GRYPE,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,TYPESCRIPT_PRETTIER,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R