chore(deps): update dependency lint-staged to v15

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
lint-staged	14.0.1 -> 15.2.5

---

Release Notes

okonet/lint-staged (lint-staged)

v15.2.5

Compare Source

Patch Changes

• #​1424 31a1f95 Thanks @​iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.

• #​1423 91abea0 Thanks @​iiroj! - Improve error logging when failing to read or parse a configuration file

• #​1424 ee43f15 Thanks @​iiroj! - Upgrade [email protected]

v15.2.4

Compare Source

Patch Changes

• 4f4537a Thanks @​iiroj! - Fix release issue with previous version; update dependencies

v15.2.2

Compare Source

Patch Changes

• #​1391 fdcdad4 Thanks @​iiroj! - Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.

v15.2.1

Compare Source

Patch Changes

• #​1387 e4023f6 Thanks @​iiroj! - Ignore stdin of spawned commands so that they don't get stuck waiting. Until now, lint-staged has used the default settings to spawn linter commands. This means the stdin of the spawned commands has accepted input, and essentially gotten stuck waiting. Now the stdin is ignored and commands will no longer get stuck. If you relied on this behavior, please open a new issue and describe how; the behavior has not been intended.

v15.2.0

Compare Source

Minor Changes

• #​1371 f3378be Thanks @​iiroj! - Using the --no-stash flag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag --no-hide-partially-staged that is automatically enabled when --no-stash is used.

Patch Changes

• #​1362 17bc480 Thanks @​antonk52! - update [email protected]

• #​1368 7c55ca9 Thanks @​iiroj! - Update most dependencies

• #​1368 777d4e9 Thanks @​iiroj! - To improve performance, only use lilconfig when searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.

• #​1373 85eb0dd Thanks @​iiroj! - When determining git directory, use fs.realpath() only for symlinks. It looks like fs.realpath() changes some Windows mapped network filepaths unexpectedly, causing issues.

v15.1.0

Compare Source

Minor Changes

• #​1344 0423311 Thanks @​danielbayley! - Add support for loading configuration from package.yaml and package.yml files, supported by pnpm.

Patch Changes

• #​1355 105d901 Thanks @​iiroj! - Suppress some warnings when using the "--quiet" flag

v15.0.2

Compare Source

Patch Changes

• #​1339 8e82364 Thanks @​iiroj! - Update dependencies, including listr2@​7.0.2 to fix an upstream issue affecting lint-staged.

v15.0.1

Compare Source

Patch Changes

• #​1217 d2e6f8b Thanks @​louneskmt! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead.

v15.0.0

Compare Source

Major Changes

• #​1322 66b93aa Thanks @​iiroj! - Require at least Node.js 18.12.0

  This release drops support for Node.js 16, which is EOL after 2023-09-11.
  Please upgrade your Node.js to the latest version.

  Additionally, all dependencies have been updated to their latest versions.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
new-web-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 25, 2024 0:28am

[changeset-bot]

⚠️ No Changeset found

Latest commit: d3685d1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: Leftover TODOs in the code should be handled.
• Apply: All new business logic should have corresponding unit tests in the tests/ directory.
• Apply: Any clearly inefficient or repeated code should be optimized or refactored.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@babel/[email protected]	environment	0	24.1 kB	nicolo-ribaudo
npm/@babel/[email protected]	environment, filesystem, unsafe	+2	877 kB	nicolo-ribaudo
npm/@babel/[email protected]	unsafe	+5	292 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	+4	831 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	+2	82.7 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	+4	243 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	+1	31 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	21.7 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	7.04 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	55 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	63.8 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	158 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	14.1 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	10.7 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	858 kB	nicolo-ribaudo
npm/@babel/[email protected]	environment	+7	105 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	2.53 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	+2	46.4 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	65 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	23.6 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	+2	88.2 kB	nicolo-ribaudo
npm/@babel/[email protected]	environment Transitive: unsafe	+82	1.81 MB	nicolo-ribaudo
npm/@babel/[email protected]	None	+5	211 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	69 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	+1	674 kB	nicolo-ribaudo
npm/@babel/[email protected]	environment	0	2.41 MB	nicolo-ribaudo
npm/@docusaurus/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+142	18.9 MB	slorber
npm/@docusaurus/[email protected]	environment Transitive: eval, filesystem, shell, unsafe	+115	13.2 MB	slorber
npm/@mdx-js/[email protected]	None	0	15.5 kB	johno
npm/@svgr/[email protected]	None	0	5.01 kB	neoziro
npm/@svgr/[email protected]	None	0	3.71 kB	neoziro
npm/@svgr/[email protected]	Transitive: environment, filesystem, shell, unsafe	+27	4.74 MB	neoziro
npm/@types/[email protected]	None	+4	4 MB	types
npm/@types/[email protected]	None	+4	3.96 MB	types
npm/@types/[email protected]	None	0	3.78 kB	types
npm/@types/[email protected]	None	+5	1.61 MB	types
npm/@types/[email protected]	None	+5	1.63 MB	types
npm/@types/[email protected]	None	+2	3.95 MB	types
npm/@types/[email protected]	None	0	8.56 kB	types
npm/@webassemblyjs/[email protected]	None	+5	341 kB	xtuc
npm/@webassemblyjs/[email protected]	None	+7	329 kB	xtuc
npm/[email protected]	None	+2	241 kB	dougwilson
npm/[email protected]	eval	+1	1.05 MB	esp
npm/[email protected]	Transitive: network	+14	516 kB	shortcuts
npm/[email protected]	None	+3	66.1 kB	nexdrew
npm/[email protected]	environment	+1	285 kB	ai
npm/[email protected]	environment, filesystem	+1	2.12 MB	ai
npm/[email protected]	environment, filesystem	+4	281 kB	paulmillr
npm/[email protected]	environment, filesystem, network	+1	1.3 MB	jakub.pawlowicz
npm/[email protected]	None	0	8.46 kB	lukeed
npm/[email protected]	None	0	114 kB	omgovich
npm/[email protected]	None	0	685 kB	zloirock
npm/[email protected]	unsafe	0	1.19 MB	lahmatiy
npm/[email protected]	Transitive: filesystem	+4	203 kB	ludovicofischer
npm/[email protected]	None	0	75.3 kB	feedic
npm/[email protected]	network	+1	191 kB	feedic
npm/[email protected]	None	+2	180 kB	ljharb
npm/[email protected]	filesystem	0	31.2 kB	stuk
npm/[email protected]	Transitive: network	+2	520 kB	bigfootjon
npm/[email protected]	Transitive: environment	+6	367 kB	evilebottnawi
npm/[email protected]	network	0	28.6 kB	rubenverborgh
npm/[email protected]	Transitive: environment, filesystem, shell	+3	389 kB	sibiraj-s
npm/[email protected]	None	0	5.94 kB	sindresorhus
npm/[email protected]	None	0	10 kB	evilebottnawi
npm/[email protected]	None	0	9.3 kB	isaacs
npm/[email protected]	None	0	5.01 kB	wooorm
npm/[email protected]	filesystem	0	3.01 kB	sindresorhus
npm/[email protected]	None	0	10.4 kB	isaacs
npm/[email protected]	None	0	2.46 kB	sindresorhus
npm/[email protected]	filesystem	0	10 kB	sindresorhus

🚮 Removed packages: npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@trivago/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@typescript-eslint/[email protected], npm/@typescript-eslint/[email protected], npm/@vitejs/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 10 minutes (more than 100, code: "api-deployments-free-per-day").

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 2 hours (more than 100, code: "api-deployments-free-per-day").

[coderabbitai]

Important

Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[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/[email protected]	Install script: postinstall Source: node -e "try{require('./postinstall')}catch(e){}"	website/package.json
Install scripts	npm/[email protected]	Install script: postinstall Source: node -e "try{require('./postinstall')}catch(e){}"	website/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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]