fix(deps): update astro monorepo to v6.4.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
astro (source)	6.4.4 → 6.4.6

---

Release Notes

withastro/astro (astro)

v6.4.6

Compare Source

Patch Changes

• #​16765 b10e86e Thanks @​fkatsuhiro! - Fixes an issue where renaming an image file while the dev server is running triggers a build error. Now Astro correctly hot-reloads the image without crashing.

• #​17026 add3df1 Thanks @​matthewp! - Hardens addAttribute to drop attribute names containing characters that are invalid per the HTML spec (", ', >, /, =, whitespace)

• #​17033 ffda27b Thanks @​matthewp! - Validates the request origin against allowedDomains before fetching prerendered error pages. When allowedDomains is configured and the Host header matches, the original origin is used. Otherwise, the fetch falls back to localhost.

v6.4.5

Compare Source

Patch Changes

• #​16985 4ecff32 Thanks @​maximslo! - Fixes the experimental.logger destination not being used for the "Server listening on..." startup message. The logger is now resolved before the server starts listening, and adapterLogger re-creates itself when the underlying logger changes so the startup message uses the correct destination.

• #​16947 e0703a6 Thanks @​ematipico! - Fixes Astro.request.url not reflecting validated X-Forwarded-Proto/X-Forwarded-Host headers when security.allowedDomains is configured. Previously, only Astro.url was updated with the forwarded origin while Astro.request.url retained the socket-derived URL, causing the two to diverge behind TLS-terminating proxies.

• #​16997 dc45246 Thanks @​matthewp! - Reverts a change to isNode runtime detection that caused a significant build time regression for Cloudflare adapter users with large prerendered sites

---

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

Scope: all 4 workspace projects
.                                        | [WARN] Ignoring broken lockfile at /tmp/renovate/repos/github/elcoosp/skilldeck: The lockfile at "/tmp/renovate/repos/github/elcoosp/skilldeck/pnpm-lock.yaml" is broken: duplicated mapping key (7806:3)

 7803 |     resolution: {integrity: sha5 ...
 7804 |     engines: {node: ^10 || ^12 | ...
 7805 | 
 7806 |   postcss@8.5.14:
----------^
 7807 |     resolution: {integrity: sha5 ...
 7808 |     engines: {node: ^10 || ^12 | ...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 32, reused 0, downloaded 0, added 0
Progress: resolved 65, reused 0, downloaded 0, added 0
Progress: resolved 94, reused 0, downloaded 0, added 0
Progress: resolved 129, reused 0, downloaded 0, added 0
Progress: resolved 143, reused 0, downloaded 0, added 0
Progress: resolved 146, reused 0, downloaded 0, added 0
Progress: resolved 148, reused 0, downloaded 0, added 0
Progress: resolved 149, reused 0, downloaded 0, added 0
Progress: resolved 150, reused 0, downloaded 0, added 0
Progress: resolved 200, reused 0, downloaded 0, added 0
Progress: resolved 260, reused 0, downloaded 0, added 0
Progress: resolved 317, reused 0, downloaded 0, added 0
Progress: resolved 351, reused 0, downloaded 0, added 0
[ERR_PNPM_NO_MATCHING_VERSION] No matching version found for @shimmer-from-structure/solid@2.4.6 while fetching it from https://registry.npmjs.org/

This error happened while installing the dependencies of shimmer-from-structure@2.4.7

The latest release of @shimmer-from-structure/solid is "2.4.5".

If you need the full list of all 6 published versions run "pnpm view @shimmer-from-structure/solid versions".