fix(deps): update dependency astro to v5.7.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
astro (source)	5.5.2 -> 5.7.7

---

Release Notes

withastro/astro (astro)

v5.7.7

Patch Changes

• #​13705 28f8716 Thanks @​florian-lefebvre! - Updates unifont to latest and adds support for fetch options from remote providers when using the experimental fonts API

• #​13692 60d5be4 Thanks @​Le0Developer! - Fixes a bug where Astro couldn't probably use inferSize for images that contain apostrophe ' in their name.

• #​13698 ab98f88 Thanks @​sarah11918! - Improves the configuration reference docs for the adapter entry with more relevant text and links.

• #​13706 b4929ae Thanks @​ascorbic! - Fixes typechecking for content config schema

• #​13653 a7b2dc6 Thanks @​florian-lefebvre! - Reduces the amount of preloaded files for the local provider when using the experimental fonts API

• #​13653 a7b2dc6 Thanks @​florian-lefebvre! - Fixes a case where invalid CSS was emitted when using an experimental fonts API family name containing a space

v5.7.6

Compare Source

Patch Changes

• #​13703 659904b Thanks @​ascorbic! - Fixes a bug where empty fallbacks could not be provided when using the experimental fonts API

• #​13680 18e1b97 Thanks @​florian-lefebvre! - Improves the UnsupportedExternalRedirect error message to include more details such as the concerned destination

• #​13703 659904b Thanks @​ascorbic! - Simplifies styles for experimental responsive images

  ⚠️ BREAKING CHANGE FOR EXPERIMENTAL RESPONSIVE IMAGES ONLY ⚠️

  The generated styles for image layouts are now simpler and easier to override. Previously the responsive image component used CSS to set the size and aspect ratio of the images, but this is no longer needed. Now the styles just include object-fit and object-position for all images, and sets max-width: 100% for constrained images and width: 100% for full-width images.

  This is an implementation change only, and most users will see no change. However, it may affect any custom styles you have added to your responsive images. Please check your rendered images to determine whether any change to your CSS is needed.

  The styles now use the :where() pseudo-class, which has a specificity of 0, meaning that it is easy to override with your own styles. You can now be sure that your own classes will always override the applied styles, as will global styles on img.

  An exception is Tailwind 4, which uses cascade layers, meaning the rules are always lower specificity. Astro supports browsers that do not support cascade layers, so we cannot use this. If you need to override the styles using Tailwind 4, you must use !important classes. Do check if this is needed though: there may be a layout that is more appropriate for your use case.

• #​13703 659904b Thanks @​ascorbic! - Adds warnings about using local font files in the publicDir when the experimental fonts API is enabled.

• #​13703 659904b Thanks @​ascorbic! - Renames experimental responsive image layout option from "responsive" to "constrained"

  ⚠️ BREAKING CHANGE FOR EXPERIMENTAL RESPONSIVE IMAGES ONLY ⚠️

  The layout option called "responsive" is renamed to "constrained" to better reflect its behavior.

  The previous name was causing confusion, because it is also the name of the feature. The responsive layout option is specifically for images that are displayed at the requested size, unless they do not fit the width of their container, at which point they would be scaled down to fit. They do not get scaled beyond the intrinsic size of the source image, or the width prop if provided.

  It became clear from user feedback that many people (understandably) thought that they needed to set layout to responsive if they wanted to use responsive images. They then struggled with overriding styles to make the image scale up for full-width hero images, for example, when they should have been using full-width layout. Renaming the layout to constrained should make it clearer that this layout is for when you want to constrain the maximum size of the image, but allow it to scale-down.

Upgrading

If you set a default image.experimentalLayout in your astro.config.mjs, or set it on a per-image basis using the layout prop, you will need to change all occurences to constrained:

// astro.config.mjs
export default {
  image: {
-    experimentalLayout: 'responsive',
+    experimentalLayout: 'constrained',
  },
}

v5.7.5

Compare Source

Patch Changes

• #​13660 620d15d Thanks @​mingjunlu! - Adds server.allowedHosts docs comment to AstroUserConfig

• #​13591 5dd2d3f Thanks @​florian-lefebvre! - Removes unused code

• #​13669 73f24d4 Thanks @​ematipico! - Fixes an issue where Astro.originPathname wasn't returning the correct value when using rewrites.

• #​13674 42388b2 Thanks @​florian-lefebvre! - Fixes a case where an experimental fonts API error would be thrown when using another astro:assets API

• #​13654 4931457 Thanks @​florian-lefebvre! - Fixes fontProviders.google() so it can forward options to the unifont provider, when using the experimental fonts API

• Updated dependencies [5dd2d3f]:

  • @​astrojs/telemetry@​3.2.1

v5.7.4

Compare Source

Patch Changes

• #​13647 ffbe8f2 Thanks @​ascorbic! - Fixes a bug that caused a session error to be logged when using actions without sessions

• #​13646 6744842 Thanks @​florian-lefebvre! - Fixes a case where extra font sources were removed when using the experimental fonts API

• #​13635 d75cac4 Thanks @​florian-lefebvre! - The experimental fonts API now generates optimized fallbacks for every weight and style

v5.7.3

Compare Source

Patch Changes

• #​13643 67b7493 Thanks @​tanishqmanuja! - Fixes a case where the font face src format would be invalid when using the experimental fonts API

• #​13639 23410c6 Thanks @​florian-lefebvre! - Fixes a case where some font families would not be downloaded when using the same font provider several times, using the experimental fonts API

v5.7.2

Compare Source

Patch Changes

• #​13632 cb05cfb Thanks @​florian-lefebvre! - Improves the optimized fallback name generated by the experimental Fonts API

• #​13630 3e7db4f Thanks @​florian-lefebvre! - Fixes a case where fonts using a local provider would not work because of an invalid generated src

• #​13634 516de7d Thanks @​ematipico! - Fixes a regression where using next('/') didn't correctly return the requested route.

• #​13632 cb05cfb Thanks @​florian-lefebvre! - Improves the quality of optimized fallbacks generated by the experimental Fonts API

• #​13616 d475afc Thanks @​lfilho! - Fixes a regression where relative static redirects didn't work as expected.

v5.7.1

Compare Source

Patch Changes

• #​13594 dc4a015 Thanks @​florian-lefebvre! - Reduces the number of font files downloaded

• #​13627 7f1a624 Thanks @​florian-lefebvre! - Fixes a case where using the <Font /> component would throw a Rollup error during the build

• #​13626 3838efe Thanks @​florian-lefebvre! - Updates fallback font generation to always read font files returned by font providers

• #​13625 f1311d2 Thanks @​florian-lefebvre! - Updates the <Font /> component so that preload links are generated before the style tag if preload is passed

• #​13622 a70d32a Thanks @​ascorbic! - Improve autocomplete for session keys

v5.7.0

Compare Source

Minor Changes

• #​13527 2fd6a6b Thanks @​ascorbic! - The experimental session API introduced in Astro 5.1 is now stable and ready for production use.

  Sessions are used to store user state between requests for on-demand rendered pages. You can use them to store user data, such as authentication tokens, shopping cart contents, or any other data that needs to persist across requests:

v5.6.2

Compare Source

Patch Changes

• #​13606 793ecd9 Thanks @​natemoo-re! - Fixes a regression that allowed prerendered code to leak into the server bundle.

• #​13576 1c60ec3 Thanks @​ascorbic! - Reduces duplicate code in server islands scripts by extracting shared logic into a helper function.

• #​13588 57e59be Thanks @​natemoo-re! - Fixes a memory leak when using SVG assets.

• #​13589 5a0563d Thanks @​ematipico! - Deprecates the asset utility function emitESMImage() and adds a new emitImageMetadata() to be used instead

  The function
  emitESMImage() is now deprecated. It will continue to function, but it is no longer recommended nor supported. This function will be completely removed in a next major release of Astro.

  Please replace it with the new functionemitImageMetadata() as soon as you are able to do so:

  - import { emitESMImage } from "astro/assets/utils";
  + import { emitImageMetadata } from "astro/assets/utils";

  The new function returns the same signature as the previous one. However, the new function removes two deprecated arguments that were not meant to be exposed for public use: _watchMode and experimentalSvgEnabled. Since it was possible to access these with the old function, you may need to verify that your code still works as intended with emitImageMetadata().

• #​13596 3752519 Thanks @​jsparkdev! - update vite to latest version to fix CVE

• #​13547 360cb91 Thanks @​jsparkdev! - Updates vite to the latest version

• #​13548 e588527 Thanks @​ryuapp! - Support for Deno to install npm pacakges.

  Deno requires npm prefix to install packages on npm. For example, to install react, we need to run deno add npm:react. But currently the command executed is deno add react, which doesn't work. So, we change the package names to have an npm prefix if you are using Deno.

• #​13587 a0774b3 Thanks @​robertoms99! - Fixes an issue with the client router where some attributes of the root element were not updated during swap, including the transition scope.

v5.6.1

Compare Source

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.

v5.6.0

Compare Source

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.

  This follows the same API described in the Speculation Rules API and allows you to balance the benefit of reduced wait times against bandwidth, memory, and CPU costs for your site visitors.

  For example, you can now use prefetch() programmatically with large sets of links and avoid browser limits in place to guard against over-speculating (prerendering/prefetching too many links). Set eagerness: 'moderate' to take advantage of First In, First Out (FIFO) strategies and browser heuristics to let the browser decide when to prerender/prefetch them and in what order:

  <a class="link-moderate" href="/nice-link-1">A Nice Link 1</a>
  <a class="link-moderate" href="/nice-link-2">A Nice Link 2</a>
  <a class="link-moderate" href="/nice-link-3">A Nice Link 3</a>
  <a class="link-moderate" href="/nice-link-4">A Nice Link 4</a>
  ...
  <a class="link-moderate" href="/nice-link-20">A Nice Link 20</a>
  <script>
    import { prefetch } from 'astro:prefetch';
    const linkModerate = document.getElementsByClassName('link-moderate');
    linkModerate.forEach((link) => prefetch(link.getAttribute('href'), { eagerness: 'moderate' }));
  </script>

• #​13482 ff257df Thanks @​florian-lefebvre! - Improves integrations error handling

  If an error is thrown from an integration hook, an error log will now provide information about the concerned integration and hook

Patch Changes

• #​13539 c43bf8c Thanks @​ascorbic! - Adds a new session.load() method to the experimental session API that allows you to load a session by ID.

  When using the experimental sessions API, you don't normally need to worry about managing the session ID and cookies: Astro automatically reads the user's cookies and loads the correct session when needed. However, sometimes you need more control over which session to load.

  The new load() method allows you to manually load a session by ID. This is useful if you are handling the session ID yourself, or if you want to keep track of a session without using cookies. For example, you might want to restore a session from a logged-in user on another device, or work with an API endpoint that doesn't use cookies.

  // src/pages/api/cart.ts
  import type { APIRoute } from 'astro';
  
  export const GET: APIRoute = async ({ session, request }) => {
    // Load the session from a header instead of cookies
    const sessionId = request.headers.get('x-session-id');
    await session.load(sessionId);
    const cart = await session.get('cart');
    return Response.json({ cart });
  };

  If a session with that ID doesn't exist, a new one will be created. This allows you to generate a session ID in the client if needed.

  For more information, see the experimental sessions docs.

• #​13488 d777420 Thanks @​stramel! - BREAKING CHANGE to the experimental SVG Component API only

  Removes some previously available prop, attribute, and configuration options from the experimental SVG API. These items are no longer available and must be removed from your code:

  • The title prop has been removed until we can settle on the correct balance between developer experience and accessibility. Please replace any title props on your components with aria-label:

    - <Logo title="My Company Logo" />
    + <Logo aria-label="My Company Logo" />

  • Sprite mode has been temporarily removed while we consider a new implementation that addresses how this feature was being used in practice. This means that there are no longer multiple mode options, and all SVGs will be inline. All instances of mode must be removed from your project as you can no longer control a mode:

    - <Logo mode="inline" />
    + <Logo />

    import { defineConfig } from 'astro'
    
    export default defineConfig({
      experimental: {
    -    svg: {
    -      mode: 'sprite'
    -    },
    +   svg: true
      }
    });

  • The default role is no longer applied due to developer feedback. Please add the appropriate role on each component individually as needed:

    - <Logo />
    + <Logo role="img" /> // To keep the role that was previously applied by default

  • The size prop has been removed to better work in combination with viewBox and additional styles/attributes. Please replace size with explicit width and height attributes:

    - <Logo size={64} />
    + <Logo width={64} height={64} />

v5.5.6

Compare Source

Patch Changes

• #​13429 06de673 Thanks @​ematipico! - The ActionAPIContext.rewrite method is deprecated and will be removed in a future major version of Astro

• #​13524 82cd583 Thanks @​ematipico! - Fixes a bug where the functions Astro.preferredLocale and Astro.preferredLocaleList would return the incorrect locales
  when the Astro configuration specifies a list of codes. Before, the functions would return the path, instead now the functions
  return a list built from codes.

• #​13526 ff9d69e Thanks @​jsparkdev! - update vite to the latest version

v5.5.5

Compare Source

Patch Changes

• #​13510 5b14d33 Thanks @​florian-lefebvre! - Fixes a case where astro:env secrets used in actions would not be available

• #​13485 018fbe9 Thanks @​ascorbic! - Fixes a bug that caused cookies to ignore custom decode function if has() had been called before

• #​13505 a98ae5b Thanks @​ematipico! - Updates the dependency vite to the latest.

• #​13483 fc2dcb8 Thanks @​ematipico! - Fixes a bug where an Astro adapter couldn't call the middleware when there isn't a route that matches the incoming request.

v5.5.4

Compare Source

Patch Changes

• #​13457 968e713 Thanks @​ascorbic! - Sets correct response status text for custom error pages

• #​13447 d80ba2b Thanks @​ematipico! - Fixes an issue where site was added to the generated redirects.

• #​13481 e9e9245 Thanks @​martrapp! - Makes server island work with the client router again.

• #​13484 8b5e4dc Thanks @​ascorbic! - Display useful errors when config loading fails because of Node addons being disabled on Stackblitz

v5.5.3

Compare Source

Patch Changes

• #​13437 013fa87 Thanks @​Vardhaman619! - Handle server.allowedHosts when the value is true without attempting to push it into an array.

• #​13324 ea74336 Thanks @​ematipico! - Upgrade to shiki v3

• #​13372 7783dbf Thanks @​ascorbic! - Fixes a bug that caused some very large data stores to save incomplete data.

• #​13358 8c21663 Thanks @​ematipico! - Adds a new function called insertPageRoute to the Astro Container API.

  The new function is useful when testing routes that, for some business logic, use Astro.rewrite.

  For example, if you have a route /blog/post and for some business decision there's a rewrite to /generic-error, the container API implementation will look like this:

  import Post from '../src/pages/Post.astro';
  import GenericError from '../src/pages/GenericError.astro';
  import { experimental_AstroContainer as AstroContainer } from 'astro/container';
  
  const container = await AstroContainer.create();
  container.insertPageRoute('/generic-error', GenericError);
  const result = await container.renderToString(Post);
  console.log(result); // this should print the response from GenericError.astro

  This new method only works for page routes, which means that endpoints aren't supported.

• #​13426 565583b Thanks @​ascorbic! - Fixes a bug that caused the astro add command to ignore the --yes flag for third-party integrations

• #​13428 9cac9f3 Thanks @​matthewp! - Prevent bad value in x-forwarded-host from crashing request

• #​13432 defad33 Thanks @​P4tt4te! - Fix an issue in the Container API, where the renderToString function doesn't render adequately nested slots when they are components.

• Updated dependencies [ea74336]:

  • @​astrojs/markdown-remark@​6.3.1

---

Configuration

📅 Schedule: 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.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[lazysegtree]

One week wait.

[lazysegtree]

Validated npm installed and website's local run