chore(deps): update dependency svelte-eslint-parser to v1.8.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
svelte-eslint-parser	1.6.1 → 1.8.0

---

Release Notes

sveltejs/svelte-eslint-parser (svelte-eslint-parser)

v1.8.0

Compare Source

Minor Changes

• #​895 fe36e97 Thanks @​baseballyama! - Add an experimental ts.sys.readFile hook that speeds up type-aware lint
  of .svelte files. Opt in with SVELTE_ESLINT_PARSER_EXPERIMENTAL_TS_SYS_HOOK=1. See
  the Experimental section in the README for details.

v1.7.1

Compare Source

Patch Changes

• #​899 009dd55 Thanks @​ota-meshi! - Fix parsing TypeScript $derived(...) declaration tags inside top-level snippets.

v1.7.0

Compare Source

Minor Changes

• #​891 05dd7f0 Thanks @​dummdidumm! - feat: support Svelte 5 declaration tags

Patch Changes

• #​897 aba2993 Thanks @​ota-meshi! - fix: wrong parent type for some nodes

---

Configuration

📅 Schedule: (in timezone Asia/Bangkok)

• Branch creation
  • "every weekend"
• 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
coding-stats	Error		Jun 27, 2026 1:45am

[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 (650 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 46, reused 0, downloaded 0, added 0
Progress: resolved 50, reused 0, downloaded 0, added 0
✗ Lockfile failed supply-chain policy check (650 entries in 6.1s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  prettier@3.8.5 was published at 2026-06-26T12:58:13.266Z, within the minimumReleaseAge cutoff (2026-06-26T01:44:56.022Z)

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.