build(deps-dev): Bump lint-staged from 15.2.5 to 15.2.6

[dependabot]

Bumps lint-staged from 15.2.5 to 15.2.6.

Release notes

Sourced from lint-staged's releases.

v15.2.6

Patch Changes

• #1433 119adb2 Thanks @​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.

Changelog

Sourced from lint-staged's changelog.

15.2.6

Patch Changes

• #1433 119adb2 Thanks @​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.

Commits

• a91d942 chore(changeset): release
• 119adb2 fix: use native git command to get .git directory
• e0386dc fix: use native git command to get top-level directory for repo
• 6593870 ci: test Node.js versions against current instead of latest dependency
• 6c226c5 ci: add workflow for testing required Node.js semver range
• See full diff in compare view

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)

[relativeci]

#11095 Bundle Size — 361.12KiB (0%).

6cdf60a(current) vs 41b1a0c master#11090(baseline)

Bundle metrics  no changes

	Current #11095	Baseline #11090
Initial JS	319.19KiB	319.19KiB
Initial CSS	41.94KiB	41.94KiB
Cache Invalidation	0%	0%
Chunks	3	3
Assets	4	4
Modules	667	667
Duplicate Modules	0	0
Duplicate Code	0%	0%
Packages	35	35
Duplicate Packages	0	0

Bundle size by type  no changes

	Current #11095	Baseline #11090
JS	319.19KiB	319.19KiB
CSS	41.94KiB	41.94KiB

---

Bundle analysis report Branch dependabot/npm_and_yarn/master/l... Project dashboard

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/memfs@4.2.1	None	+5	7.3 MB	streamich
npm/memory-fs@0.4.1	None	0	13.4 kB	sokra

🚮 Removed packages: npm/ariakit@2.0.0-next.44, npm/autoprefixer@10.4.19, npm/babel-eslint@10.1.0, npm/babel-jest@29.7.0, npm/babel-loader@9.1.3, npm/babel-plugin-preact-require@1.0.0, npm/babel-plugin-react-require@4.0.2, npm/babel-plugin-require-context-hook@1.0.0, npm/boxen@5.1.2

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/fsevents@1.2.13	Install script: install Source: node install.js	packages/webpack-plugin/test/package/package.json

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/fsevents@1.2.13