chore(deps): update dependency eslint-plugin-simple-import-sort to v14 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-simple-import-sort	^13.0.0 → ^14.0.0

---

Release Notes

lydell/eslint-plugin-simple-import-sort (eslint-plugin-simple-import-sort)

v14.0.0

Compare Source

ES2022 allows string literals as module export names ("arbitrary module namespace names"):

export { yukuTs as "yuku-ts" };
import { "a-b" as c } from "a";

This release adds support for such quotes names. Previously, those were sorted oddly, and the autofix could suggest changes that wasn’t valid syntax.

This is only a breaking change if you use string literals as module export names, and only in the form of that you need to autofix your files.

Thanks to Kamronbek_Juraev (@​KAMRONBEK) for fixing this!

---

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

? Verifying lockfile against supply-chain policies (780 entries)...
✗ Lockfile failed supply-chain policy check (780 entries in 3.2s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 11 lockfile entries failed verification:
  @playwright/test@1.62.1 was published at 2026-07-30T16:36:50.000Z, within the minimumReleaseAge cutoff (2026-07-30T06:41:56.152Z)
  @types/react@19.2.18 was published at 2026-07-30T21:54:03.456Z, within the minimumReleaseAge cutoff (2026-07-30T06:41:56.152Z)
  baseline-browser-mapping@2.11.8 was published at 2026-07-30T15:57:18.000Z, within the minimumReleaseAge cutoff (2026-07-30T06:41:56.152Z)
  brace-expansion@1.1.18 was published at 2026-07-30T10:17:06.961Z, within the minimumReleaseAge cutoff (2026-07-30T06:41:56.152Z)
  brace-expansion@2.1.4 was published at 2026-07-30T10:15:01.601Z, within the minimumReleaseAge cutoff (2026-07-30T06:41:56.152Z)
  brace-expansion@5.0.9 was published at 2026-07-30T10:00:32.762Z, within the minimumReleaseAge cutoff (2026-07-30T06:41:56.152Z)
  enhanced-resolve@5.24.5 was published at 2026-07-30T10:14:14.000Z, within the minimumReleaseAge cutoff (2026-07-30T06:41:56.152Z)
  flatted@3.4.4 was published at 2026-07-30T09:53:10.155Z, within the minimumReleaseAge cutoff (2026-07-30T06:41:56.152Z)
  lucide-react@1.28.0 was published at 2026-07-30T07:53:09.000Z, within the minimumReleaseAge cutoff (2026-07-30T06:41:56.152Z)
  playwright-core@1.62.1 was published at 2026-07-30T16:36:44.000Z, within the minimumReleaseAge cutoff (2026-07-30T06:41:56.152Z)
  playwright@1.62.1 was published at 2026-07-30T16:36:38.000Z, within the minimumReleaseAge cutoff (2026-07-30T06:41:56.152Z)

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.