fix(deps): update dependency @vitest/eslint-plugin to v1.1.36

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vitest/eslint-plugin	1.0.1 -> 1.1.36

---

Release Notes

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

v1.1.36

Compare Source

Bug Fixes

• consistent-test-filename: match allTestPattern against full file path (#​674) (97dcb0f)

v1.1.35

Compare Source

Bug Fixes

• peer deps (18fc2c7)

v1.1.34

Compare Source

v1.1.33

Compare Source

v1.1.32

Compare Source

v1.1.31

Compare Source

Bug Fixes

• require-mock-type-parameters: fixed checking of type annotation (#​661) (20a56a7)

v1.1.30

Compare Source

v1.1.29

Compare Source

Bug Fixes

• linter (#​659) (02c5330)
• remove conflict with another rule (#​657) (d81da70)

What's Changed

• fix: remove conflict with another rule by @​veritem in https://github.com/vitest-dev/eslint-plugin-vitest/pull/657
• Add chai global by @​silverwind in https://github.com/vitest-dev/eslint-plugin-vitest/pull/658
• fix: linter by @​veritem in https://github.com/vitest-dev/eslint-plugin-vitest/pull/659

New Contributors

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

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.28...v1.1.29

v1.1.28

Compare Source

Bug Fixes

• remove the module-sync condition (#​656) (68d2f76)

v1.1.27

Compare Source

Features

• added the require-mock-type-parameters rule (#​651) (5674c25)

What's Changed

• docs(prefer-strict-boolean-matchers): added documentation for the rule by @​marekdedic in https://github.com/vitest-dev/eslint-plugin-vitest/pull/653
• feat: added the require-mock-type-parameters rule by @​marekdedic in https://github.com/vitest-dev/eslint-plugin-vitest/pull/651

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.26...v1.1.27

v1.1.26

Compare Source

Features

• added the prefer-strict-boolean-matchers rule (#​650) (4d86836)

What's Changed

• fix: various build issues by @​aryaemami59 in https://github.com/vitest-dev/eslint-plugin-vitest/pull/641
• feat: added the prefer-strict-boolean-matchers rule by @​marekdedic in https://github.com/vitest-dev/eslint-plugin-vitest/pull/650
• chore: remove duplicate message id by @​yasuaki640 in https://github.com/vitest-dev/eslint-plugin-vitest/pull/652

New Contributors

• @​marekdedic made their first contribution in https://github.com/vitest-dev/eslint-plugin-vitest/pull/650
• @​yasuaki640 made their first contribution in https://github.com/vitest-dev/eslint-plugin-vitest/pull/652

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.25...v1.1.26

v1.1.25

Compare Source

Bug Fixes

• consistent-test-it: Remove duplicate imports inside the import statement (#​638) (0ae4289)

v1.1.24

Compare Source

Bug Fixes

• fix types (#​632) (b7b4f0f)

v1.1.23

Compare Source

Bug Fixes

• make rule message punctuation more consistent and address some typos (#​628) (31cae3b)

What's Changed

• fix: make rule message punctuation more consistent and address some typos by @​G-Rath in https://github.com/vitest-dev/eslint-plugin-vitest/pull/628
• chore: avoid nullish config type by @​ST-DDT in https://github.com/vitest-dev/eslint-plugin-vitest/pull/629

New Contributors

• @​G-Rath made their first contribution in https://github.com/vitest-dev/eslint-plugin-vitest/pull/628
• @​ST-DDT made their first contribution in https://github.com/vitest-dev/eslint-plugin-vitest/pull/629

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.22...v1.1.23

v1.1.22

Compare Source

Bug Fixes

• valid-title false positives when test.extend is used (#​584) (9c2670a)

v1.1.21

Compare Source

Bug Fixes

• fix types (1476da0)

Performance Improvements

• only build regexp ones for detecting expectations (#​608) (448650c)

What's Changed

• perf: only build regexp once for detecting expectations by @​ghusse in https://github.com/vitest-dev/eslint-plugin-vitest/pull/608
• Refactor tsconfig for Stricter Type-Safe Settings by @​y-hsgw in https://github.com/vitest-dev/eslint-plugin-vitest/pull/605
• chore(deps-dev): bump unbuild from 2.0.0 to 3.0.1 by @​dependabot in https://github.com/vitest-dev/eslint-plugin-vitest/pull/609
• chore(deps-dev): bump @​types/node from 20.17.10 to 22.10.2 by @​dependabot in https://github.com/vitest-dev/eslint-plugin-vitest/pull/610
• chore(deps-dev): bump bumpp from 9.9.1 to 9.9.2 by @​dependabot in https://github.com/vitest-dev/eslint-plugin-vitest/pull/611
• chore(deps-dev): bump @​typescript-eslint/parser from 8.0.0 to 8.18.2 by @​dependabot in https://github.com/vitest-dev/eslint-plugin-vitest/pull/612
• chore(deps-dev): bump vitest from 1.6.0 to 2.1.8 by @​dependabot in https://github.com/vitest-dev/eslint-plugin-vitest/pull/613
• chore(deps-dev): bump eslint-doc-generator from 1.7.1 to 2.0.2 by @​dependabot in https://github.com/vitest-dev/eslint-plugin-vitest/pull/614
• fix false postive issues by @​veritem in https://github.com/vitest-dev/eslint-plugin-vitest/pull/617
• make build work by @​veritem in https://github.com/vitest-dev/eslint-plugin-vitest/pull/618
• chore: improve ci by @​veritem in https://github.com/vitest-dev/eslint-plugin-vitest/pull/619
• Chore/ci by @​veritem in https://github.com/vitest-dev/eslint-plugin-vitest/pull/620
• Feat/test extend by @​veritem in https://github.com/vitest-dev/eslint-plugin-vitest/pull/621

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.20...v1.1.21

v1.1.20

Compare Source

Bug Fixes

• detect expectations in chains with underscores (#​607) (d31fdb7)

What's Changed

• fix: detect expectations in chains with underscores by @​ghusse in https://github.com/vitest-dev/eslint-plugin-vitest/pull/607
• docs: fix no-standalone-expect.md options example by @​andykenward in https://github.com/vitest-dev/eslint-plugin-vitest/pull/606

New Contributors

• @​ghusse made their first contribution in https://github.com/vitest-dev/eslint-plugin-vitest/pull/607
• @​andykenward made their first contribution in https://github.com/vitest-dev/eslint-plugin-vitest/pull/606

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.19...v1.1.20

v1.1.19

Compare Source

Bug Fixes

• Apply ESLint to .ts files (#​602) (085e320)
• vitest/expect-expect throws false positive (#​604) (7fd75ea)

What's Changed

• fix: Apply ESLint to .ts files by @​y-hsgw in https://github.com/vitest-dev/eslint-plugin-vitest/pull/602
• fix: vitest/expect-expect throws false positive by @​y-hsgw in https://github.com/vitest-dev/eslint-plugin-vitest/pull/604

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.18...v1.1.19

v1.1.18

Compare Source

Features

• add missing globals (vitest-dev#​598) (#​599) (a0e9641)

What's Changed

• feat: add missing globals by @​yongholeeme in https://github.com/vitest-dev/eslint-plugin-vitest/pull/599
• [prefer-expect-assertions]fix false negatives for test context usage by @​y-hsgw in https://github.com/vitest-dev/eslint-plugin-vitest/pull/600

New Contributors

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

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.17...v1.1.18

v1.1.17

Compare Source

Bug Fixes

• expect.hasAssertions() / expect.assertions() - Does not work when using expect() bound to current test (#​595) (efe79c9)

What's Changed

• Change jest.fn → vi.fn in prefer-called-with rule docs by @​FloEdelmann in https://github.com/vitest-dev/eslint-plugin-vitest/pull/592
• fix: expect.hasAssertions() / expect.assertions() - Does not work when using expect() bound to current test by @​y-hsgw in https://github.com/vitest-dev/eslint-plugin-vitest/pull/595

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

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

v1.1.15

Compare Source

Bug Fixes

• padding-around-expect-groups doesn't detect expectTypeOf as an expect clause (#​588) (1138003)

What's Changed

• fix: padding-around-expect-groups doesn't detect expectTypeOf as an expect clause by @​y-hsgw in https://github.com/vitest-dev/eslint-plugin-vitest/pull/588

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

v1.1.14

Compare Source

What's Changed

• docs: Add Documentation for valid-expect-in-promise Rule by @​y-hsgw in https://github.com/vitest-dev/eslint-plugin-vitest/pull/581
• [valid-describe-callback] Fix to support options as second parameter for valid-describe-callback by @​y-hsgw in https://github.com/vitest-dev/eslint-plugin-vitest/pull/582

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.13...v1.1.14

v1.1.13

Compare Source

What's Changed

• Enhance "all" configuration and update documentation by @​y-hsgw in https://github.com/vitest-dev/eslint-plugin-vitest/pull/578

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.12...v1.1.13

v1.1.12

Compare Source

Bug Fixes

• dependancy import (a63b6c9)

What's Changed

• [valid-expect] Support typecheck by @​y-hsgw in https://github.com/vitest-dev/eslint-plugin-vitest/pull/576

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.11...v1.1.12

v1.1.11

Compare Source

What's Changed

• docs: correct "ESLint" and "Vitest" capitalization in README.md by @​JoshuaKGoldberg in https://github.com/vitest-dev/eslint-plugin-vitest/pull/575
• [valid-expect] include fixer for adding missing await by @​y-hsgw in https://github.com/vitest-dev/eslint-plugin-vitest/pull/574

New Contributors

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

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.10...v1.1.11

v1.1.10

Compare Source

Bug Fixes

• __filename used by mistake (#​573) (169413f)

v1.1.9

Compare Source

Features

• update depandancies (#​571) (753808f)
• vitest/valid-expect-in-promise: add rule (#​569) (b7cd69a)

v1.1.8

Compare Source

v1.1.7

Compare Source

Bug Fixes

• Turn vitest peer dependency optional (#​548) (a3935c7)

v1.1.6

Compare Source

Features

• prefer-vi-mocked: Add new prefer-vi-mocked rule (#​547) (cb45ae7)

v1.1.5

Compare Source

Bug Fixes

• dev-deps: fix dev dependancies meta (#​546) (1e5ef49)

v1.1.4

Compare Source

Bug Fixes

• add 'assertType' to 'expect-expect' allowed assertions (#​534) (fa377d7)

v1.1.3

Compare Source

v1.1.2

Compare Source

Bug Fixes

• fix typecheck (#​531) (2a0bd8e)

v1.1.1

Compare Source

Bug Fixes

• correct the message when required to be all lowercase (#​528) (fccefaa)

v1.1.0

Compare Source

introducing formatting rules

v1.0.5

Compare Source

Bug Fixes

• valid-expect: allow expect(value, "message") (#​518) (c0d05fd)

v1.0.4

Compare Source

Bug Fixes

• valid-describe-callback: remove noAsyncDescribeCallback (#​517) (117312f)

v1.0.3

Compare Source

Bug Fixes

• expect-expect: make assert work well with expect-expect (#​508) (ffefeae)

v1.0.2

Compare Source

Bug Fixes

• expect-expect: make sure rules doesn't break when assert is used (#​504) (65cc22c)

What's Changed

• fixed instructions for legacy plugin name by @​yairkukielka in https://github.com/vitest-dev/eslint-plugin-vitest/pull/499
• fix(expect-expect): make sure rules doesn't break when assert is used by @​veritem in https://github.com/vitest-dev/eslint-plugin-vitest/pull/504

New Contributors

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

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.0.1...v1.0.2

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone UTC, 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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 10 workspace projects
 ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with <ROOT>/package.json

Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile"

    Failure reason:
    specifiers in the lockfile ({"@0glabs/0g-ts-sdk":"0.2.1","@coinbase/coinbase-sdk":"0.10.0","@deepgram/sdk":"^3.9.0","@elizaos-plugins/adapter-sqlite":"workspace:*","@injectivelabs/sdk-ts":"^1.14.33","@vitest/eslint-plugin":"1.0.1","amqplib":"0.10.5","bs58":"5.0.0","csv-parse":"5.6.0","langdetect":"^0.2.1","ollama-ai-provider":"0.16.1","optional":"0.1.4","pnpm":"9.15.0","sharp":"0.33.5","ws":"8.18.0","zod":"3.24.1","@biomejs/biome":"^1.9.4","@commitlint/cli":"18.6.1","@commitlint/config-conventional":"18.6.3","@types/jest":"^29.5.11","cli":"workspace:*","concurrently":"9.1.0","cross-env":"7.0.3","husky":"9.1.7","jest":"^29.7.0","lerna":"8.1.5","nodemon":"3.1.7","only-allow":"1.2.1","turbo":"2.4.4","typedoc":"0.26.11","typescript":"5.6.3","viem":"2.21.58","vite":"5.4.12","vitest":"3.0.5"}) don't match specs in package.json ({"@biomejs/biome":"^1.9.4","@commitlint/cli":"18.6.1","@commitlint/config-conventional":"18.6.3","@types/jest":"^29.5.11","cli":"workspace:*","concurrently":"9.1.0","cross-env":"7.0.3","husky":"9.1.7","jest":"^29.7.0","lerna":"8.1.5","nodemon":"3.1.7","only-allow":"1.2.1","turbo":"2.4.4","typedoc":"0.26.11","typescript":"5.6.3","viem":"2.21.58","vite":"5.4.12","vitest":"3.0.5","@0glabs/0g-ts-sdk":"0.2.1","@coinbase/coinbase-sdk":"0.10.0","@deepgram/sdk":"^3.9.0","@elizaos-plugins/adapter-sqlite":"workspace:*","@injectivelabs/sdk-ts":"^1.14.33","@vitest/eslint-plugin":"1.1.36","amqplib":"0.10.5","bs58":"5.0.0","csv-parse":"5.6.0","langdetect":"^0.2.1","ollama-ai-provider":"0.16.1","optional":"0.1.4","pnpm":"9.15.0","sharp":"0.33.5","ws":"8.18.0","zod":"3.24.1"})

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• merge-queue - adds this PR to the back of the merge queue
• merge-queue-hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. 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.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using 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 do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.