fix(deps): update dependency eslint-plugin-jsdoc to v48.11.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-jsdoc	48.2.0 -> 48.11.0

---

Release Notes

gajus/eslint-plugin-jsdoc (eslint-plugin-jsdoc)

v48.11.0

Compare Source

Features

• check-template-names: check callback/function tag blocks (058018b)
• require-template: check callback/function tag block content (116b3e8)

v48.10.2

Compare Source

Bug Fixes

• check-template-names: check for param and returns tags; fixes #​1286 (12fca71)

v48.10.1

Compare Source

Bug Fixes

• add espree as dependency; fixes #​1284 (31e0a35)

v48.10.0

Compare Source

Features

• require-template, check-template-names: add support ClassDeclaration (31d3255)
• require-template, check-template-names: add support FunctionDeclaration (28bc1cb)
• require-template, check-template-names: add support TSInterfaceDeclaration (320a1eb)

v48.9.3

Compare Source

Bug Fixes

• getJsdocProcessorPlugin: ensure package.json file is consistently located (87a1270)

v48.9.2

Compare Source

Bug Fixes

• examples processor: ensure config can be loaded with plugins (2fbd47c)

v48.9.1

Compare Source

Bug Fixes

• move processor to own file; fixes #​1277; fixes #​1278 (3ba475e)

v48.9.0

Compare Source

Features

• add check-examples replacement processor; fixes #​928 (6248d59)

v48.8.3

Compare Source

Bug Fixes

• require-template, check-template-names: check @​property tags; fixes #​1269 (22e3274)

v48.8.2

Compare Source

Bug Fixes

• require-template, check-template-names: avoid erring out with missing or bad typedef type; partial fix for #​1269 (736a23b)

v48.8.1

Compare Source

Bug Fixes

• sort-tags: @​template must be before @​typedef (6fb0b3e)

v48.8.0

Compare Source

Features

• check-template-names: add rule; fixes #​1120 (962d99d)
• update semver, synckit, devDeps (f61e5b2)

v48.7.0

Compare Source

Features

• require-template: add rule; fixes part of #​1120 (d46be35)

v48.6.0

Compare Source

Features

• new rule convert-to-jsdoc-comments; fixes #​1002 (d5fa8da)

v48.5.2

Compare Source

Bug Fixes

• require-param: proper errors/fixing for succeeding destructured objects; fixes #​762 (394b85f)

v48.5.1

Compare Source

Bug Fixes

• check-param-names: proper error messages for rest elements; fixes #​1225 (6371c4a)

v48.5.0

Compare Source

Features

• check-param-names: check TSMethodSignature (as on interface methods); fixes #​1249 (49400e1)

v48.4.0

Compare Source

Features

• no-types: add TSMethodSignature; fixes #​1249 (1aa3313)

v48.3.0

Compare Source

Bug Fixes

• no-undefined-types: treat variables imported by [@import](https://redirect.github.com/import) tags as defined; fixes #​1244 (54ac4fd)

Features

• check-values: checks for valid [@import](https://redirect.github.com/import) syntax (ad31b14)

v48.2.15

Compare Source

Bug Fixes

• Revert "fix(no-undefined-types): treat variables imported by [@import](https://redirect.github.com/import) tags as defined"; fixes #​1246 (ce066df)

v48.2.14

Compare Source

Bug Fixes

• no-undefined-types: treat variables imported by [@import](https://redirect.github.com/import) tags as defined; fixes #​1244 (34ba2e0)

v48.2.13

Compare Source

Bug Fixes

• no-undefined-types: prevent linting of "type" within @​import; fixes #​1242 (0bea154)

v48.2.12

Compare Source

Bug Fixes

• namespace flat config name's (8603579)

v48.2.11

Compare Source

Bug Fixes

• avoid inserting name for eslintrc configs; fixes #​1239 (c2d5a35)

v48.2.10

Compare Source

Bug Fixes

• add names to flat configs (5429982)

v48.2.9

Compare Source

Bug Fixes

• require-description-complete-sentence: regression with heading exempting; fixes #​1220 (fbc9fca)

v48.2.8

Compare Source

Bug Fixes

• require-description-complete-sentence: avoid triggering punctuation warning after Markdown headings; fixes #​1220 (e9e4440)

v48.2.7

Compare Source

Bug Fixes

• bump jsdoccomment and semver; fixes #​1233 (fb3e0e6)

v48.2.6

Compare Source

Bug Fixes

• require-yields: avoid error when ExportNamedDeclaration has no declaration prop (93a9415)

v48.2.5

Compare Source

Bug Fixes

• handle deprecated typeParameters (#​1229) (d417d05)

v48.2.4

Compare Source

Bug Fixes

• valid-types: disable checking of types/names within import tags; fixes #​1226 (4da4aeb)

v48.2.3

Compare Source

Bug Fixes

• valid-types: whitelist pratt parser keywords; fixes #​1221 (ab5624b)

v48.2.2

Compare Source

Bug Fixes

• add TS import tag; fixes #​1218 (9e9fed5)

v48.2.1

Compare Source

Bug Fixes

• require-jsdoc: avoid erring on #-marked private methods; fixes #​1212 (783b4e9)

---

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

[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.

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
• 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 explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 sequence diagram to generate a sequence diagram of the changes in 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.