chore(deps): update dependency svelte-check to v4.7.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
svelte-check	4.4.8 → 4.7.1

---

Release Notes

sveltejs/language-tools (svelte-check)

v4.7.1

Compare Source

Patch Changes

• fix: correctly parse --tsgo-experimental-api flag (#​3067)

v4.7.0

Compare Source

Minor Changes

• feat: add --config option (#​3066)

• feat: svelte-check tsgo support with experimental api (#​3036)

Patch Changes

• fix: load esm version of Vite (#​3065)

• fix: stop excluding workspaces under dot-prefixed ancestors (#​3037)

• Updated dependencies [7a3464b, a2561fc]:

  • @​sveltejs/load-config@​0.2.0

v4.6.0

Compare Source

Minor Changes

• feat: support reading Svelte config from vite.config.js/ts (#​3031)

Patch Changes

• Updated dependencies [151cf45]:
  • @​sveltejs/load-config@​0.1.1

v4.5.0

Compare Source

Minor Changes

• feat: support Svelte 5 declaration tags (#​3033)

Patch Changes

• fix: properly handle props with the name slot inside Svelte 5 snippets (#​3030)

• feat: add support for svelte config ts/mts files (#​3009)

---

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:44am

[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 45, reused 0, downloaded 0, added 0
Progress: resolved 49, 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:37.837Z)

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.