Updatify / Astro | Release notes

Patch Changes

• #17151 ccceda3 Thanks @matthewp! - Fixes astro dev incorrectly starting in background mode for Warp terminal users. Hybrid environments like Warp are no longer treated as AI agents for auto-background detection.

• #17158 164df87 Thanks @ematipico! - Fixes astro dev --background --host not listing the network addresses. The background server start output and astro dev status now show every exposed network URL, matching the foreground dev server.

• #17141 d785b9d Thanks @astrobot-houston! - Fixes responsive image CSS overriding user styles defined inside CSS @layer blocks. The generated image styles are now wrapped in @layer astro.images, ensuring they have lower cascade priority than user-defined layers.

Major Changes

• #15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

Minor Changes

• #16335 9a53f77 Thanks @ascorbic! - Adds an opt-in CDN cache provider for Astro route caching on Cloudflare Workers

  [!WARNING] This provider requires the Cloudflare Workers Cache feature, which is currently in private beta. It is opt-in: nothing changes unless you import cacheCloudflare() and set it as your provider. But without beta access it does not work and should not be used. Cloudflare Workers run in front of the cache, so cached responses are never served, and calling cache.invalidate() throws an error.

  Setup

  Import cacheCloudflare() from @astrojs/cloudflare/cache and set it as your cache provider:

  import { defineConfig } from 'astro/config';
  import cloudflare from '@astrojs/cloudflare';
  import { cacheCloudflare } from '@astrojs/cloudflare/cache';
  
  export default defineConfig({
    adapter: cloudflare(),
    cache: {
      provider: cacheCloudflare(),
    },
  });

Major Changes

• #15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

Minor Changes

• #17093 4585fe5 Thanks @Princesseuh! - Replaces the import entrypoint of getContainerRenderer()

  A new container-renderer entrypoint exporting getContainerRenderer() has been added to the following integrations: React, Preact, Svelte, SolidJS, Vue, and MDX. This prevents bundlers from trying to bundle unrelated exports from the package root when only the Container API is used.

  If you are using the Container API, update your import statements to use the new entrypoint. The following example updates the getContainerRenderer() import for React:

  - import { getContainerRenderer } from '@astrojs/react';
  + import { getContainerRenderer } from '@astrojs/react/container-renderer';

  Importing getContainerRenderer() from the package root still works, but is now deprecated and logs a warning.

Patch Changes

Major Changes

• #15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

Minor Changes

• #17093 4585fe5 Thanks @Princesseuh! - Replaces the import entrypoint of getContainerRenderer()

  A new container-renderer entrypoint exporting getContainerRenderer() has been added to the following integrations: React, Preact, Svelte, SolidJS, Vue, and MDX. This prevents bundlers from trying to bundle unrelated exports from the package root when only the Container API is used.

  If you are using the Container API, update your import statements to use the new entrypoint. The following example updates the getContainerRenderer() import for React:

  - import { getContainerRenderer } from '@astrojs/react';
  + import { getContainerRenderer } from '@astrojs/react/container-renderer';

  Importing getContainerRenderer() from the package root still works, but is now deprecated and logs a warning.

Minor Changes

• #17122 cbd6123 Thanks @matthewp! - Adds a default AGENTS.md file to new projects with dev server instructions and documentation links. Also creates a CLAUDE.md symlink (with hard link fallback) pointing to AGENTS.md.

Major Changes

• #15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

Minor Changes

• #17093 4585fe5 Thanks @Princesseuh! - Replaces the import entrypoint of getContainerRenderer()

  A new container-renderer entrypoint exporting getContainerRenderer() has been added to the following integrations: React, Preact, Svelte, SolidJS, Vue, and MDX. This prevents bundlers from trying to bundle unrelated exports from the package root when only the Container API is used.

  If you are using the Container API, update your import statements to use the new entrypoint. The following example updates the getContainerRenderer() import for React:

  - import { getContainerRenderer } from '@astrojs/react';
  + import { getContainerRenderer } from '@astrojs/react/container-renderer';

  Importing getContainerRenderer() from the package root still works, but is now deprecated and logs a warning.

Major Changes

• #15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

Minor Changes

• #17093 4585fe5 Thanks @Princesseuh! - Replaces the import entrypoint of getContainerRenderer()

  A new container-renderer entrypoint exporting getContainerRenderer() has been added to the following integrations: React, Preact, Svelte, SolidJS, Vue, and MDX. This prevents bundlers from trying to bundle unrelated exports from the package root when only the Container API is used.

  If you are using the Container API, update your import statements to use the new entrypoint. The following example updates the getContainerRenderer() import for React:

  - import { getContainerRenderer } from '@astrojs/react';
  + import { getContainerRenderer } from '@astrojs/react/container-renderer';

  Importing getContainerRenderer() from the package root still works, but is now deprecated and logs a warning.

Patch Changes

Major Changes

• #15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

Minor Changes

• #17093 4585fe5 Thanks @Princesseuh! - Replaces the import entrypoint of getContainerRenderer()

  A new container-renderer entrypoint exporting getContainerRenderer() has been added to the following integrations: React, Preact, Svelte, SolidJS, Vue, and MDX. This prevents bundlers from trying to bundle unrelated exports from the package root when only the Container API is used.

  If you are using the Container API, update your import statements to use the new entrypoint. The following example updates the getContainerRenderer() import for React:

  - import { getContainerRenderer } from '@astrojs/react';
  + import { getContainerRenderer } from '@astrojs/react/container-renderer';

  Importing getContainerRenderer() from the package root still works, but is now deprecated and logs a warning.

Patch Changes

Major Changes

• #15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

Patch Changes

• #17027 241250b Thanks @ocavue! - Triggers beta prereleases for packages that are still on alpha

Major Changes

• #15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

Minor Changes

• #17093 4585fe5 Thanks @Princesseuh! - Replaces the import entrypoint of getContainerRenderer()

  A new container-renderer entrypoint exporting getContainerRenderer() has been added to the following integrations: React, Preact, Svelte, SolidJS, Vue, and MDX. This prevents bundlers from trying to bundle unrelated exports from the package root when only the Container API is used.

  If you are using the Container API, update your import statements to use the new entrypoint. The following example updates the getContainerRenderer() import for React:

  - import { getContainerRenderer } from '@astrojs/react';
  + import { getContainerRenderer } from '@astrojs/react/container-renderer';

  Importing getContainerRenderer() from the package root still works, but is now deprecated and logs a warning.

Patch Changes

Patch Changes

• #17124 7e7ab87 Thanks @Princesseuh! - Updates satteri to 0.9.0. See the Sätteri changelog for details.

• #17129 ff7b718 Thanks @Princesseuh! - Adds support for modifying frontmatter programmatically with the default Markdown processor.

  A Sätteri plugin can now read and mutate ctx.data.astro.frontmatter, and Astro uses the result as the page’s frontmatter, in both Markdown and MDX.

• #17027 241250b Thanks @ocavue! - Triggers beta prereleases for packages that are still on alpha

Major Changes

• #15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

• #16965 57ead0d Thanks @Princesseuh! - Makes 'jsx' the default value for compressHTML

  Astro now strips whitespace from your HTML using JSX rules by default, the same way frameworks like React do. Whitespace and line breaks around elements are removed, but meaningful whitespace within a single line — like a space between two inline elements — is preserved. To keep a space that would otherwise be removed, write it explicitly in your source, for example with {" "}.

  This can change rendered output where whitespace between inline elements was previously meaningful. To keep Astro’s earlier behavior, set compressHTML: true for HTML-aware compression, or compressHTML: false to preserve all whitespace.

• #16610 c63e7e4 Thanks @matthewp! - Adds background dev server management for AI coding agents.

Major Changes

• #15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

Minor Changes

• #16335 9a53f77 Thanks @ascorbic! - Adds a CDN cache provider for Astro route caching on Netlify

  Setup

  Import cacheNetlify() from @astrojs/netlify/cache and set it as your cache provider:

  import { defineConfig } from 'astro/config';
  import netlify from '@astrojs/netlify';
  import { cacheNetlify } from '@astrojs/netlify/cache';
  
  export default defineConfig({
    adapter: netlify(),
    cache: {
      provider: cacheNetlify(),
    },
  });

  Caching responses

  Use Astro.cache.set() in your pages and API routes to cache responses on Netlify’s edge network. The provider uses Netlify’s durable cache so cached responses are shared across all edge nodes, reducing function invocations.

  ---
  Astro.cache.set({ maxAge: 300, tags: ['products'] });
  const data = await fetchProducts();
  ---
  
  <ProductList items={data} />

Major Changes

• #15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

Minor Changes

• #16335 9a53f77 Thanks @ascorbic! - Adds a CDN cache provider for Astro route caching on Vercel

  Setup

  Import cacheVercel() from @astrojs/vercel/cache and set it as your cache provider:

  import { defineConfig } from 'astro/config';
  import vercel from '@astrojs/vercel';
  import { cacheVercel } from '@astrojs/vercel/cache';
  
  export default defineConfig({
    adapter: vercel(),
    cache: {
      provider: cacheVercel(),
    },
  });

  Caching responses

  Use Astro.cache.set() in your pages and API routes to cache responses on Vercel’s edge network. The provider sets Vercel-CDN-Cache-Control and Vercel-Cache-Tag headers on responses.

  ---
  Astro.cache.set({ maxAge: 300, tags: ['products'] });
  const data = await fetchProducts();
  ---
  
  <ProductList items={data} />

  You can also set cache rules for groups of routes in your config:

  cache: { provider: cacheVercel() },

Major Changes

• #15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

Patch Changes

• #17027 241250b Thanks @ocavue! - Triggers beta prereleases for packages that are still on alpha

Patch Changes

• #17054 d426b67 Thanks @astrobot-houston! - Fixes an issue where Astro files with non-ASCII characters in their name weren’t correctly served after the build.

• #17027 241250b Thanks @ocavue! - Triggers beta prereleases for packages that are still on alpha

Patch Changes

• #17109 27c80ea Thanks @ematipico! - Harden the limits on the number of decoding on the URL.

Patch Changes

• #17035 197e50e Thanks @astrobot-houston! - Fixes getRelativeLocaleUrl, getAbsoluteLocaleUrl, and getAbsoluteLocaleUrlList to strip trailing slashes when trailingSlash: 'never' is configured

• #16967 3719765 Thanks @astrobot-houston! - Fixes double URL-encoded paths returning 400 Bad Request on on-demand routes

  Previously, any URL containing a double-encoded character (like %255B, which is [ encoded twice) was unconditionally rejected with a 400 Bad Request before middleware or route handlers could run. This broke embedded tools like Sanity Studio whose client-side router legitimately produces double-encoded URLs.

Patch Changes

• #17018 1310277 Thanks @matthewp! - Hardens remotePatterns regex generation to match canonical wildcard semantics more strictly

• Updated dependencies []:

  • @astrojs/underscore-redirects@1.0.3

Patch Changes

• #16765 b10e86e Thanks @fkatsuhiro! - Fixes an issue where renaming an image file while the dev server is running triggers a build error. Now Astro correctly hot-reloads the image without crashing.

• #17026 add3df1 Thanks @matthewp! - Hardens addAttribute to drop attribute names containing characters that are invalid per the HTML spec (", ', >, /, =, whitespace)

• #17033 ffda27b Thanks @matthewp! - Validates the request origin against allowedDomains before fetching prerendered error pages. When allowedDomains is configured and the Host header matches, the original origin is used. Otherwise, the fetch falls back to localhost.

Patch Changes

• #16985 4ecff32 Thanks @maximslo! - Fixes the experimental.logger destination not being used for the “Server listening on…” startup message. The logger is now resolved before the server starts listening, and adapterLogger re-creates itself when the underlying logger changes so the startup message uses the correct destination.

• #16947 e0703a6 Thanks @ematipico! - Fixes Astro.request.url not reflecting validated X-Forwarded-Proto/X-Forwarded-Host headers when security.allowedDomains is configured. Previously, only Astro.url was updated with the forwarded origin while Astro.request.url retained the socket-derived URL, causing the two to diverge behind TLS-terminating proxies.

• #16997 dc45246 Thanks @matthewp! - Reverts a change to isNode runtime detection that caused a significant build time regression for Cloudflare adapter users with large prerendered sites

Patch Changes

• #16964 b048826 Thanks @Princesseuh! - Deprecates the @astrojs/db integration. We no longer have the bandwidth to maintain this package, and we recommend that users directly use the database client of their choice (Drizzle, Kysely, etc.) in their Astro projects instead.

Minor Changes

• #16571 d4b0cd1 Thanks @MA2153! - Sets immutable cache headers for static assets

  Static assets under _astro can be cached to improve performance. The adapter now automatically injects a Cache-Control header at build time when possible.

Patch Changes

• #16968 7a5c001 Thanks @astrobot-houston! - Fixes a build crash when using experimental.advancedRouting with a custom fetchFile that statically imports cf from @astrojs/cloudflare/fetch. The circular dependency between @astrojs/cloudflare/fetch and astro/app/entrypoint caused createApp or createGetEnv to be undefined at module evaluation time. Initialization is now deferred to the first cf() call, breaking the cycle.

• Updated dependencies []:

  • @astrojs/underscore-redirects@1.0.3

Patch Changes

• #16985 4ecff32 Thanks @maximslo! - Fixes the experimental.logger destination not being used for the “Server listening on…” startup message. The logger is now resolved before the server starts listening, and adapterLogger re-creates itself when the underlying logger changes so the startup message uses the correct destination.

Patch Changes

• #16969 4a31f90 Thanks @Princesseuh! - Adds support for Prism syntax highlighting to the Sätteri Markdown and MDX processors. Setting markdown.syntaxHighlight to 'prism' now highlights your code blocks with Prism.

  // astro.config.mjs
  import { satteri } from '@astrojs/markdown-satteri';
  
  export default defineConfig({
    markdown: {
      processor: satteri(),
      syntaxHighlight: 'prism',
    },
  });

Minor Changes

• #16969 4a31f90 Thanks @Princesseuh! - Adds support for Prism syntax highlighting to the Sätteri Markdown and MDX processors. Setting markdown.syntaxHighlight to 'prism' now highlights your code blocks with Prism.

  // astro.config.mjs
  import { satteri } from '@astrojs/markdown-satteri';
  
  export default defineConfig({
    markdown: {
      processor: satteri(),
      syntaxHighlight: 'prism',
    },
  });

Patch Changes

• #16926 1b39ae8 Thanks @narendraio! - Prevents App.match() from throwing on request paths that contain an invalid percent-sequence.

• #16924 2c0bc94 Thanks @astrobot-houston! - Fixes an issue where editing a client-side component (e.g. with client:idle, client:load, etc.) caused an unnecessary full program reload of the backend during development.

• #16958 2c1d50f Thanks @fkatsuhiro! - Fixes a bug where static file endpoints using getStaticPaths with .html in dynamic param values (e.g. { path: 'file.html' }) would fail with a NoMatchingStaticPathFound error during build. The .html suffix is no longer incorrectly stripped from endpoint route pathnames.

Patch Changes

• #16955 9a93d68 Thanks @Princesseuh! - Updates Sätteri processor to v0.8.0. See its changelog for details on bugs fixed and features added.

• Updated dependencies [9a93d68]:

  • @astrojs/markdown-satteri@0.2.2

Patch Changes

• #16955 9a93d68 Thanks @Princesseuh! - Updates Sätteri processor to v0.8.0. See its changelog for details on bugs fixed and features added.

Patch Changes

• #16922 7dce185 Thanks @astrobot-houston! - Fixes prerendered pages returning 404 when using build.format: 'file' or build.format: 'preserve' with the Node adapter in standalone mode.

  Previously, clean URLs like /about would fail to resolve to about.html on disk, because the static file handler only supported the default directory format (about/index.html). Now the handler correctly resolves clean URLs to .html files when the build format produces them.

Patch Changes

• #16693 9e6edc2 Thanks @ArmandPhilippot! - Fixes a link in the documentation specifying where to open an issue for the adapter.

• Updated dependencies []:

  • @astrojs/underscore-redirects@1.0.3

Patch Changes

• #16900 17a0fbd Thanks @ocavue! - Bumps devalue dependency to v5.8.1

Patch Changes

• #16900 17a0fbd Thanks @ocavue! - Bumps devalue dependency to v5.8.1

• #16016 0d85e1b Thanks @felmonon! - Fix a false positive in the dev toolbar accessibility audit for anchors with text inside closed <details> elements.

• #16911 79c6c46 Thanks @astrobot-houston! - Fixes a bug where experimental.advancedRouting with astro/hono handlers threw TypeError: Cannot read properties of undefined (reading 'route') for unmatched routes instead of rendering the custom 404 page.

• #16899 239c469 Thanks @matthewp! - Fixes a false “does not call the middleware() handler” warning when using astro() in a custom src/app.ts and the first request is a redirect route.

Patch Changes

• #16900 17a0fbd Thanks @ocavue! - Bumps devalue dependency to v5.8.1

Patch Changes

• #16914 4bdd240 Thanks @matthewp! - Fixes astro/fetch and astro/hono being discovered at runtime during dev instead of pre-bundled

• #16693 9e6edc2 Thanks @ArmandPhilippot! - Fixes a link in the documentation specifying where to open an issue for the adapter.

• Updated dependencies []:

  • @astrojs/underscore-redirects@1.0.3

Patch Changes

• #16889 b94bcfd Thanks @Princesseuh! - Fixes a plugins is not iterable crash when using a pre-6.0 @astrojs/mdx alongside integrations (e.g. Starlight) that set markdown.remarkPlugins, markdown.rehypePlugins, or markdown.remarkRehype.

• #16878 b9f6bb9 Thanks @fkatsuhiro! - Fixes an issue where on-demand (SSR) dynamic routes would return 404 when a prerendered dynamic route with the same URL pattern was sorted first alphabetically. In production builds with @astrojs/node adapter, if [a_prebuild].astro (prerender=true) came before [b_ssr].astro alphabetically, requests to URLs not in the prerendered route’s static paths would 404 instead of falling through to the SSR route. The fix adds fallthrough logic so that when a prerendered dynamic route matches but can’t serve the request, Astro tries subsequent matching routes.

Patch Changes

• #16883 eeb064c Thanks @Princesseuh! - Fixes missing provenance information on the publish

13.6.0

Minor Changes

• #16729 01aa164 Thanks @matthewp! - Adds @astrojs/cloudflare/fetch and @astrojs/cloudflare/hono exports for composing Cloudflare-specific setup with Astro’s advanced routing handlers.

  @astrojs/cloudflare/fetch

  For use with astro/fetch in a custom fetch handler:

  import { astro, FetchState } from 'astro/fetch';
  import { cf } from '@astrojs/cloudflare/fetch';
  
  export default {
    async fetch(request: Request, env: Env, ctx: ExecutionContext) {
      const state = new FetchState(request);
      const asset = await cf(state, env, ctx);
      if (asset) return asset;
      return astro(state);
    },
  };

  @astrojs/cloudflare/hono

  For use with astro/hono as Hono middleware:

  import { Hono } from 'hono';
  import { actions, middleware, pages, i18n } from 'astro/hono';
  import { cf } from '@astrojs/cloudflare/hono';
  
  const app = new Hono<{ Bindings: Env }>();
  
  app.use(cf());
  app.use(actions());
  app.use(middleware());
  app.use(pages());
  app.use(i18n());
  
  export default app;

  Both handlers configure SESSION KV bindings, static asset serving via the ASSETS binding, locals.cfContext, client address, waitUntil, and prerendered error page fetch.

0.10.0

Minor Changes

• #16848 f732f3c Thanks @Princesseuh! - Adds markdown, frontmatter, and shiki helper modules, shared by Astro’s content pipeline.

1.0.6

Patch Changes

• #16848 f732f3c Thanks @Princesseuh! - Removes @astrojs/markdown-remark from @astrojs/markdoc‘s dependencies in favour of Astro’s internal markdown utilities now that Astro’s Markdown support is processor agnostic.

• Updated dependencies [f732f3c]:

  • @astrojs/internal-helpers@0.10.0

7.2.0

Minor Changes

• #16848 f732f3c Thanks @Princesseuh! - Adds a new markdown.processor configuration option, allowing you to choose an alternative Markdown processor.

  Websites with many Markdown/MDX files tend to be slow to build because the unified ecosystem (e.g., remark, rehype) is slow to process. This feature introduces the ability to replace this part of the build pipeline with another processor.

  The default processor is unified(). This means that existing configurations remain unchanged and your remark/rehype plugins continue to work.

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  import { unified } from '@astrojs/markdown-remark';
  import remarkToc from 'remark-toc';
  
  export default defineConfig({
    markdown: {
      processor: unified({
        remarkPlugins: [remarkToc],
      }),
    },
  });

  In addition to this new configuration option, Astro provides a new alternative processor based on Rust: Sätteri. You can choose to use it now by installing @astrojs/markdown-satteri, importing the satteri() processor, and adapting your existing configuration:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';

6.0.0

Major Changes

• #16848 f732f3c Thanks @Princesseuh! - Adds a new markdown.processor configuration option, allowing you to choose an alternative Markdown processor.

  Websites with many Markdown/MDX files tend to be slow to build because the unified ecosystem (e.g., remark, rehype) is slow to process. This feature introduces the ability to replace this part of the build pipeline with another processor.

  The default processor is unified(). This means that existing configurations remain unchanged and your remark/rehype plugins continue to work.

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  import { unified } from '@astrojs/markdown-remark';
  import remarkToc from 'remark-toc';
  
  export default defineConfig({
    markdown: {
      processor: unified({
        remarkPlugins: [remarkToc],
      }),
    },
  });

  In addition to this new configuration option, Astro provides a new alternative processor based on Rust: Sätteri. You can choose to use it now by installing @astrojs/markdown-satteri, importing the satteri() processor, and adapting your existing configuration:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';

Patch Changes

• Updated dependencies [f732f3c]:
  • @astrojs/internal-helpers@0.10.0
  • @astrojs/underscore-redirects@1.0.3

Patch Changes

• Updated dependencies [f732f3c]:
  • @astrojs/internal-helpers@0.10.0

Patch Changes

• Updated dependencies [f732f3c]:
  • @astrojs/internal-helpers@0.10.0

Patch Changes

• Updated dependencies [f732f3c]:
  • @astrojs/internal-helpers@0.10.0

Patch Changes

• Updated dependencies [f732f3c]:
  • @astrojs/internal-helpers@0.10.0

Minor Changes

• #16468 4cff3a1 Thanks @matthewp! - Adds a new preserveBuildServerDir adapter feature

  Adapters can now set preserveBuildServerDir: true in their adapter features to keep the dist/server/ directory structure for static builds, mirroring the existing preserveBuildClientDir option. This is useful for adapters that require a consistent dist/client/ and dist/server/ layout regardless of build output type.

  setAdapter({
    name: 'my-adapter',
    adapterFeatures: {
      buildOutput,
      preserveBuildClientDir: true,
      preserveBuildServerDir: true,
    },
  });

• #16848 f732f3c Thanks @Princesseuh! - Adds a new markdown.processor configuration option, allowing you to choose an alternative Markdown processor.

  Websites with many Markdown/MDX files tend to be slow to build because the unified ecosystem (e.g., remark, rehype) is slow to process. This feature introduces the ability to replace this part of the build pipeline with another processor.

Patch Changes

• #16827 90ee151 Thanks @matthewp! - Fixes a crash in the language server and astro check when using TypeScript project references with .vue or .svelte files

Patch Changes

• #16496 4d79750 Thanks @fkatsuhiro! - Fixed an issue where type errors occurred during testing library type checks because Astro overrides Svelte 5 component types.