chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@mheob/commitlint-config (source)	1.1.1 -> 1.1.2
@mheob/prettier-config (source)	3.2.0 -> 3.3.1
@mheob/tsconfig (source)	2.0.0 -> 2.1.0
@types/node (source)	20.12.8 -> 20.14.9
@vitest/coverage-v8 (source)	1.5.3 -> 1.6.0
cz-git (source)	1.9.1 -> 1.9.3
lint-staged	15.2.2 -> 15.2.7
prettier (source)	3.2.5 -> 3.3.2
rimraf	5.0.5 -> 5.0.7
typescript (source)	5.4.5 -> 5.5.2
vitest (source)	1.5.3 -> 1.6.0

---

Release Notes

mheob/config (@​mheob/commitlint-config)

v1.1.2

Compare Source

Patch Changes

• #​182 (@​mheob): Improve README.md file and add spell checker.

vitest-dev/vitest (@​vitest/coverage-v8)

v1.6.0

Compare Source

   🚀 Features

• Support standalone mode  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/5565 (bdce0)
• Custom "snapshotEnvironment" option  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/5449 (30f72)
• benchmark: Support comparing benchmark result  -  by @​hi-ogawa and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/5398 (f8d3d)
• browser: Allow injecting scripts  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/5656 (21e58)
• reporter: Support includeConsoleOutput and addFileAttribute in junit  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/5659 (2f913)
• ui: Sort items by file name  -  by @​btea in https://github.com/vitest-dev/vitest/issues/5652 (1f726)

   🐞 Bug Fixes

• Keep order of arguments for .each in custom task collectors  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/5640 (7d57c)
• Call resolveId('vitest') after buildStart  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/5646 (f5faf)
• Hash the name of the file when caching  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/5654 (c9e68)
• Don't panic on empty files in node_modules  -  by @​sheremet-va (40c29)
• Use toJSON for error serialization  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/5526 (19a21)
• coverage:
  • Exclude *.test-d.* by default  -  by @​MindfulPol in https://github.com/vitest-dev/vitest/issues/5634 (bfe8a)
  • Apply vite-node's wrapper only to executed files  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/5642 (c9883)
• vm:
  • Support network imports  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/5610 (103a6)

   🏎 Performance

• Improve performance of forks pool  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/5592 (d8304)
• Unnecessary rpc call when coverage is disabled  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/5658 (c5712)

    View changes on GitHub

Zhengqbbb/cz-git (cz-git)

v1.9.3

Compare Source

Bug Fixes

• cli: czg export type can not be used (#​175) (4fe94cf)

v1.9.2

Compare Source

Bug Fixes

• cz-git: incorrect maxSubjectLength on custom scope (#​173) (baa58ae)

okonet/lint-staged (lint-staged)

v15.2.7

Compare Source

Patch Changes

• #​1440 a51be80 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.

v15.2.6

Compare Source

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.

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

prettier/prettier (prettier)

v3.3.2

Compare Source

diff

Fix handlebars path expressions starts with @ (#​16358 by @​Princeyadav05)

{{! Input }}
<div>{{@&#8203;x.y.z}}</div>

{{! Prettier 3.3.1 }}
<div>{{@&#8203;x}}</div>

{{! Prettier 3.3.2 }}
<div>{{@&#8203;x.y.z}}</div>

v3.3.1

Compare Source

diff

Preserve empty lines in front matter (#​16347 by @​fisker)

<!-- Input -->
---
foo:
  - bar1

  - bar2

  - bar3
---
Markdown

<!-- Prettier 3.3.0 -->

---
foo:
  - bar1
  - bar2
  - bar3
---

Markdown

<!-- Prettier 3.3.1 -->
---
foo:
  - bar1

  - bar2

  - bar3
---

Markdown

Preserve explicit language in front matter (#​16348 by @​fisker)

<!-- Input -->
---yaml
title: Hello
slug: home
---

<!-- Prettier 3.3.0 -->
---
title: Hello
slug: home
---

<!-- Prettier 3.3.1 -->
---yaml
title: Hello
slug: home
---

Avoid line breaks in import attributes (#​16349 by @​fisker)

// Input
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

// Prettier 3.3.0
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type:
  "json" };

// Prettier 3.3.1
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

v3.3.0

Compare Source

diff

🔗 Release Notes

isaacs/rimraf (rimraf)

v5.0.7

Compare Source

v5.0.6

Compare Source

Microsoft/TypeScript (typescript)

v5.5.2

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone Europe/Berlin, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[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 an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to full the review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud