chore(deps): bump astro from 5.5.5 to 5.6.1

[dependabot]

Bumps astro from 5.5.5 to 5.6.1.

Release notes

Sourced from astro's releases.

astro@5.6.1

Patch Changes

• #13519 3323f5c Thanks @​florian-lefebvre! - Refactors some internals to improve Rolldown compatibility

• #13545 a7aff41 Thanks @​stramel! - Prevent empty attributes from appearing in the SVG output

• #13552 9cd0fd4 Thanks @​ematipico! - Fixes an issue where Astro validated the i18n configuration incorrectly, causing false positives in downstream libraries.

astro@5.6.0

Minor Changes

• #13403 dcb9526 Thanks @​yurynix! - Adds a new optional prerenderedErrorPageFetch option in the Adapter API to allow adapters to provide custom implementations for fetching prerendered error pages.

  Now, adapters can override the default fetch() behavior, for example when fetch() is unavailable or when you cannot call the server from itself.

  The following example provides a custom fetch for 500.html and 404.html, reading them from disk instead of performing an HTTP call:

  return app.render(request, {
    prerenderedErrorPageFetch: async (url: string): Promise<Response> => {
      if (url.includes("/500")) {
          const content = await fs.promises.readFile("500.html", "utf-8");
          return new Response(content, {
            status: 500,
            headers: { "Content-Type": "text/html" },
          });
      }
      const content = await fs.promises.readFile("404.html", "utf-8");
        return new Response(content, {
          status: 404,
          headers: { "Content-Type": "text/html" },
        });
  });

  If no value is provided, Astro will fallback to its default behavior for fetching error pages.

  Read more about this feature in the Adapter API reference.

• #13482 ff257df Thanks @​florian-lefebvre! - Updates Astro config validation to also run for the Integration API. An error log will specify which integration is failing the validation.

  Now, Astro will first validate the user configuration, then validate the updated configuration after each integration astro:config:setup hook has run. This means updateConfig() calls will no longer accept invalid configuration.

  This fixes a situation where integrations could potentially update a project with a malformed configuration. These issues should now be caught and logged so that you can update your integration to only set valid configurations.

• #13405 21e7e80 Thanks @​Marocco2! - Adds a new eagerness option for prefetch() when using experimental.clientPrerender

  With the experimental clientPrerender flag enabled, you can use the eagerness option on prefetch() to suggest to the browser how eagerly it should prefetch/prerender link targets.

... (truncated)

Changelog

Sourced from astro's changelog.

5.6.1

Patch Changes

• #13519 3323f5c Thanks @​florian-lefebvre! - Refactors some internals to improve Rolldown compatibility

• #13545 a7aff41 Thanks @​stramel! - Prevent empty attributes from appearing in the SVG output

• #13552 9cd0fd4 Thanks @​ematipico! - Fixes an issue where Astro validated the i18n configuration incorrectly, causing false positives in downstream libraries.

5.6.0

Minor Changes

• #13403 dcb9526 Thanks @​yurynix! - Adds a new optional prerenderedErrorPageFetch option in the Adapter API to allow adapters to provide custom implementations for fetching prerendered error pages.

  Now, adapters can override the default fetch() behavior, for example when fetch() is unavailable or when you cannot call the server from itself.

  The following example provides a custom fetch for 500.html and 404.html, reading them from disk instead of performing an HTTP call:

  return app.render(request, {
    prerenderedErrorPageFetch: async (url: string): Promise<Response> => {
      if (url.includes("/500")) {
          const content = await fs.promises.readFile("500.html", "utf-8");
          return new Response(content, {
            status: 500,
            headers: { "Content-Type": "text/html" },
          });
      }
      const content = await fs.promises.readFile("404.html", "utf-8");
        return new Response(content, {
          status: 404,
          headers: { "Content-Type": "text/html" },
        });
  });

  If no value is provided, Astro will fallback to its default behavior for fetching error pages.

  Read more about this feature in the Adapter API reference.

• #13482 ff257df Thanks @​florian-lefebvre! - Updates Astro config validation to also run for the Integration API. An error log will specify which integration is failing the validation.

  Now, Astro will first validate the user configuration, then validate the updated configuration after each integration astro:config:setup hook has run. This means updateConfig() calls will no longer accept invalid configuration.

  This fixes a situation where integrations could potentially update a project with a malformed configuration. These issues should now be caught and logged so that you can update your integration to only set valid configurations.

• #13405 21e7e80 Thanks @​Marocco2! - Adds a new eagerness option for prefetch() when using experimental.clientPrerender

... (truncated)

Commits

• 9520a23 [ci] release (#13554)
• 5af40dc [ci] format
• 9cd0fd4 fix(i18n): incorrect validation (#13552)
• a7aff41 fix(svg): prevent empty attributes (#13545)
• 3323f5c feat: improve rolldown compatibility (#13519)
• 90b0ac1 [ci] release (#13540)
• d777420 Remove non-stable SVG features (#13488)
• f5a8b07 [ci] format
• c43bf8c feat: add session.load(id) method (#13539)
• 0edd79f [ci] format
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[cloudflare-workers-and-pages]

Deploying www with    Cloudflare Pages

Latest commit:	e3c8bdd
Status:	✅  Deploy successful!
Preview URL:	https://9a9ab1a0.www-5g5.pages.dev
Branch Preview URL:	https://dependabot-npm-and-yarn-astr-486u.www-5g5.pages.dev

View logs