fix(deps): update dependency astro to v5 #169

renovate · 2024-12-03T11:28:56Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
astro (source)	`4.16.18` -> `5.9.2`

Release Notes

withastro/astro (astro)

`v5.9.2`

Compare Source

Patch Changes

#13919 423fe60 Thanks @ematipico! - Fixes a bug where Astro added quotes to the CSP resources.

Only certain resources require quotes (e.g. 'self' but not https://cdn.example.com), so Astro no longer adds quotes to any resources. You must now provide the quotes yourself for resources such as 'self' when necessary:
```
export default defineConfig({
  experimental: {
    csp: {
      styleDirective: {
        resources: [
-          "self",
+          "'self'",
          "https://cdn.example.com"
        ]
      }
    }
  }
})
```
#13914 76c5480 Thanks @ematipico! - BREAKING CHANGE to the experimental Content Security Policy feature only

Removes support for experimental Content Security Policy (CSP) when using the <ClientRouter /> component for view transitions.

It is no longer possible to enable experimental CSP while using Astro's view transitions. Support was already unstable with the <ClientRouter /> because CSP required making its underlying implementation asynchronous. This caused breaking changes for several users and therefore, this PR removes support completely.

If you are currently using the component for view transitions, please remove the experimental CSP flag as they cannot be used together.
```
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
-   csp: true
   }
});
```
Alternatively, to continue using experimental CSP in your project, you can consider migrating to the browser native View Transition API and remove the <ClientRouter /> from your project. You may be able to achieve similar results if you are not using Astro's enhancements to the native View Transitions and Navigation APIs.

Support might be reintroduced in future releases. You can follow this experimental feature's development in the CSP RFC.

`v5.9.1`

Compare Source

Patch Changes

#13899 7a1303d Thanks @reknih! - Fix bug where error pages would return invalid bodies if the upstream response was compressed
#13902 051bc30 Thanks @arHSM! - Fixes a bug where vite virtual module ids were incorrectly added in the dev server
#13905 81f71ca Thanks @jsparkdev! - Fixes wrong contents in CSP meta tag.
#13907 8246bcc Thanks @martrapp! - Fixes a bug that caused view transition names to be lost.
#13901 37fa0a2 Thanks @ansg191! - fix fallback not being removed when server island is rendered

`v5.9.0`

Compare Source

Minor Changes

#13802 0eafe14 Thanks @ematipico! - Adds experimental Content Security Policy (CSP) support

CSP is an important feature to provide fine-grained control over resources that can or cannot be downloaded and executed by a document. In particular, it can help protect against cross-site scripting (XSS) attacks.

Enabling this feature adds additional security to Astro's handling of processed and bundled scripts and styles by default, and allows you to further configure these, and additional, content types. This new experimental feature has been designed to work in every Astro rendering environment (static pages, dynamic pages and single page applications), while giving you maximum flexibility and with type-safety in mind.

It is compatible with most of Astro's features such as client islands, and server islands, although Astro's view transitions using the <ClientRouter /> are not yet fully supported. Inline scripts are not supported out of the box, but you can provide your own hashes for external and inline scripts.

To enable this feature, add the experimental flag in your Astro config:
```
// astro.config.mjs
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
    csp: true,
  },
});
```
For more information on enabling and using this feature in your project, see the Experimental CSP docs.

For a complete overview, and to give feedback on this experimental API, see the Content Security Policy RFC.
#13850 1766d22 Thanks @ascorbic! - Provides a Markdown renderer to content loaders

When creating a content loader, you will now have access to a renderMarkdown function that allows you to render Markdown content directly within your loaders. It uses the same settings and plugins as the renderer used for Markdown files in Astro, and follows any Markdown settings you have configured in your Astro project.

This allows you to render Markdown content from various sources, such as a CMS or other data sources, directly in your loaders without needing to preprocess the Markdown content separately.
```
import type { Loader } from 'astro/loaders';
import { loadFromCMS } from './cms';

export function myLoader(settings): Loader {
  return {
    name: 'my-loader',
    async load({ renderMarkdown, store }) {
      const entries = await loadFromCMS();

      store.clear();

      for (const entry of entries) {
        // Assume each entry has a 'content' field with markdown content
        store.set(entry.id, {
          id: entry.id,
          data: entry,
          rendered: await renderMarkdown(entry.content),
        });
      }
    },
  };
}
```
The return value of renderMarkdown is an object with two properties: html and metadata. These match the rendered property of content entries in content collections, so you can use them to render the content in your components or pages.

`v5.8.2`

Compare Source

Patch Changes

#13877 5a7797f Thanks @yuhang-dong! - Fixes a bug that caused Astro.rewrite to fail when used in sequenced middleware
#13872 442b841 Thanks @isVivek99! - Fixes rendering of the download attribute when it has a boolean value

`v5.8.1`

Compare Source

Patch Changes

#13037 de2fc9b Thanks @nanarino! - Fixes rendering of the popover attribute when it has a boolean value
#13851 45ae95a Thanks @ascorbic! - Allows disabling default styles for responsive images

This change adds a new image.experimentalDefaultStyles option that allows you to disable the default styles applied to responsive images.

When using experimental responsive images, Astro applies default styles to ensure the images resize correctly. In most cases this is what you want – and they are applied with low specificity so your own styles override them. However in some cases you may want to disable these default styles entirely. This is particularly useful when using Tailwind 4, because it uses CSS cascade layers to apply styles, making it difficult to override the default styles.

image.experimentalDefaultStyles is a boolean option that defaults to true, so you can change it in your Astro config file like this:
```
export default {
  image: {
    experimentalDefaultStyles: false,
  },
  experimental: {
    responsiveImages: true,
  },
};
```
#13858 cb1a168 Thanks @florian-lefebvre! - Fixes the warning shown when client directives are used on Astro components
#12574 da266d0 Thanks @apatel369! - Allows using server islands in mdx files
#13843 fbcfa68 Thanks @z1haze! - Export type AstroSession to allow use in explicitly typed safe code.

`v5.8.0`

Compare Source

Minor Changes

#13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

Patch Changes

Updated dependencies [3c3b492]:
- @astrojs/telemetry @3.3.0
- @astrojs/markdown-remark @6.3.2

`v5.7.14`

Compare Source

Patch Changes

#13773 3aa5337 Thanks @sijad! - Ignores lightningcss unsupported pseudo-class warning.
#13833 5a6d2ae Thanks @ascorbic! - Fixes an issue where session modules would fail to resolve in Node.js < 20.6
#13383 f7f712c Thanks @Haberkamp! - Stop toolbar settings from overflowing
#13794 85b19d8 Thanks @alexcarpenter! - Exclude pre tags from a11y-no-noninteractive-tabindex audit check.
#13373 50ef568 Thanks @jpwienekus! - Fixes a bug where highlights and tooltips render over the audit list window.
#13769 e9fc456 Thanks @romanstetsyk! - Expand ActionError codes to include all IANA-registered HTTP error codes.
#13668 866285a Thanks @sapphi-red! - Replaces internal CSS chunking behavior for Astro components' scoped styles to use Vite's cssScopeTo feature. The feature is a port of Astro's implementation so this should not change the behavior.

`v5.7.13`

Compare Source

Patch Changes

#13761 a2e8463 Thanks @jp-knj! - Adds new content collections errors
#13788 7d0b7ac Thanks @florian-lefebvre! - Fixes a case where an error would not be thrown when using the <Font /> component from the experimental fonts API without adding fonts in the Astro config
#13784 d7a1889 Thanks @florian-lefebvre! - Fixes the experimental fonts API to correctly take config.base, config.build.assets and config.build.assetsPrefix into account
#13777 a56b8ea Thanks @L4Ph! - Fixed an issue where looping GIF animation would stop when converted to WebP
#13566 0489d8f Thanks @TheOtterlord! - Fix build errors being ignored when build.concurrency > 1

`v5.7.12`

Compare Source

Patch Changes

#13752 a079c21 Thanks @florian-lefebvre! - Improves handling of font URLs not ending with a file extension when using the experimental fonts API
#13750 7d3127d Thanks @martrapp! - Allows the ClientRouter to open new tabs or windows when submitting forms by clicking while holding the Cmd, Ctrl, or Shift key.
#13765 d874fe0 Thanks @florian-lefebvre! - Fixes a case where font sources with relative protocol URLs would fail when using the experimental fonts API
#13640 5e582e7 Thanks @florian-lefebvre! - Allows inferring weight and style when using the local provider of the experimental fonts API

If you want Astro to infer those properties directly from your local font files, leave them undefined:
```
{
  // No weight specified: infer
  style: 'normal'; // Do not infer
}
```

`v5.7.11`

Compare Source

Patch Changes

#13734 30aec73 Thanks @ascorbic! - Loosen content layer schema types
#13751 5816b8a Thanks @florian-lefebvre! - Updates unifont to support subsets when using the google provider with the experimental fonts API
#13756 d4547ba Thanks @florian-lefebvre! - Adds a terminal warning when a remote provider returns no data for a family when using the experimental fonts API
#13742 f599463 Thanks @florian-lefebvre! - Fixes optimized fallback css generation to properly add a src when using the experimental fonts API
#13740 6935540 Thanks @vixalien! - Fix cookies set after middleware did a rewrite with next(url) not being applied
#13759 4a56d0a Thanks @jp-knj! - Improved the error handling of certain error cases.

`v5.7.10`

Compare Source

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

`v5.7.9`

Compare Source

Patch Changes

#13711 2103991 Thanks @ascorbic! - Fixes height for responsive images

`v5.7.8`

Compare Source

Patch Changes

#13715 b32dffa Thanks @florian-lefebvre! - Updates unifont to fix a case where a unicodeRange related error would be thrown when using the experimental fonts API

`v5.7.7`

Compare Source

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

#13773 3aa5337 Thanks @sijad! - Ignores lightningcss unsupported pseudo-class warning.
#13833 5a6d2ae Thanks @ascorbic! - Fixes an issue where session modules would fail to resolve in Node.js < 20.6
#13383 f7f712c Thanks @Haberkamp! - Stop toolbar settings from overflowing
#13794 85b19d8 Thanks @alexcarpenter! - Exclude pre tags from a11y-no-noninteractive-tabindex audit check.
#13373 50ef568 Thanks @jpwienekus! - Fixes a bug where highlights and tooltips render over the audit list window.
#13769 e9fc456 Thanks @romanstetsyk! - Expand ActionError codes to include all IANA-registered HTTP error codes.
#13668 866285a Thanks @sapphi-red! - Replaces internal CSS chunking behavior for Astro components' scoped styles to use Vite's cssScopeTo feature. The feature is a port of Astro's implementation so this should not change the behavior.

`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 [

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.

tatsutakeinjp-bot

Device	URL
mobile	https://7214fee4.asis-docs.pages.dev