chore(deps): update dependency @vitest/eslint-plugin to v1.1.16

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vitest/eslint-plugin	1.1.15 -> 1.1.16

---

Release Notes

vitest-dev/eslint-plugin-vitest (@​vitest/eslint-plugin)

v1.1.16

Compare Source

What's Changed

• Change jest.mock → vi.mock in rule message by @​FloEdelmann in https://github.com/vitest-dev/eslint-plugin-vitest/pull/590

New Contributors

• @​FloEdelmann made their first contribution in https://github.com/vitest-dev/eslint-plugin-vitest/pull/590

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.15...v1.1.16

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

Summary by Sourcery

Chores:

• Update @vitest/eslint-plugin dependency from version 1.1.15 to 1.1.16.

[sourcery-ai]

Reviewer's Guide by Sourcery

This is a minor dependency update PR that upgrades @vitest/eslint-plugin from version 1.1.15 to 1.1.16. The update includes a small change in the rule message, replacing 'jest.mock' with 'vi.mock'.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Update @vitest/eslint-plugin dependency version	Bump version from 1.1.15 to 1.1.16 in package.json Update corresponding version in pnpm-lock.yaml Update package resolution hash in pnpm-lock.yaml	package.json pnpm-lock.yaml

Possibly linked issues

• Dependency Dashboard #1: The PR updates @vitest/eslint-plugin, which is listed in the issue's dependency dashboard.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@vitest/[email protected]	Transitive: environment, filesystem	+33	3.01 MB	veritemm

🚮 Removed packages: npm/@vitest/[email protected]

View full report↗︎

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud