chore(deps): update astro monorepo #77

renovate · 2025-05-21T20:36:14Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/check (source)	`0.9.4` → `0.9.6`
@astrojs/mdx (source)	`4.3.0` → `4.3.13`
@astrojs/rss (source)	`4.0.12` → `4.0.15`
@astrojs/sitemap (source)	`3.4.1` → `3.7.0`
astro (source)	`5.9.0` → `5.17.0`

Release Notes

withastro/astro (@astrojs/check)

`v0.9.6`

Patch Changes

#14740 abfed97 Thanks @ArmandPhilippot! - Fixes link targets in documentation following repository relocation.
Updated dependencies [abfed97]:
- @astrojs/language-server@2.16.1

`v0.9.5`

Patch Changes

d415d4e: When no errors or warnings are detected, display "0 errors" or "0 warnings" in a dimmed color on the console instead of red or yellow.

withastro/astro (@astrojs/mdx)

Patch Changes

#14813 e1dd377 Thanks @ematipico! - Removes picocolors as dependency in favor of the fork piccolore.

`v4.3.11`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.9

`v4.3.10`

Compare Source

Patch Changes

#14715 3d55c5d Thanks @ascorbic! - Adds support for client hydration in getContainerRenderer()

The getContainerRenderer() function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint.

See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

`v4.3.9`

Patch Changes

#14621 e3175d9 Thanks @GameRoMan! - Updates vite version to fix CVE

`v4.3.8`

Patch Changes

#14591 3e887ec Thanks @matthewp! - Adds TypeScript support for the components prop on MDX Content component when using await render(). Developers now get proper IntelliSense and type checking when passing custom components to override default MDX element rendering.
#14598 7b45c65 Thanks @delucis! - Reduces terminal text styling dependency size by switching from kleur to picocolors

`v4.3.7`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.8

`v4.3.6`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.7

`v4.3.5`

Compare Source

Patch Changes

#14326 c24a8f4 Thanks @jsparkdev! - Updates vite version to fix CVE

`v4.3.4`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.6

`v4.3.3`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.5

`v4.3.2`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.4

`v4.3.1`

Compare Source

Patch Changes

Updated dependencies [6bd5f75]:
- @astrojs/markdown-remark@6.3.3

withastro/astro (@astrojs/rss)

`v4.0.15`

Compare Source

Patch Changes

#15199 d8e64ef Thanks @ArmandPhilippot! - Fixes the links to Astro Docs so that they match the current docs structure.

`v4.0.14`

Compare Source

Patch Changes

#14813 e1dd377 Thanks @ematipico! - Removes picocolors as dependency in favor of the fork piccolore.

`v4.0.13`

Compare Source

Patch Changes

#14598 7b45c65 Thanks @delucis! - Reduces terminal text styling dependency size by switching from kleur to picocolors

withastro/astro (@astrojs/sitemap)

`v3.7.0`

Compare Source

Minor Changes

#14471 4296373 Thanks @Slackluky! - Adds the ability to split sitemap generation into chunks based on customizable logic. This allows for better management of large sitemaps and improved performance. The new chunks option in the sitemap configuration allows users to define functions that categorize sitemap items into different chunks. Each chunk is then written to a separate sitemap file.

integrations: [
  sitemap({
    serialize(item) { th
      return item
    },
    chunks: { // this property will be treated last on the configuration
      'blog': (item) => {  // will produce a sitemap file with `blog` name (sitemap-blog-0.xml)
        if (/blog/.test(item.url)) { // filter path that will be included in this specific sitemap file
          item.changefreq = 'weekly';
          item.lastmod = new Date();
          item.priority = 0.9; // define specific properties for this filtered path
          return item;
        }
      },
      'glossary': (item) => {
        if (/glossary/.test(item.url)) {
          item.changefreq = 'weekly';
          item.lastmod = new Date();
          item.priority = 0.7;
          return item;
        }
      }

      // the rest of the path will be stored in `sitemap-pages.0.xml`
    },
  }),
],

`v3.6.1`

Compare Source

Patch Changes

#15033 dd06779 Thanks @florian-lefebvre! - Updates how routes are retrieved to avoid relying on a deprecated API

`v3.6.0`

Compare Source

Minor Changes

#14285 bedc31b Thanks @jdcolombo! - Adds a new configuration option namespaces for more control over XML namespaces used in sitemap generation

Excluding unused namespaces can help create cleaner, more focused sitemaps that are faster for search engines to parse and use less bandwidth. If your site doesn't have news content, videos, or multiple languages, you can exclude those namespaces to reduce XML bloat.

The namespaces option allows you to configure news, xhtml, image, and video namespaces independently. All namespaces are enabled by default for backward compatibility and no change to existing projects is necessary. But now, you can choose to streamline your XML and avoid unnecessary code.

For example, to exclude the video namespace from your sitemap, set video: false in your configuration:
```
// astro.config.mjs
import { sitemap } from '@&#8203;astrojs/sitemap';

export default {
  integrations: [
    sitemap({
      namespaces: {
        video: false,
        // other namespaces remain enabled by default
      }
    })
  ]
};
```
The generated XML will not include the xmlns:video namespace:
```
<?xml version="1.0" encoding="UTF-8"?>
<urlset
  xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
  xmlns:news="http://www.google.com/schemas/sitemap-news/0.9"
  xmlns:xhtml="http://www.w3.org/1999/xhtml"
  xmlns:image="http://www.google.com/schemas/sitemap-image/1.1"
>
  
</urlset>
```

`v3.5.1`

Compare Source

Patch Changes

#14233 896886c Thanks @gouravkhunger! - Fixes the issue with the option lastmod where if it is defined it applies correctly to <url> entries in each sitemap-${i}.xml file but not the <sitemap> entries in the root sitemap-index.xml file.

`v3.5.0`

Compare Source

Minor Changes

#13682 5824b32 Thanks @gouravkhunger! - Adds a customSitemaps option to include extra sitemaps in the sitemap-index.xml file generated by Astro.

This is useful for multi-framework setups on the same domain as your Astro site (example.com), such as a blog at example.com/blog whose sitemap is generated by another framework.

The following example shows configuring your Astro site to include sitemaps for an externally-generated blog and help center along with the generated sitemap entries in sitemap-index.xml:

Example:
```
import { defineConfig } from 'astro/config';
import sitemap from '@&#8203;astrojs/sitemap';

export default defineConfig({
  site: 'https://example.com',
  integrations: [
    sitemap({
      customSitemaps: [
        'https://example.com/blog/sitemap.xml',
        'https://example.com/helpcenter/sitemap.xml',
      ],
    }),
  ],
});
```
Learn more in the @astrojs/sitemap configuration documentation.

`v3.4.2`

Compare Source

Patch Changes

#14127 2309ada Thanks @florian-lefebvre! - Upgrades zod

withastro/astro (astro)

`v5.17.0`

Compare Source

Minor Changes

#14932 b19d816 Thanks @patrickarlt! - Adds support for returning a Promise from the parser() option of the file() loader

This enables you to run asynchronous code such as fetching remote data or using async parsers when loading files with the Content Layer API.

For example:

import { defineCollection } from 'astro:content';
import { file } from 'astro/loaders';

const blog = defineCollection({
  loader: file('src/data/blog.json', {
    parser: async (text) => {
      const data = JSON.parse(text);

      // Perform async operations like fetching additional data
      const enrichedData = await fetch(`https://api.example.com/enrich`, {
        method: 'POST',
        body: JSON.stringify(data),
      }).then((res) => res.json());

      return enrichedData;
    },
  }),
});

export const collections = { blog };

See the parser() reference documentation for more information.

#15171 f220726 Thanks @mark-ignacio! - Adds a new, optional kernel configuration option to select a resize algorithm in the Sharp image service

By default, Sharp resizes images with the lanczos3 kernel. This new config option allows you to set the default resizing algorithm to any resizing option supported by Sharp (e.g. linear, mks2021).

Kernel selection can produce quite noticeable differences depending on various characteristics of the source image - especially drawn art - so changing the kernel gives you more control over the appearance of images on your site:
```
export default defineConfig({
  image: {
    service: {
      entrypoint: 'astro/assets/services/sharp',
      config: {
        kernel: "mks2021"
      }
  }
})
```
This selection will apply to all images on your site, and is not yet configurable on a per-image basis. For more information, see Sharps documentation on resizing images.
#15063 08e0fd7 Thanks @jmortlock! - Adds a new partitioned option when setting a cookie to allow creating partitioned cookies.

Partitioned cookies can only be read within the context of the top-level site on which they were set. This allows cross-site tracking to be blocked, while still enabling legitimate uses of third-party cookies.

You can create a partitioned cookie by passing partitioned: true when setting a cookie. Note that partitioned cookies must also be set with secure: true:
```
Astro.cookies.set('my-cookie', 'value', {
  partitioned: true,
  secure: true,
});
```
For more information, see the AstroCookieSetOptions API reference.
#15022 f1fce0e Thanks @ascorbic! - Adds a new retainBody option to the glob() loader to allow reducing the size of the data store.

Currently, the glob() loader stores the raw body of each content file in the entry, in addition to the rendered HTML.

The retainBody option defaults to true, but you can set it to false to prevent the raw body of content files from being stored in the data store. This significantly reduces the deployed size of the data store and helps avoid hitting size limits for sites with very large collections.

The rendered body will still be available in the entry.rendered.html property for markdown files, and the entry.filePath property will still point to the original file.
```
import { defineCollection } from 'astro:content';
import { glob } from 'astro/loaders';

const blog = defineCollection({
  loader: glob({
    pattern: '**/*.md',
    base: './src/content/blog',
    retainBody: false,
  }),
});
```
When retainBody is false, entry.body will be undefined instead of containing the raw file contents.
#15153 928529f Thanks @jcayzac! - Adds a new background property to the <Image /> component.

This optional property lets you pass a background color to flatten the image with. By default, Sharp uses a black background when flattening an image that is being converted to a format that does not support transparency (e.g. jpeg). Providing a value for background on an <Image /> component, or passing it to the getImage() helper, will flatten images using that color instead.

This is especially useful when the requested output format doesn't support an alpha channel (e.g. jpeg) and can't support transparent backgrounds.
```
---
import { Image } from 'astro:assets';
---

<Image
  src="/transparent.png"
  alt="A JPEG with a white background!"
  format="jpeg"
  background="#ffffff"
/>
```
See more about this new property in the image reference docs
#15015 54f6006 Thanks @tony! - Adds optional placement config option for the dev toolbar.

You can now configure the default toolbar position ('bottom-left', 'bottom-center', or 'bottom-right') via devToolbar.placement in your Astro config. This option is helpful for sites with UI elements (chat widgets, cookie banners) that are consistently obscured by the toolbar in the dev environment.

You can set a project default that is consistent across environments (e.g. dev machines, browser instances, team members):
```
// astro.config.mjs
export default defineConfig({
  devToolbar: {
    placement: 'bottom-left',
  },
});
```
User preferences from the toolbar UI (stored in localStorage) still take priority, so this setting can be overridden in individual situations as necessary.

`v5.16.16`

Compare Source

Patch Changes

#15281 a1b80c6 Thanks @matthewp! - Ensures server island requests carry an encrypted component export identifier so they do not accidentally resolve to the wrong component.
#15304 02ee3c7 Thanks @cameronapak! - Fix: Remove await from getActionResult example
#15324 ab41c3e Thanks @Princesseuh! - Fixes an issue where certain unauthorized links could be rendered as clickable in the error overlay

`v5.16.15`

Compare Source

Patch Changes

#15286 0aafc83 Thanks @florian-lefebvre! - Fixes a case where font providers provided as class instances may not work when using the experimental Fonts API. It affected the local provider

`v5.16.14`

Compare Source

Patch Changes

#15213 c775fce Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Updates how the local provider must be used when using the experimental Fonts API

Previously, there were 2 kinds of font providers: remote and local.

Font providers are now unified. If you are using the local provider, the process for configuring local fonts must be updated:

-import { defineConfig } from "astro/config";
+import { defineConfig, fontProviders } from "astro/config";

export default defineConfig({
    experimental: {
        fonts: [{
            name: "Custom",
            cssVariable: "--font-custom",
-            provider: "local",
+            provider: fontProviders.local(),
+            options: {
            variants: [
                {
                    weight: 400,
                    style: "normal",
                    src: ["./src/assets/fonts/custom-400.woff2"]
                },
                {
                    weight: 700,
                    style: "normal",
                    src: ["./src/assets/fonts/custom-700.woff2"]
                }
                // ...
            ]
+            }
        }]
    }
});

Once configured, there is no change to using local fonts in your project. However, you should inspect your deployed site to confirm that your new font configuration is being applied.

See the experimental Fonts API docs for more information.

#15213 c775fce Thanks @florian-lefebvre! - Exposes root on FontProvider init() context

When building a custom FontProvider for the experimental Fonts API, the init() method receives a context. This context now exposes a root URL, useful for resolving local files:
```
import type { FontProvider } from "astro";

export function registryFontProvider(): FontProvider {
  return {
    // ...
-    init: async ({ storage }) => {
+    init: async ({ storage, root }) => {
        // ...
    },
  };
}
```
#15185 edabeaa Thanks @EricGrill! - Add .vercel to .gitignore when adding the Vercel adapter via astro add vercel

`v5.16.13`

Compare Source

Patch Changes

#15182 cb60ee1 Thanks @florian-lefebvre! - Adds a new getFontBuffer() method to retrieve font file buffers when using the experimental Fonts API

The getFontData() helper function from astro:assets was introduced in 5.14.0 to provide access to font family data for use outside of Astro. One of the goals of this API was to be able to retrieve buffers using URLs.

However, it turned out to be impactical and even impossible during prerendering.

Astro now exports a new getFontBuffer() helper function from astro:assets to retrieve font file buffers from URL returned by getFontData(). For example, when using satori to generate OpenGraph images:

// src/pages/og.png.ts

import type{ APIRoute } from "astro"
-import { getFontData } from "astro:assets"
+import { getFontData, getFontBuffer } from "astro:assets"
import satori from "satori"

export const GET: APIRoute = (context) => {
  const data = getFontData("--font-roboto")

  const svg = await satori(
    <div style={{ color: "black" }}>hello, world</div>,
    {
      width: 600,
      height: 400,
      fonts: [
        {
          name: "Roboto",
-          data: await fetch(new URL(data[0].src[0].url, context.url.origin)).then(res => res.arrayBuffer()),
+          data: await getFontBuffer(data[0].src[0].url),
          weight: 400,
          style: "normal",
        },
      ],
    },
  )

  // ...
}

See the experimental Fonts API documentation for more information.

`v5.16.12`

Compare Source

Patch Changes

#15175 47ae148 Thanks @florian-lefebvre! - Allows experimental Font providers to specify family options

Previously, an Astro FontProvider could only accept options at the provider level when called. That could result in weird data structures for family-specific options.

Astro FontProviders can now declare family-specific options, by specifying a generic:

// font-provider.ts
import type { FontProvider } from "astro";
import { retrieveFonts, type Fonts } from "./utils.js",

interface Config {
  token: string;
}

+interface FamilyOptions {
+    minimal?: boolean;
+}

-export function registryFontProvider(config: Config): FontProvider {
+export function registryFontProvider(config: Config): FontProvider<FamilyOptions> {
  let data: Fonts = {}

  return {
    name: "registry",
    config,
    init: async () => {
      data = await retrieveFonts(token);
    },
    listFonts: () => {
      return Object.keys(data);
    },
-    resolveFont: ({ familyName, ...rest }) => {
+    // options is typed as FamilyOptions
+    resolveFont: ({ familyName, options, ...rest }) => {
      const fonts = data[familyName];
      if (fonts) {
        return { fonts };
      }
      return undefined;
    },
  };
}

Once the font provider is registered in the Astro config, types are automatically inferred:

// astro.config.ts
import { defineConfig } from "astro/config";
import { registryFontProvider } from "./font-provider";

export default defineConfig({
    experimental: {
        fonts: [{
            provider: registryFontProvider({
              token: "..."
            }),
            name: "Custom",
            cssVariable: "--font-custom",
+            options: {
+                minimal: true
+            }
        }]
    }
});

#15175 47ae148 Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Updates how options are passed to the Google and Google Icons font providers when using the experimental Fonts API

Previously, the Google and Google Icons font providers accepted options that were specific to given font families.

These options must now be set using the options property instead. For example using the Google provider:

import { defineConfig, fontProviders } from "astro/config";

export default defineConfig({
    experimental: {
        fonts: [{
            name: 'Inter',
            cssVariable: '--astro-font-inter',
            weights: ['300 900'],
-            provider: fontProviders.google({
-                experimental: {
-                    variableAxis: {
-                        Inter: { opsz: ['14..32'] }
-                    }
-                }
-            }),
+            provider: fontProviders.google(),
+            options: {
+                experimental: {
+                    variableAxis: { opsz: ['14..32'] }
+                }
+            }
        }]
    }
})

#15200 c0595b3 Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Removes getFontData() exported from astro:assets with fontData when using the experimental Fonts API

Accessing font data can be useful for advanced use cases, such as generating meta tags or Open Graph images. Before, we exposed a getFontData() helper function to retrieve the font data for a given cssVariable. That was however limiting for programmatic usages that need to access all font data.

The getFontData() helper function is removed and replaced by a new fontData object:
```
-import { getFontData } from "astro:assets";
-const data = getFontData("--font-roboto")

+import { fontData } from "astro:assets";
+const data = fontData["--font-roboto"]
```
We may reintroduce getFontData() later on for a more friendly DX, based on your feedback.
#15254 8d84b30 Thanks @lamalex! - Fixes CSS assetsPrefix with remote URLs incorrectly prepending a forward slash

When using build.assetsPrefix with a remote URL (e.g., https://cdn.example.com) for CSS assets, the generated <link> elements were incorrectly getting a / prepended to the full URL, resulting in invalid URLs like /https://cdn.example.com/assets/style.css.

This fix checks if the stylesheet link is a remote URL before prepending the forward slash.
#15178 731f52d Thanks @kedarvartak! - Fixes an issue where stopping the dev server with q+enter incorrectly created a dist folder and copied font files when using the experimental Fonts API
#15230 3da6272 Thanks @rahuld109! - Fixes greedy regex in error message markdown rendering that caused link syntax examples to capture extra characters
#15253 2a6315a Thanks @matthewp! - Fixes hydration for React components nested inside HTML elements in MDX files
#15227 9a609f4 Thanks @matthewp! - Fixes styles not being included for conditionally rendered Svelte 5 components in production builds
#14607 ee52160 Thanks @simensfo! - Reintroduces css deduplication for hydrated client components. Ensures assets already added to a client chunk are not flagged as orphaned

`v5.16.11`

Compare Source

Patch Changes

#15017 9e7a3c8 Thanks @ixchio! - Fixes CSS double-bundling when the same CSS file is imported in both a page's frontmatter and a component's script tag
#15225 6fe62e1 Thanks @ematipico! - Updates to the latest version of devalue

`v5.16.10`

Compare Source

Patch Changes

2fa19c4 - Improved error handling in the rendering phase

Added defensive validation in App.render() and #renderError() to provide a descriptive error message when a route module doesn't have a valid page function.
#15199 d8e64ef Thanks @ArmandPhilippot! - Fixes the links to Astro Docs so that they match the current docs structure.
#15169 b803d8b Thanks @rururux! - fix: fix image 500 error when moving dist directory in standalone Node
#14622 9b35c62 Thanks @aprici7y! - Fixes CSS url() references to public assets returning 404 in dev mode when base path is configured
#15219 43df4ce Thanks @matthewp! - Upgrades the diff package to v8

`v5.16.9`

Compare Source

Patch Changes

#15174 37ab65a Thanks @florian-lefebvre! - Adds Google Icons to built-in font providers

To start using it, access it on fontProviders:

import { defineConfig, fontProviders } from 'astro/config';

export default defineConfig({
  experimental: {
    fonts: [
      {
        name: 'Material Symbols Outlined',
        provider: fontProviders.googleicons(),
        cssVariable: '--font-material',
      },
    ],
  },
});

#15150 a77c4f4 Thanks @matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.
#15130 9b726c4 Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Changes how font providers are implemented with updates to the FontProvider type

This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

What should I do?

If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

// astro.config.ts
import { defineConfig } from "astro/config";
import { acmeProvider, type AcmeOptions } from '@&#8203;acme/unifont-provider'
+import type { FontProvider } from "astro";
+import type { InitializedProvider } from 'unifont';

+function acme(config?: AcmeOptions): FontProvider {
+	const provider = acmeProvider(config);
+	let initializedProvider: InitializedProvider | undefined;
+	return {
+		name: provider._name,
+		config,
+		async init(context) {
+			initializedProvider = await provider(context);
+		},
+		async resolveFont({ familyName, ...rest }) {
+			return await initializedProvider?.resolveFont(familyName, rest);
+		},
+		async listFonts() {
+			return await initializedProvider?.listFonts?.();
+		},
+	};
+}

export default defineConfig({
    experimental: {
        fonts: [{
-            provider: acmeProvider({ /* ... */ }),
+            provider: acme({ /* ... */ }),
            name: "Material Symbols Outlined",
            cssVariable: "--font-material"
        }]
    }
});

#15147 9cd5b87 Thanks @matthewp! - Fixes scripts in components not rendering when a sibling <Fragment slot="..."> exists but is unused

`v5.16.8`

Compare Source

Patch Changes

#15124 81db3c0 Thanks @leonace924! - Fixes an issue where requests with query parameters to the base path would return a 404 if trailingSlash was not 'ignore' in development
#15152 39ee41f Thanks @rururux! - Fixes a case where context.cookies.set() would be overriden when setting cookies via response headers in development
#15140 6f6f8f8 Thanks @cameronraysmith! - Fixes esbuild warning due to dead code in assets virtual module
#15127 2cff904 Thanks @Princesseuh! - Updates "Unsupported page types found" error to only appear in more realistic cases
#15149 34f84c2 Thanks @rahuld109! - Skips "Use the Image component" audit warning for images inside framework components (React, Vue, Svelte, etc.)

`v5.16.7`

Compare Source

Patch Changes

#15122 b137946 Thanks @florian-lefebvre! - Improves JSDoc annotations for AstroGlobal, AstroSharedContext and APIContext types
#15123 3f58fa2 Thanks @43081j! - Improves rendering performance by grouping render chunks when emitting from async iterables to avoid encoding costs
#14954 7bec4bd Thanks @volpeon! - Fixes remote images Etag header handling by disabling internal cache
#15052 b2bcd5a Thanks @Princesseuh! - Fixes images not working in development when using setups with port forwarding
#15028 87b19b8 Thanks @Princesseuh! - Fixes certain aliases not working when using images in JSON files with the content layer

#15118 cfa382b Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Removes the defineAstroFontProvider() type helper.

If you are building a custom font provider, remove any occurrence of defineAstroFontProvider() and use the FontProvider type instead:

-import { defineAstroFontProvider } from 'astro/config';

-export function myProvider() {
-    return defineAstroFontProvider({
-        entrypoint: new URL('./implementation.js', import.meta.url)
-    });
-};

+import type { FontProvider } from 'astro';

+export function myProvider(): FontProvider {
+    return {
+        entrypoint: new URL('./implementation.js', import.meta.url)
+    },
+}

#15055 4e28db8 Thanks @delucis! - Reduces Astro’s install size by around 8 MB
#15088 a19140f Thanks @martrapp! - Enables the ClientRouter to preserve the original hash part of the target URL during server side redirects.
#15117 b1e8e32 Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Changes the font format downloaded by default when using the experimental Fonts API. Additionally, adds a new formats configuration option to specify which font formats to download.

Previously, Astro was opinionated about which font sources would be kept for usage, mainly keeping woff2 and woff files.

You can now specify what font formats should be downloaded (if available). Only woff2 files are downloaded by default.

What should I do?

If you were previously relying on Astro downloading the woff format, you will now need to specify this explicitly with the new formats configuration option. Additionally, you may also specify any additional file formats to download if available:

// astro.config.mjs
import { defineConfig, fontProviders } from 'astro/config'

export default defineConfig({
    experimental: {
        fonts: [{
            name: 'Roboto',
            cssVariable: '--font-roboto',
            provider: fontProviders.google(),
+            formats: ['woff2', 'woff', 'otf']
        }]
    }
})

#15034 8115752 Thanks @florian-lefebvre! - Fixes a vite warning log during builds when using npm

`v5.16.6`

Compare Source

Patch Changes

#14982 6849e38 Thanks @Princesseuh! - Fixes images outside the project directory not working when using astro:assets in development mode
#14987 9dd9fca Thanks @Princesseuh! - Fixes SVGs not working in dev mode when using the passthrough

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

changeset-bot · 2025-05-21T20:36:18Z

⚠️ No Changeset found

Latest commit: 5e7227f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

codecov · 2025-05-21T20:36:58Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 31.74%. Comparing base (3edf8a5) to head (a6f709a).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #77   +/-   ##
=======================================
  Coverage   31.74%   31.74%           
=======================================
  Files          10       10           
  Lines         419      419           
  Branches       22       22           
=======================================
  Hits          133      133           
  Misses        281      281           
  Partials        5        5

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

renovate bot force-pushed the renovate/astro-monorepo branch from 8b62004 to 3b816ac Compare May 22, 2025 16:35

renovate bot changed the title ~~fix(deps): update dependency astro to v5.7.14~~ fix(deps): update astro monorepo May 22, 2025

renovate bot changed the title ~~fix(deps): update astro monorepo~~ fix(deps): update astro monorepo - autoclosed May 22, 2025

renovate bot closed this May 22, 2025

renovate bot deleted the renovate/astro-monorepo branch May 22, 2025 17:38

renovate bot changed the title ~~fix(deps): update astro monorepo - autoclosed~~ fix(deps): update astro monorepo May 29, 2025

renovate bot reopened this May 29, 2025

renovate bot force-pushed the renovate/astro-monorepo branch from f56dcfc to 3b816ac Compare May 29, 2025 14:59

renovate bot changed the title ~~fix(deps): update astro monorepo~~ fix(deps): update dependency astro to v5.8.1 May 29, 2025

renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from 089abc6 to 9de2c2d Compare June 4, 2025 12:24

renovate bot changed the title ~~fix(deps): update dependency astro to v5.8.1~~ fix(deps): update astro monorepo Jun 4, 2025

renovate bot changed the title ~~fix(deps): update astro monorepo~~ fix(deps): update astro monorepo - autoclosed Jun 5, 2025

renovate bot closed this Jun 5, 2025

renovate bot changed the title ~~fix(deps): update astro monorepo - autoclosed~~ fix(deps): update astro monorepo Jun 7, 2025

renovate bot reopened this Jun 7, 2025

renovate bot force-pushed the renovate/astro-monorepo branch from 828c13b to 9de2c2d Compare June 7, 2025 09:08

renovate bot changed the title ~~fix(deps): update astro monorepo~~ fix(deps): update dependency astro to v5.9.1 Jun 7, 2025

renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from 71e77f5 to 185d905 Compare June 9, 2025 19:35

renovate bot changed the title ~~fix(deps): update dependency astro to v5.9.1~~ fix(deps): update dependency astro to v5.9.2 Jun 9, 2025

renovate bot force-pushed the renovate/astro-monorepo branch from 185d905 to 3bfa26b Compare June 15, 2025 08:14

renovate bot changed the title ~~fix(deps): update dependency astro to v5.9.2~~ fix(deps): update dependency astro to v5.9.3 Jun 15, 2025

renovate bot force-pushed the renovate/astro-monorepo branch from 3bfa26b to 9dc1970 Compare June 17, 2025 12:56

renovate bot changed the title ~~fix(deps): update dependency astro to v5.9.3~~ fix(deps): update dependency astro to v5.9.4 Jun 17, 2025

renovate bot force-pushed the renovate/astro-monorepo branch from 9dc1970 to 72e873c Compare June 19, 2025 14:58

renovate bot changed the title ~~fix(deps): update dependency astro to v5.9.4~~ fix(deps): update dependency astro to v5.10.0 Jun 19, 2025

renovate bot force-pushed the renovate/astro-monorepo branch from 72e873c to d2401bc Compare June 22, 2025 14:51

renovate bot force-pushed the renovate/astro-monorepo branch 5 times, most recently from c0c85fa to b986935 Compare November 15, 2025 17:27

renovate bot force-pushed the renovate/astro-monorepo branch 3 times, most recently from 2addfbb to 20c269f Compare November 20, 2025 13:55

renovate bot force-pushed the renovate/astro-monorepo branch 4 times, most recently from 934a535 to 6279b8e Compare November 29, 2025 19:48

renovate bot force-pushed the renovate/astro-monorepo branch from 6279b8e to 84b54d0 Compare December 3, 2025 17:45

renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from ed96709 to fe04031 Compare December 16, 2025 12:42

renovate bot force-pushed the renovate/astro-monorepo branch from fe04031 to bdae410 Compare December 31, 2025 13:00

renovate bot force-pushed the renovate/astro-monorepo branch 4 times, most recently from c5730f7 to b2da497 Compare January 12, 2026 18:12

renovate bot force-pushed the renovate/astro-monorepo branch 6 times, most recently from 2161a0e to cbbea65 Compare January 22, 2026 21:25

renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from 27209eb to 8b6844b Compare January 28, 2026 17:28

chore(deps): update astro monorepo

5e7227f

renovate bot force-pushed the renovate/astro-monorepo branch from 8b6844b to 5e7227f Compare January 29, 2026 14:01

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update astro monorepo #77

chore(deps): update astro monorepo #77

renovate bot commented May 21, 2025 •

edited

Loading

Uh oh!

changeset-bot bot commented May 21, 2025 •

edited

Loading

Uh oh!

codecov bot commented May 21, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

chore(deps): update astro monorepo #77

Are you sure you want to change the base?

chore(deps): update astro monorepo #77

Conversation

renovate bot commented May 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

What should I do?

Patch Changes

Patch Changes

What should I do?

Patch Changes

Configuration

Uh oh!

changeset-bot bot commented May 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

codecov bot commented May 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented May 21, 2025 •

edited

Loading

changeset-bot bot commented May 21, 2025 •

edited

Loading

codecov bot commented May 21, 2025 •

edited

Loading