This PR significantly improves Starlight performance by implementing lazy loading for two major bundles that previously impacted initial load times and rendering metrics:

1. Lazy Load Starlight Built-in Translations: (Commit 89a0c52) Moved from eager to lazy loading for built-in translation JSON files. Only English is loaded by default for type inference and as a fallback, while other languages are dynamically imported only when required by the project locale. This reduces the server-side memory footprint and the size of the initial localization bundle.

2. Lazy Load Pagefind UI: Optimized the Search.astro component to defer the loading of the @pagefind/default-ui bundle (~73kB). Previously loaded on DOMContentLoaded, it now loads only when a user first interacts with the search button or shortcut (Ctrl+K). A prefetch hint has been added to ensure the search UI remains responsive when needed.

What does this PR change? Implements on-demand loading for Starlight translations and the Pagefind search interface to optimize Core Web Vitals.

Did you change something visual? No. The UI remains identical, but the background loading logic is now significantly more efficient.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.16.16

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.

Changes

This updates a JSDoc comment to remove the await keyword on Astro.getActionResult since it doesn't return a promise.

I came upon this small issue when using intellsense for the Astro.getActionResult and saw that it said await but in the docs it didn't have an await.

Testing

There is no need for testing since this is a JSDoc update.

Docs

No docs needed. This change makes the JSDoc for the getActionResult function congruent with the docs: https://docs.astro.build/en/reference/api-reference/#getactionresult

This PR contains the following updates:

Package	Change	Age	Confidence
@playwright/test (source)	1.57.0 → 1.58.0
@preact/signals (source)	^2.5.1 → ^2.6.1
htmlparser2	^10.0.0 → ^10.1.0
prettier (source)	^3.8.0 → ^3.8.1
publint (source)	^0.3.16 → ^0.3.17
sass	^1.97.2 → ^1.97.3
svelte (source)	^5.46.1 → ^5.48.0
typescript-eslint (source)	^8.53.0 → ^8.53.1
unist-util-visit	^5.0.0 → ^5.1.0
vue (source)	^3.5.26 → ^3.5.27

Release Notes

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

Changes

This PR changes the sponsors to reflect our current top sponsors in alphabetical order.

Testing

Docs

Changes

This PR addresses #15271 adding an optional embeddedLangs prop to <Code /> :

• Previously, <Code /> creates a shiki highlighter with langs: [lang].
• This usually works great. Embedded langs are already included in canonical situations like ts-in-svelte without a need for additional langs.
• But in some less canonical cases e.g. tsx-in-vue, more control is needed over the langs param for shiki to correctly highlight
• Now shiki highlighter is created with langs: [lang, ...embeddedLangs]

Testing

• Create fixture using TSX in Vue
• Without langs support, setting lang to "vue" results in the main line of TSX being one long <span />.
• With langs support, each TSX token is its own <span />
• Test for a <span /> containing the lone string "const"

Docs

Docs will need an update here (can I do this for en? Would I submit an issue there first or just a PR?)
/cc @withastro/maintainers-docs

fixes: #13400

Changes

I removed the is:raw attribute from the code generated by the rehype-prism plugin.
Summary of Comment: #13400 (comment)

• The is:raw attribute is handled within @astrojs/compiler.

• @astrojs/compiler is used within astroVitePlugin.

• Subsequent plugins do not use @astrojs/compiler. (Search results for the compile function using transform imported from @astrojs/compiler)

• The markdownVitePlugin, which uses the rehype-prism plugin, is configured after astroVitePlugin.

• Consequently, this causes the is:raw attribute added by markdownVitePlugin to remain unchanged until the end.

Testing

I added a test to verify that the is:raw attribute is not included in the post-build code.

Docs

N/A

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

astro@6.0.0-beta.4

Patch Changes

• #15279 8983f17 Thanks @ematipico! - Fixes an issue where the dev server would serve files like /README.md from the project root when they shouldn't be accessible. A new route guard middleware now blocks direct URL access to files that exist outside of srcDir and publicDir, returning a 404 instead.

Changes

• Fixes #14353
• Prevents infinite loop in resolveClientDir() when server folder is not found
• Throws a descriptive error instead of hanging indefinitely

Testing

Existing tests pass.

Docs

N/A, bug fix

Changes

• What does this change?
• Be short and concise. Bullet points can help!
• Before/after screenshots can help as well.
• Don't forget a changeset! Run pnpm changeset.
• See https://contribute.docs.astro.build/docs-for-code-changes/changesets/ for more info on writing changesets.

Testing

Docs

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.16.15

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

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@astrojs/markdown-remark@7.0.0-beta.2

Minor Changes

• #15277 cb99214 Thanks @ematipico! - Fixes an issue where the function createShikiHighlighter would always create a new Shiki highlighter instance. Now the function returns a cached version of the highlighter based on the Shiki options. This should improve the performance for sites that heavily rely on Shiki and code in their pages.

Patch Changes

• Updated dependencies [11efb05]:
  • @astrojs/prism@4.0.0-beta.2

astro@6.0.0-beta.3

Patch Changes

• #15277 cb99214 Thanks @ematipico! - Fixes an issue where the function createShikiHighlighter would always create a new Shiki highlighter instance. Now the function returns a cached version of the highlighter based on the Shiki options. This should improve the performance for sites that heavily rely on Shiki and code in their pages.

• #15264 11efb05 Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22

• Updated dependencies [cb99214]:

  • @astrojs/markdown-remark@7.0.0-beta.2

@astrojs/prism@4.0.0-beta.2

Patch Changes

• #15264 11efb05 Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22

create-astro@5.0.0-beta.2

Patch Changes

• #15264 11efb05 Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22

@astrojs/markdoc@1.0.0-beta.5

Patch Changes

• #15264 11efb05 Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22

• Updated dependencies [cb99214, 11efb05]:

  • @astrojs/markdown-remark@7.0.0-beta.2
  • @astrojs/prism@4.0.0-beta.2

@astrojs/mdx@5.0.0-beta.2

Patch Changes

• #15264 11efb05 Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22

• Updated dependencies [cb99214]:

  • @astrojs/markdown-remark@7.0.0-beta.2

@astrojs/preact@5.0.0-beta.2

Patch Changes

• #15264 11efb05 Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22

@astrojs/react@5.0.0-beta.2

Patch Changes

• #15264 11efb05 Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22

@astrojs/solid-js@6.0.0-beta.2

Patch Changes

• #15264 11efb05 Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22

@astrojs/svelte@8.0.0-beta.1

Patch Changes

• #15264 11efb05 Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22

@astrojs/upgrade@0.7.0-beta.2

Patch Changes

• #15264 11efb05 Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22

Changes

• Reported by a user on Discord: TypeError: Cannot write private member #root to an object whose class did not declare it
• Zod remaps object but we want to keep the initial value instead, so that this remains valid

Testing

Manually + unit test

Docs

Changeset

Changes

Fix for #15282 and code piece was taken from zod4-final branch.

Changes

• Encrypts the componentExport prop in server islands.
• This is not a security issue, as you could only call other Astro components and would not be able to control the props. And only if the module is a barrel file.

Testing

• Updated tests

Docs

N/A, bug fix

Changes

• What does this change?
• Be short and concise. Bullet points can help!
• Before/after screenshots can help as well.
• Don't forget a changeset! Run pnpm changeset.
• See https://contribute.docs.astro.build/docs-for-code-changes/changesets/ for more info on writing changesets.

Testing

Docs

Changes

Closes #15273

This PR creates a new vite middleware that prevents the exposure of requests of files that are outside of publicDir and srcDir

I reviewed the code, and it seems fine.

Testing

Added new tests. CI should stay green

Docs

N/A

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.16.14

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

Changes

Found this bug when I was working with CSP and Shiki.

We weren't caching instances, leading to creating an highlighter for each code block, especially if the Code component was involved multiple times.

I could have sent this to main, but we're getting closer to freezing main, so preferred next.

Testing

CI should stay green

Docs

N/A

Changes

• What does this change?
• Be short and concise. Bullet points can help!
• Before/after screenshots can help as well.
• Don't forget a changeset! Run pnpm changeset.
• See https://contribute.docs.astro.build/docs-for-code-changes/changesets/ for more info on writing changesets.

Testing

Docs

Changes

• These files should not have been committed. That's because I had them on another branch where they were gitignored

Testing

N/A

Docs

N/A

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/db@0.19.0

Minor Changes

• #15069 d14dfc2 Thanks @webstackdev! - Adds a --db-app-token CLI flag to astro db commands execute, push, query, and verify

  The new Astro DB CLI flags allow you to provide a remote database app token directly instead of ASTRO_DB_APP_TOKEN. This ensures that no untrusted code (e.g. CI / CD workflows) has access to the secret that is only needed by the astro db commands.

  The following command can be used to safely push database configuration changes to your project database:

  astro db push --db-app-token <token>
  

  See the Astro DB integration documentation for more information.

astro@5.16.13

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.

Changes

Closes #15261

This PR fixes two bugs:

• serverEntry wasn't working with the new adapter entryType: 'self'. We didn't catch that because we don't test against the new adapter entry point kind.
• serverEntry stopped working with the CF adapter, mostly due to how the CF vite plugin now works under the hood. I don't like the fix, as explained in the PR, but I couldn't find a better way. Even adding entryFilesNames in the CF adapter couldn't work. Happy to receive advice here

Testing

I added a new testing adapter so that we can start testing against entryType: 'self'.

Added new tests to check things work as expected.

Docs

N/A

fixes: #14557
Image source for the polar bear: https://commons.wikimedia.org/wiki/File:Polar_Bear_-_Alaska_(cropped).jpg

Changes

Previously, there was an issue where unnecessary images were generated when using the Picture component. This PR fixes this issue to ensure only the required images are generated.

• Changed the <Picture> component to read properties from clonedSrc instead of originalSrc.
  • This avoids generating the file named image_HASH.jpg.
• Changed the src property of the getImage return value to a getter.
  • This ensures that the optimized image of the same size as the original is only generated when the src property is actually accessed.
• Behavioral examples:
  • When neither widths nor densities are set: Generates one WebP and one JPG each.
  • When widths is set: Generates WebP images equal to widths.length, and JPG images equal to widths.length + 1 for the fallback.
  • When densities is set: Generates densities.length + 1 images for both WebP and JPG.

Testing

I added tests to verify that the component behaves according to the examples described above.

Docs

I believe no documentation updates are necessary as this should not affect existing users.

Changes

• Extracted from #15145
• I don't think it's wise to include the types improvement in v6. It can occur in a minor as an experimental flag but to allow it, I need to make this breaking change for CSP
• Matching sessions, if CSP is not enabled, context.csp will be undefined instead of throwing when using one of its methods

Testing

Should pass

Docs

• Changeset
• withastro/docs#13079

Changes

• Astro 6 officially only supports Node 22
• Stackblitz is still on Node 20 so we relax the node version requirement for now
• However we required a too recent version of Node 20, so it lowers it to Stackblitz's version

Testing

N/A

Docs

Changeset, shouldn't be documented

Changes

• Explicitly add a favicon.ico reference for templates that previously relied on SVG-only favicons.
• Align default output with Google Search favicon guidelines to improve favicon visibility in search results.
• Prevent sites generated from SVG-only templates from appearing without any favicon in Google Search.

Fixes #15236

Testing

• Verified locally that the generated HTML includes an explicit <link rel="icon" href="/favicon.ico">.
• Confirmed that favicon.ico is correctly served from the root when present in public/.
• No automated tests were added since this change affects build output and external crawler behavior (Google Search), which cannot be reliably tested in CI.

Docs

• No documentation updates were required.

Changes

Closes #15234

The module astro:virtual:manifest wasn't correctly invalidated when new pages were added. With change, the manifest is refreshed when files change inside the srcDir.

Testing

I tested manually by adding new pages to examples/minimal, and made sure that I could see a blank page instead of 404.

CI should stay green

Docs

N/A

Changes

Closes #15194

The code was trying to run runner.import using the wrong vite environment. runner.import doesn't function when the environment is non-runnable. SSR is non-runnable when using the cloudflare vite plugin

Testing

Manually tested.

CI should stay green

Docs

N/A

Changes

• What does this change?
• Be short and concise. Bullet points can help!
• Before/after screenshots can help as well.
• Don't forget a changeset! Run pnpm changeset.
• See https://contribute.docs.astro.build/docs-for-code-changes/changesets/ for more info on writing changesets.

Testing

Docs

fixes: #15252

Changes

• 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), the generated <link> elements were getting a / prepended to the full URL
• Before: <link href="/https://cdn.example.com/_astro/style.css" rel="stylesheet">
• After: <link href="https://cdn.example.com/_astro/style.css" rel="stylesheet">
• The fix checks if the stylesheet link is a remote URL using isRemotePath() before calling prependForwardSlash()
• JavaScript assets with the same assetsPrefix configuration were unaffected - only CSS had this issue

Testing

Tested with a minimal reproduction: https://stackblitz.com/github/lamalex/astro-css-assetsprefix-bug

1. Created an Astro project with MDX and content collections
2. Configured build.assetsPrefix.css to https://cdn.example.com
3. Set build.inlineStylesheets: 'never' to force external CSS files
4. Built the project and verified CSS links now have the correct CDN URL without the leading /
5. Ran test/astro-assets-prefix.test.js and verified no breakage
6. Updated test/astro-assets-prefix.test.js.

Docs

No documentation changes needed - this is a bug fix that corrects behavior to match the existing documented assetsPrefix feature. The feature should now work as users expect based on current docs.

Changes

• Fix #15251
• Fix #15248

Testing

Adds a regression test for issue #15251 where React components with client:load nested inside HTML elements in MDX files fail to hydrate.

Docs

Changes

• What does this change?
• Be short and concise. Bullet points can help!
• Before/after screenshots can help as well.
• Don't forget a changeset! Run pnpm changeset.
• See https://contribute.docs.astro.build/docs-for-code-changes/changesets/ for more info on writing changesets.

Testing

Docs

Changes

• Merges main into next

Testing

• All tests passing

Docs

N/A

This PR contains the following updates:

Package	Change	Age	Confidence
prettier (source)	^3.7.4 → ^3.8.0

Release Notes

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/sitemap (source)	^3.6.1 → ^3.7.0
@cloudflare/workers-types	^4.20260109.0 → ^4.20260116.0
@vercel/routing-utils (source)	^5.3.1 → ^5.3.2
fastify (source)	^5.6.2 → ^5.7.0
wrangler (source)	4.58.0 → 4.59.2

Release Notes

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

This PR contains the following updates:

Package	Change	Age	Confidence
@libsql/client (source)	^0.15.15 → ^0.17.0
alpinejs (source)	^3.15.3 → ^3.15.4
preact (source)	^10.28.1 → ^10.28.2
prettier (source)	^3.7.4 → ^3.8.0
sass	^1.97.1 → ^1.97.2
shiki (source)	^3.20.0 → ^3.21.0
turbo (source)	^2.7.2 → ^2.7.4
typescript-eslint (source)	^8.51.0 → ^8.53.0

Release Notes

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

This PR contains the following updates:

Package	Change	Age	Confidence
@types/react (source)	^18.3.20 → ^18.3.27
@types/react-dom (source)	^18.3.6 → ^18.3.7
postcss-preset-env (source)	^10.6.0 → ^10.6.1
preact (source)	^10.28.1 → ^10.28.2
rollup (source)	^4.54.0 → ^4.55.1
sass	^1.97.1 → ^1.97.2
shiki (source)	^3.20.0 → ^3.21.0
undici (source)	^6.22.0 → ^6.23.0
unifont	~0.7.1 → ~0.7.3
unstorage (source)	^1.17.3 → ^1.17.4

Release Notes

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/svelte (source)	^7.2.4 → ^7.2.5
astro (source)	^5.16.6 → ^5.16.10
preact (source)	^10.28.1 → ^10.28.2
vue (source)	^3.5.13 → ^3.5.26

Release Notes

// astro.config.ts
import { defineConfig } from "astro/config";
import { acmeProvider, type AcmeOptions } from '@​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"
        }]
    }
});

// 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']
        }]
    }
})

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

Reverts #15108

See prettier/prettier-vscode#3899

Changes

• Add an option to override the default output format webp

Testing

Docs

Image component might need an update to state that the default value can be overridden.

Fix typo: to to → to in factory.ts

Changes

As discussed in the issue #14515 and #15067, the current implementation of inferRemoteSize had the problem of increased network traffic because it did not cache data.
To address this issue, I added a getRemoteSize property to the Image Service and implemented the publicly exposed inferRemoteSize API to utilize this property.
Additionally, for baseService's getRemoteSize, I configured a function that simply wraps the existing inferRemoteSize. This ensures no breaking changes occur for users who do not wish to see their behavior altered.

• Set getRemoteSize as an API of the Image Service.
• Modified the publicly exposed inferRemoteSize function to utilize the Image Service's getRemoteSize.
• Assigned the existing inferRemoteSize function to baseService's getRemoteSize. This prevents breaking changes and facilitates easy, lightweight extensions based on the existing implementation.

Testing

I implemented tests to verify that arbitrary processing can be configured and that delegation from baseService to the original inferRemoteSize is possible.

Docs

Since we are setting the existing inferRemoteSize as the default value, I don't believe this constitutes a breaking change. However, since we will be introducing a new property called getRemoteSize in the Image Service, I think the documentation will need to be updated.

/cc @withastro/maintainers-docs

As this is a PR introducing a new property, I would like to hear the opinions of the maintainers regarding this approach. Therefore, I will submit this PR as a draft for now.

Changes

• Fixed greedy regex in renderErrorMarkdown that caused markdown link examples in error messages to capture extra characters
• Changed linkRegex from /\[([^[]+)\]\((.*)\)/g to /\[([^[]+)\]\(([^)]*)\)/g
• The (.*) was capturing everything up to the last ) in the string instead of the first one after the URL

Root Cause

When an error message contained [text](url)</code>), the greedy (.*) incorrectly captured url)</code> as the URL, causing the rendered output to include escaped HTML in the href attribute (appearing as %3C/code%3E).

Process

1. Wrote tests first to verify the hypothesis - tests for renderErrorMarkdown covering link parsing edge cases
2. Ran tests to confirm they failed with the buggy regex
3. Applied the fix: changed (.*) to ([^)]*) to stop at the first )
4. Ran tests again - all passing

Closes #15068

Testing

Added 13 new unit tests for renderErrorMarkdown in packages/astro/test/units/errors/dev-utils.test.js:

• Basic markdown rendering (links, bold, code, URLs)
• Edge cases for links followed by other content
• Links inside parentheses
• Multiple links in same message
• Escaped HTML followed by link syntax

All 52 error unit tests pass.

Docs

No documentation changes needed - this is a bug fix for error message display.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.16.12

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

Changes

When Svelte 5 components are conditionally rendered (e.g., inside {#if} blocks with an initially false condition), their styles were not being included in production builds. This happened because:

1. Svelte 5.26+ added css.hasGlobal flag to compiler output
2. vite-plugin-svelte 5.1.0+ uses this to add cssScopeTo metadata
3. Vite 6.2+ cssScopeTo allows CSS treeshaking if the export isn't "used"

During SSR, conditionally rendered components aren't included in the server build (tree-shaken), but they are in the client build. Astro's CSS-to-page mapping primarily happens during the server build, so the CSS gets orphaned.

The fix adds logic in the client build's generateBundle to:

• Track which component exports are actually rendered (renderedComponentExports)
• For CSS modules with cssScopeTo metadata where the export IS rendered, walk up the module graph to find pages and ensure the CSS is included

Fixes #14252

Testing

Test case added based on the provided issue reproduction.

Docs

Bug fix

Changes

What the title says

Testing

N/A

Docs

N/A

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/starlight@0.37.4

Patch Changes

• #3534 703fab0 Thanks @HiDeoo! - Fixes support for running builds when npx is unavailable.

  Previously, Starlight would spawn a process to run the Pagefind search indexing binary using npx. On platforms where npx isn’t available, this could cause issues. Starlight now runs Pagefind using its Node.js API to avoid a separate process. As a side effect, you may notice that logging during builds is now less verbose.

• #3656 a0e6368 Thanks @delucis! - Fixes several edge cases in highlighting the current page heading in Starlight’s table of contents

• #3663 00cbf00 Thanks @lines-of-codes! - Adds Thai language support

• #3658 ac79329 Thanks @delucis! - Avoids adding redundant aria-current="false" attributes to sidebar entries

• #3382 db295c2 Thanks @trueberryless! - Fixes an issue where the mobile table of contents is unable to find the first heading when a page has a tall banner.

Description

This PR fixes handling of a boolean attribute in our sidebar code to avoid adding redundant aria-current="false" attributes. Before Astro v5, passing false to aria-current resulted in omitting the attribute in the HTML output. But since v5, this is now stringified to "false" (Astro only omits the attribute for officially boolean attributes in the HTML spec now).

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.16.11

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

Changes

Updates devalue to the latest

I commented minimumReleaseAge, installed the library, and uncommented it minimumReleaseAge

Testing

I believe I needed to add devalue to minimumReleaseAgeExclude so that it will be installed in fresh installs too, but I might be wrong.

CI should stay green.

Docs

N/A

This PR includes an addition of a link to a new Starlight community plugin.

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
svelte (source)	^4.2.20 → ^5.0.0
svelte (source)	5.46.1 → 5.46.4

GitHub Vulnerability Alerts

CVE-2025-15265

Summary

An XSS vulnerability exists in Svelte 5.46.0-2 resulting from improper escaping of hydratable keys. If these keys incorporate untrusted user input, arbitrary JavaScript can be injected into server-rendered HTML.

Details

When using the hydratable function, the first argument is used as a key to uniquely identify the data, such that the value is not regenerated in the browser.

This key is embedded into a <script> block in the server-rendered <head> without escaping unsafe characters. A malicious key can break out of the script context and inject arbitrary JavaScript into the HTML response.

Impact

This is a cross-site scripting vulnerability affecting applications that have the experimental.async flag enabled and use hydratable with keys incorporating untrusted user input.

• Impact: Arbitrary JS execution in the client’s browser.
• Exploitability: Remote, single-request if key is attacker-controlled.
• Typical Outcomes:
  • Session/token theft
  • DOM defacement
  • CSRF bypass via injected JS
  • Account takeover depending on cookie/session strategy

Affected applications should upgrade to a patched version immediately.

Release Notes

Configuration

📅 Schedule: Branch creation - "" (UTC), 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 these updates again.

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

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

Changes

• Upstream package that's now on version 8.
• Removed types dep since types are built-in now.

Testing

Tests should pass

Docs

N/A, bug fix

Changes

Format moved this comment, which broke the check

Testing

No errors in my editor

Docs

N/A

Description

This PR fixes an issue with Starlight’s intersection observer used for updating table of contents state, which we discovered while reviewing #3382 during Talking & Doc’ing today.

We found multiple issues:

• After we added anchor link support, headings in sites with this enabled are wrapped in a <div> breaking an assumption in the table of contents logic.
• After moving Markdown styles to an external CSS file, we renamed .content to .sl-markdown-content, but forgot to rename the same in a query selector here.

This caused some subtle issues that were not super obvious, but we noticed them while digging deeper.

This PR also adds some Playwright tests to make sure highlighting behaves as expected in the browser.

Changes

Fixed an issue where the internal timers weren't updated after the internal refactor.

Testing

Maybe with a review PR?

Docs

N/A

Changes

• Depends on #15175
• Updates the local provider to be a regular provider (see changeset for change), consistency FTW! This allows to simplify code and docs by a lot
• I used it as an opportunity to simplify fonts internals, thanks to the learnings of when we coded with Joe Rainsberger in December. I know the diff is massive so really it's not worth reviewing (altho it's doable), as long as the tests pass we're safe
• TLDR: unified API for font providers, removed some internal abstractions, more tests!

Testing

• Added a lot more tests for the core logic
• Added tests for some infra
• Added in memory e2e tests
• All other tests should pass

Docs

• local provider jsdoc
• Changesets
  • local provider breaking change
  • provider api init root
• RFC
• withastro/docs#13084

Adapters like Cloudflare, Netlify, and Node provide default session drivers, so users should be able to configure session options (like ttl) without explicitly specifying a driver.

Changes

• Fixes #15202
• Mostly this just uses .optional() in the schema.

Testing

Added test case to packages/astro/test/units/config/config-validate.test.js

Docs

N/A, bug fix

Changes

Removed a cyclic module dependency between router.js and event.js, which could explain the behavior observed in #15191.

While investigating why our existing end to end tests did not fail, I found that I could reproduce the issue with 6.0.0-beta.1, but not with the current tip of next.

Breaking the cycle seems still the right thing to do.

Closes #15191

Testing

We already have an e2e test for that case.

Docs

n.a.

Changes

• Depends on #15181
• At ViteConf, I got some feedback that getFontData() was a bit limiting. So this PR replaces it with fontData
• This change should affect very few users, as this is an advanced API

Testing

Updated

Docs

• Changeset
• withastro/docs#13047

Changes

This PR updates the version of @astrojs/check to fix its current versioning:

• On 10/20/2025, 0.9.5 was released.
• On 11/10/2025, 0.9.6-alpha.0 was released as part of the Astro v6 alpha.
• On 11/26/2025, 0.9.6 was released due to some changes in main.
• On 01/13/2026, 0.9.6-beta.1 was released yesterday as part of the Astro v6 beta.

This versioning goes backwards with 0.9.6-beta.1 having more recent changes than 0.9.6 and, when exiting beta, changesets will automatically try publishing 0.9.6 and skip it as it's already published on npm.

This PR does 2 things:

• Manually edit the package.json file version of @astrojs/check to 0.9.7-beta.0
• Add a patch changeset for this package

If my understanding is correct, this would mean that with the next release, it'll be published as 0.9.7-beta.1, and then when exiting beta, it'll be published as 0.9.7.

Testing

No testing; not aware of any testing possible for this.

Docs

This is a version fix; no doc updates are needed.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

astro@6.0.0-beta.2

Major Changes

• #15192 ada2808 Thanks @gameroman! - Removes support for CommonJS config files - (v6 upgrade guidance)

• #15266 f7c9365 Thanks @florian-lefebvre! - Allows Astro.csp and context.csp to be undefined instead of throwing errors when csp: true is not configured

  When using the experimental Content Security Policy feature in Astro 5.x, context.csp was always defined but would throw if experimental.csp was not enabled in the Astro config.

  For the stable version of this API in Astro 6, context.csp can now be undefined if CSP is not enabled and its methods will never throw.

  What should I do?

  If you were using experimental CSP runtime utilities, you must now access methods conditionally:

  -Astro.csp.insertDirective("default-src 'self'");
  +Astro.csp?.insertDirective("default-src 'self'");

Patch Changes

• #15208 8dbdd8e Thanks @matthewp! - Makes session.driver optional in config schema, allowing adapters to provide default drivers

  Adapters like Cloudflare, Netlify, and Node provide default session drivers, so users can now configure session options (like ttl) without explicitly specifying a driver.

• #15260 abca1eb Thanks @ematipico! - Fixes an issue where adding new pages weren't correctly shown when using the development server.

• #15214 6bab8c9 Thanks @ematipico! - Fixes an issue where the internal perfomance timers weren't correctly updated to reflect new build pipeline.

• #15259 8670a69 Thanks @ematipico! - Fixes an issue where styles weren't correctly reloaded when using the @astrojs/cloudflare adapter.

• #15205 12adc55 Thanks @martrapp! - Fixes an issue where the astro:page-load event did not fire on initial page loads.

• #15269 6f82aae Thanks @ematipico! - Fixes a regression where build.serverEntry stopped working as expected.

@astrojs/cloudflare@13.0.0-beta.1

Patch Changes

• #15269 6f82aae Thanks @ematipico! - Fixes a regression where build.serverEntry stopped working as expected.

• Updated dependencies []:

  • @astrojs/underscore-redirects@1.0.0

@astrojs/check@0.9.7-beta.1

Patch Changes

• #15198 55107a1 Thanks @HiDeoo! - Updates to Astro 6 beta

Changes

Closes #14625

This issue is weird. Somehow the tool wrk is able to send HTTP requests where the URL contains the # inside the type req.url. I believe this is a bug coming from wrk, because the hash inside the URL is a browser thing.

As for the fix, I didn't want to use the URL object on purpose to avoid too many changes, so I added a check for the # and stripped it out

Testing

Only manually, because our internal tests already remove the hash from the URL

Docs

N/A

Changes

update esbuild

Testing

existing tests should pass

Docs

not needed

Changes

Drop cjs config support

Testing

Existing tests should pass

Docs

Might be needed

/cc @withastro/maintainers-docs for feedback!

Changes

• Instead of mutating the provider name, we keep the mapping from the provider object to an ID inside the font resolver

Testing

Updated

Docs

N/A, internal refactor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

astro@6.0.0-beta.1

Patch Changes

• Updated dependencies [bbb5811]:
  • @astrojs/markdown-remark@7.0.0-beta.1

@astrojs/prism@4.0.0-beta.1

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

@astrojs/rss@4.0.15-beta.1

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

create-astro@5.0.0-beta.1

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

@astrojs/db@0.19.0-beta.2

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

@astrojs/alpinejs@0.5.0-beta.1

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

@astrojs/markdoc@1.0.0-beta.4

Patch Changes

• Updated dependencies [bbb5811, bbb5811]:
  • @astrojs/markdown-remark@7.0.0-beta.1
  • @astrojs/prism@4.0.0-beta.1

@astrojs/mdx@5.0.0-beta.1

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

• Updated dependencies [bbb5811]:

  • @astrojs/markdown-remark@7.0.0-beta.1

@astrojs/netlify@7.0.0-beta.5

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

• Updated dependencies []:

  • @astrojs/underscore-redirects@1.0.0

@astrojs/preact@5.0.0-beta.1

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

@astrojs/react@5.0.0-beta.1

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

@astrojs/sitemap@3.6.1-beta.2

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

@astrojs/solid-js@6.0.0-beta.1

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

@astrojs/check@0.9.6-beta.1

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

• Updated dependencies [bbb5811]:

  • @astrojs/language-server@2.16.1-beta.1

@astrojs/language-server@2.16.1-beta.1

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

@astrojs/markdown-remark@7.0.0-beta.1

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

• Updated dependencies [bbb5811]:

  • @astrojs/prism@4.0.0-beta.1

@astrojs/upgrade@0.7.0-beta.1

Patch Changes

• #15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/sitemap@3.7.0

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`
      },
    }),
  ],
  
  

astro@5.16.10

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

@astrojs/rss@4.0.15

Patch Changes

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

@astrojs/netlify@6.6.4

Patch Changes

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

• Updated dependencies []:

  • @astrojs/underscore-redirects@1.0.0

@astrojs/node@9.5.2

Patch Changes

• #15196 a8317c1 Thanks @ematipico! - Fixes an issue where some prendered pages weren't correctly rendered when using the Node.js adapter in middleware mode.

• #15169 b803d8b Thanks @rururux! - fix: fix image 500 error when moving dist directory in standalone Node

@astrojs/vercel@9.0.4

Patch Changes

• #14863 29fd188 Thanks @drwpow! - Improves error message when using Node builtins inside Edge middlewares

@astrojs/language-server@2.16.3

Patch Changes

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

Adds missing changesets for packages not published.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@astrojs/markdoc@1.0.0-beta.3

Patch Changes

• #15184 f47c071 Thanks @ematipico! - Fixes an issue where the package wasn't correctly published

Summary

When running astro add vercel, the Vercel adapter creates build artifacts in .vercel/output/. This directory should be gitignored to avoid committing build artifacts.

This PR adds automatic .gitignore handling for the Vercel adapter, following the same pattern already used for Cloudflare, Tailwind, Svelte, and other integrations:

• If .gitignore exists but doesn't contain .vercel, prompts to add it
• If .gitignore doesn't exist, prompts to create it with .vercel
• If .vercel is already in .gitignore, skips silently

Closes #15058

Test plan

1. Run astro add vercel in a project without .gitignore - should prompt to create one
2. Run astro add vercel in a project with .gitignore without .vercel - should prompt to add it
3. Run astro add vercel in a project with .gitignore containing .vercel - should skip silently

🤖 Generated with Claude Code

Changes

Should fix the package publishing

Testing

Docs

Changes

• We have APIs to allow using font data programmatically, which was mainly designed for advanced usage such as OG images
• However, getting the font buffer has always been clunky. It actually didn't work during prererendering (which is the main usecase)
• This PR introduces a new getFontBuffer() function that get the buffer using a url from the result of getFontData()
• In SSR if getFontData() is used, a js file is created per buffer in the server output in addition to actual files in the client output. Not sure there's much we can do about it
• On the client, calling the function always throws. This is avoid making the client bundle size huge

Testing

• New unit test
• Add ssr integrated tests
• Add integrated tests

Docs

• Changeset
• RFC
• withastro/docs#13041

Changes

• Makes so that the fonts runtime is type checked and used as an entrypoint only. It matches the work made for actions virtual modules in v6
• This PR is mostly about moving code around, which makes the diff big
• Moves the functions that were defined in runtime.ts to core/<name>.ts
• Moves the code that was defined inline in the assets virtual module to runtime.ts
• Moves tests

Testing

Updated. Tests are added for createGetFontData()

Docs

N/A, internal refactor

Changes

Based of #15154, original branch didn't have push rights for maintainers. This is the same PR just rebased of next instead of main.

Testing

See original PR

Docs

withastro/docs#13039

Changes

Initially reported on Discord, this PR fixes an issue when importing using an import alias a file with a name matching a directory name.

• Repro
• The custom resolver used in the vite plugin to alias paths now checks if a match is a file instead of only relying on fs.existsSync(), which returns true for both files and directories.

Testing

• Added a new src/pages.ts file in the existing alias-tsconfig fixture, matching the name of the src/pages/ directory, and imported it using an alias.
  • The associated test fails before the fix.
  • The test succeeds after the fix.

Docs

This is a bug fix; no doc updates are needed.

Changes

• Closes #15091
• Added isBuild check in buildEnd() hook to prevent font copying during dev server shutdown
• Font copying now only occurs during astro build, not when stopping dev server with q+enter
• Added test case to verify no dist folder is created when dev server stops
• Changeset added: fix-dev-quit-fonts-dist-creation.md

Testing

• Added test: "Does not create dist folder or copy fonts when dev server stops"
• Manual verification that q+enter no longer creates dist folder or copies fonts
• Verified fonts still work correctly in dev mode
• Verified astro build still copies fonts as expected

Docs

No docs changes needed. This fixes incorrect behavior in dev mode. User-facing behavior remains the same.

Switches the tag to beta for the beta release.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/starlight@0.37.3

Patch Changes

• #3648 292666c Thanks @maxchang3! - Prevents unwanted font size adjustments on iOS after orientation changes.

Changes

• Allows font providers to specify family specific options. That allows for a better DX (before it was a beir weird, see the diff of the changeset about the breaking change)
• Figuring out how to make the types work in defineConfig() was an absolute nightmare. We have types tests to avoid regressions

Testing

• Manually
• Types tests
• Config tests

Docs

• Changesets
• withastro/docs#13037

Changes

• After T&D feedback
• Since the beginning of the experimental fonts API, I have always omitted the Google Icons provider, which made things more confusing to document and support
• We now re-export all unifont providers

Testing

Updated

Docs

Changeset + withastro/docs#13035

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/sitemap (source)	^3.6.0 → ^3.6.1
@astrojs/svelte (source)	^7.2.4 → ^7.2.5
@astrojs/vue (source)	^5.1.3 → ^5.1.4
@cloudflare/workers-types	^4.20260101.0 → ^4.20260109.0
rollup (source)	^4.54.0 → ^4.55.1
wrangler (source)	4.54.0 → 4.58.0

Release Notes