chore(deps): update dependency prettier-plugin-svelte to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
prettier-plugin-svelte	^3.5.1 → ^4.0.0

---

Release Notes

sveltejs/prettier-plugin-svelte (prettier-plugin-svelte)

v4.1.1

Compare Source

Patch Changes

• fix: preserve nested rest patterns in {#each} destructuring (#​537)

• fix: preserve whitespace inside <textarea> (its content is whitespace-sensitive, like <pre>) (#​540)

• fix: don't drop <script>/<style> content when the closing tag has whitespace (</script >) (#​539)

v4.1.0

Compare Source

Minor Changes

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

v4.0.1

Compare Source

Patch Changes

• fix: print @const correctly (#​530)

v4.0.0

Compare Source

• (breaking) Require Svelte 5
• (breaking) Remove svelteBracketNewLine option
• (breaking) Remove svelteStrictMode option
• (fix) Keep trailing <!-- #endregion --> comments below svelte:options / scripts / styles

v3.5.2

Compare Source

• (fix) Preserve non-breaking spaces
• (fix) handle comments in bind: get/set tuple
• (fix) handle computed properties in e.g. {#each} blocks

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ 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 8 workspace projects
? Verifying lockfile against supply-chain policies (1393 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 30, reused 0, downloaded 0, added 0
Progress: resolved 31, reused 0, downloaded 0, added 0
✗ Lockfile failed supply-chain policy check (1393 entries in 8.4s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  astro@6.4.7 was published at 2026-06-15T10:47:19.000Z, within the minimumReleaseAge cutoff (2026-06-15T01:57:11.178Z)

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.