fix(deps): update dependency eslint-plugin-jsdoc to v63

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-jsdoc	^61.2.1 → ^63.0.0

---

Release Notes

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

v63.0.1

Compare Source

Bug Fixes

• empty-tags: preserve start and ending delimiters to avoid erros with single-line tags; fixes #​1697 (938a1f0)

v63.0.0

Compare Source

Bug Fixes

• require-throws: avoid skipping constructors; fixes #​1692 (cacb73e)

chore

• test Node 26; drop 20 (c43043a)

BREAKING CHANGES

• Drop Node 20

v62.9.0

Compare Source

Features

• update jsdoccomment, devDeps. (8569d0c)

v62.8.1

Compare Source

v62.8.0

Compare Source

Features

• tsdoc-ruleset: add recommended TSDoc ruleset (a96bc7c)

v62.7.1

Compare Source

Bug Fixes

• require-property: err if user blocks [@property](https://redirect.github.com/property); fixes #​1634 (23a9f1d)

v62.7.0

Compare Source

Features

• support ESLint 10 (d8599fb)

v62.6.1

Compare Source

Bug Fixes

• check-param-names: only fire on TSPropertySignature if with TSFunctionNode; fixes #​1663 (951d354)

v62.6.0

Compare Source

Features

• tag-lines: add startLinesWithNoTags option; fixes #​1661 (b36a67a)

v62.5.5

Compare Source

v62.5.4

Compare Source

Bug Fixes

• no-undefined-types: avoid treating infer type identifier as undefined; fixes #​1654 (da44046)
• no-undefined-types: ensure template tags are defined; fixes #​1655 (bfef848)

v62.5.3

Compare Source

Bug Fixes

• default-expressions and examples configs: avoid applying deprecated rules now that ESLint warns against them; fixes #​1651 (a252868)

v62.5.2

Compare Source

Bug Fixes

• valid-types: allow numeric properties for jsdoc mode; fixes #​1646 (122d283)

v62.5.1

Compare Source

Bug Fixes

• require-template: stop treating type parameters names as unknown template names; fixes #​1648 (dfc662e)
• type-formatting: update jsdoccomment and devDeps.; fixes #​1647 (19f36b6)

v62.5.0

Compare Source

Features

• check-tag-names: add Typedoc include, includeCode, and TSDoc inheritDoc/inheritdoc and label to allowable inline tags; add TSDoc and typedoc tags (925f6e3)
• require-description-complete-sentence: allow inline inheritDoc, inheritdoc, include, includeCode, label to avoid rule; fixes #​1641 (c5a09c8)
• valid-types: add Typedoc include, includeCode, and TSDoc inheritDoc/inheritdoc and label to allowable inline tags (c078633)

v62.4.1

Compare Source

v62.4.0

Compare Source

Features

• type-formatting: support trailingPunctuationMultilineOnly boolean option; fixes #​1636 (#​1638) (3907822)

v62.3.1

Compare Source

Bug Fixes

• update comment-parser, devDeps (#​1637) (f443986)

v62.3.0

Compare Source

v62.2.0

Compare Source

v62.1.0

Compare Source

v62.0.1

Compare Source

v62.0.0

Compare Source

Features

• update jsdoccomment, allowing for skipInvokedExpressionsForCommentFinding setting; fixes #​1624 (9c0e4a3)

BREAKING CHANGES

• Require Node ^20.19.0 || ^22.13.0 || >=24

---

Configuration

📅 Schedule: (UTC)

• 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 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 9 workspace projects
? Verifying lockfile against supply-chain policies (743 entries)...
✗ Lockfile failed supply-chain policy check (743 entries in 8s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 29 lockfile entries failed verification:
  @oxlint/binding-android-arm-eabi@1.68.0 was published at 2026-06-01T17:06:31.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-android-arm64@1.68.0 was published at 2026-06-01T17:06:00.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-darwin-arm64@1.68.0 was published at 2026-06-01T17:05:55.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-darwin-x64@1.68.0 was published at 2026-06-01T17:07:19.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-freebsd-x64@1.68.0 was published at 2026-06-01T17:07:30.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-linux-arm-gnueabihf@1.68.0 was published at 2026-06-01T17:06:37.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-linux-arm-musleabihf@1.68.0 was published at 2026-06-01T17:06:43.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-linux-arm64-gnu@1.68.0 was published at 2026-06-01T17:06:13.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-linux-arm64-musl@1.68.0 was published at 2026-06-01T17:06:19.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-linux-ppc64-gnu@1.68.0 was published at 2026-06-01T17:06:55.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-linux-riscv64-gnu@1.68.0 was published at 2026-06-01T17:07:01.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-linux-riscv64-musl@1.68.0 was published at 2026-06-01T17:07:06.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-linux-s390x-gnu@1.68.0 was published at 2026-06-01T17:07:13.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-linux-x64-gnu@1.68.0 was published at 2026-06-01T17:07:38.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-linux-x64-musl@1.68.0 was published at 2026-06-01T17:07:45.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-openharmony-arm64@1.68.0 was published at 2026-06-01T17:06:25.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-win32-arm64-msvc@1.68.0 was published at 2026-06-01T17:06:06.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-win32-ia32-msvc@1.68.0 was published at 2026-06-01T17:06:48.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @oxlint/binding-win32-x64-msvc@1.68.0 was published at 2026-06-01T17:07:25.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  @vitest/expect@4.1.8 was published at 2026-06-01T08:14:36.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:13:18.840Z)
  …and 9 more

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.