chore(deps): update dependency @doist/eslint-config to v13

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@doist/eslint-config	8.1.4 → 13.1.1

---

Release Notes

Doist/eslint-config (@​doist/eslint-config)

v13.1.1

Compare Source

v13.1.0

Compare Source

v13.0.0

Compare Source

v12.0.1

Compare Source

v12.0.0

Compare Source

v11.2.1

Compare Source

v11.2.0

Compare Source

v11.1.0

Compare Source

v11.0.0

Compare Source

v10.0.0

Compare Source

v9.0.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Monday through Friday (* * * * 1-5)
• 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: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"5.62.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @typescript-eslint/eslint-plugin@"^6.0.0 || ^7.0.0 || ^8.0.0" from @doist/[email protected]
npm error node_modules/@doist/eslint-config
npm error   dev @doist/eslint-config@"13.1.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-29T17_58_23_184Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-29T17_58_23_184Z-debug-0.log

[doistbot-app]

This PR updates the @doist/eslint-config dependency to v13, bringing in the latest flat config support and linting rules. However, this major version bump introduces breaking changes requiring manual updates to .eslintrc.js for new configuration entry points and renamed base configurations. Additionally, the project's @typescript-eslint dependencies will need to be upgraded to v6 to prevent peer dependency conflicts and ensure successful linting.

_{Share Feedback • Review Logs}

[doistbot-app]

[P1] Upgrading to @doist/eslint-config v13 introduces breaking changes that require manual intervention. According to the release notes, you must update .eslintrc.js to use the new configuration entry points (e.g., prefixing paths with eslintrc/) and rename the base configurations (e.g., from recommended-requiring-type-checking to recommended-type-checked).

Additionally, this version requires @typescript-eslint/eslint-plugin and @typescript-eslint/parser to be at v6, but they are currently pinned at v5 in this project. This mismatch will likely cause peer dependency conflicts or linting errors when running npm run integrity-check.