fix(deps): update astro monorepo (major) by renovate[bot] · Pull Request #10 · jee-r/patchwork

renovate · 2026-03-10T13:06:40Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/node (source)	`^9.5.4` → `^11.0.0`
@astrojs/vercel (source)	`^9.0.4` → `^11.0.0`
astro (source)	`^5.18.0` → `^7.0.0`

Release Notes

withastro/astro (@astrojs/node)

`v11.0.0`

Compare Source

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

`v10.1.4`

Compare Source

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.

`v10.1.3`

Compare Source

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.

Minor Changes

#16639 4d72482 Thanks @ematipico! - The adapter now depends on Astro 6.3.0.

`v10.0.6`

Compare Source

Patch Changes

Updated dependencies [99464ed, f3485c3]:
- @astrojs/internal-helpers@0.9.0

`v10.0.5`

Compare Source

Patch Changes

#16319 940afd5 Thanks @matthewp! - Fixes static asset error responses incorrectly including immutable cache headers. Conditional request failures (e.g. If-Match mismatch) now return the correct status code without far-future cache directives.

`v10.0.4`

Compare Source

Patch Changes

#16002 846f27f Thanks @buley! - Fixes file descriptor leaks from read streams that were not destroyed on client disconnect or read errors
#15941 f41584a Thanks @ematipico! - Fixes an infinite loop in resolveClientDir() when the server entry point is bundled with esbuild or similar tools. The function now throws a descriptive error instead of hanging indefinitely when the expected server directory segment is not found in the file path.

`v10.0.3`

Compare Source

Patch Changes

#15735 9685e2d Thanks @fa-sharp! - Fixes an EventEmitter memory leak when serving static pages from Node.js middleware.

When using the middleware handler, requests that were being passed on to Express / Fastify (e.g. static files / pre-rendered pages / etc.) weren't cleaning up socket listeners before calling next(), causing a memory leak warning. This fix makes sure to run the cleanup before calling next().

`v10.0.2`

Compare Source

Patch Changes

#15934 6f8f0bc Thanks @ematipico! - Updates the Astro peerDependencies#astro to be 6.0.0.

`v10.0.1`

Compare Source

Patch Changes

#15868 bb2b8f5 Thanks @ematipico! - Fixes an issue where the adapter would cause a series of warnings during the build.

`v10.0.0`

Compare Source

Major Changes

#15654 a32aee6 Thanks @florian-lefebvre! - Removes the experimentalErrorPageHost option

This option allowed fetching a prerendered error page from a different host than the server is currently running on.

However, there can be security implications with prefetching from other hosts, and often more customization was required to do this safely. This has now been removed as a built-in option so that you can implement your own secure solution as needed and appropriate for your project via middleware.

What should I do?

If you were previously using this feature, you must remove the option from your adapter configuration as it no longer exists:

// astro.config.mjs
import { defineConfig } from 'astro/config'
import node from '@&#8203;astrojs/node'

export default defineConfig({
  adapter: node({
    mode: 'standalone',
-    experimentalErrorPageHost: 'http://localhost:4321'
  })
})

You can replicate the previous behavior by checking the response status in a middleware and fetching the prerendered page yourself:

// src/middleware.ts
import { defineMiddleware } from 'astro:middleware';

export const onRequest = defineMiddleware(async (ctx, next) => {
  const response = await next();
  if (response.status === 404 || response.status === 500) {
    return fetch(`http://localhost:4321/${response.status}.html`);
  }
  return response;
});

Minor Changes

#15258 d339a18 Thanks @ematipico! - Stabilizes the adapter feature experimentalStatiHeaders. If you were using this feature in any of the supported adapters, you'll need to change the name of the flag:
```
export default defineConfig({
  adapter: netlify({
-    experimentalStaticHeaders: true
+    staticHeaders: true
  })
})
```
#15759 39ff2a5 Thanks @matthewp! - Adds a new bodySizeLimit option to the @astrojs/node adapter

You can now configure a maximum allowed request body size for your Node.js standalone server. The default limit is 1 GB. Set the value in bytes, or pass 0 to disable the limit entirely:
```
import node from '@&#8203;astrojs/node';
import { defineConfig } from 'astro/config';

export default defineConfig({
  adapter: node({
    mode: 'standalone',
    bodySizeLimit: 1024 * 1024 * 100, // 100 MB
  }),
});
```
#15006 f361730 Thanks @florian-lefebvre! - Adds new session driver object shape

For greater flexibility and improved consistency with other Astro code, session drivers are now specified as an object:
```
-import { defineConfig } from 'astro/config'
+import { defineConfig, sessionDrivers } from 'astro/config'

export default defineConfig({
  session: {
-    driver: 'redis',
-    options: {
-      url: process.env.REDIS_URL
-    },
+    driver: sessionDrivers.redis({
+      url: process.env.REDIS_URL
+    }),
  }
})
```
Specifying the session driver as a string has been deprecated, but will continue to work until this feature is removed completely in a future major version. The object shape is the current recommended and documented way to configure a session driver.
#14946 95c40f7 Thanks @ematipico! - Removes the experimental.csp flag and replaces it with a new configuration option security.csp - (v6 upgrade guidance)

Patch Changes

#15473 d653b86 Thanks @matthewp! - Improves error page loading to read from disk first before falling back to configured host
#15562 e14a51d Thanks @florian-lefebvre! - Updates to new Adapter API introduced in v6
#15585 98ea30c Thanks @matthewp! - Add a default body size limit for server actions to prevent oversized requests from exhausting memory.
#15777 02e24d9 Thanks @matthewp! - Fixes CSRF origin check mismatch by passing the actual server listening port to createRequest, ensuring the constructed URL origin includes the correct port (e.g., http://localhost:4321 instead of http://localhost). Also restricts X-Forwarded-Proto to only be trusted when allowedDomains is configured.
#15714 9a2c949 Thanks @ematipico! - Fixes an issue where static headers weren't correctly applied when the website uses base.
#15763 1567e8c Thanks @matthewp! - Normalizes static file paths before evaluating dotfile access rules for improved consistency
#15164 54dc11d Thanks @HiDeoo! - Fixes an issue where the Node.js adapter could fail to serve a 404 page matching a pre-rendered dynamic route pattern.
#15745 20b05c0 Thanks @matthewp! - Hardens static file handler path resolution to ensure resolved paths stay within the client directory
#15495 5b99e90 Thanks @leekeh! - Refactors to use middlewareMode adapter feature (set to classic)
#15657 cb625b6 Thanks @qzio! - Adds a new security.actionBodySizeLimit option to configure the maximum size of Astro Actions request bodies.

This lets you increase the default 1 MB limit when your actions need to accept larger payloads. For example, actions that handle file uploads or large JSON payloads can now opt in to a higher limit.

If you do not set this option, Astro continues to enforce the 1 MB default to help prevent abuse.
```
// astro.config.mjs
export default defineConfig({
  security: {
    actionBodySizeLimit: 10 * 1024 * 1024, // set to 10 MB
  },
});
```
Updated dependencies [4ebc1e3, 4e7f3e8, a164c77, cf6ea6b, a18d727, 240c317, 745e632]:
- @astrojs/internal-helpers@0.8.0

withastro/astro (@astrojs/vercel)

`v11.0.0`

Compare Source

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 '@&#8203;astrojs/vercel';
import { cacheVercel } from '@&#8203;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() },
routeRules: {
  '/products/[...slug]': { maxAge: 3600, tags: ['products'] },
  '/api/[...path]': { maxAge: 60, swr: 600 },
},

Invalidation

Purge cached responses by tag or path from any API route or server endpoint:

// src/pages/api/purge.ts
export async function POST({ request, cache }) {
  await cache.invalidate({ tags: ['products'] });
  return new Response('Purged');
}

// Path-based invalidation
await cache.invalidate({ path: '/products/123' });

Both tag-based and path-based invalidation are supported. Tag invalidation is a soft invalidation, marking cached responses as stale so they can be revalidated in the background via stale-while-revalidate.

Patch Changes

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

`v10.0.8`

Compare Source

Patch Changes

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

`v10.0.7`

Compare Source

Patch Changes

Updated dependencies [d365c97]:
- @astrojs/internal-helpers@0.9.1

`v10.0.6`

Compare Source

Patch Changes

#16486 0bae1a5 Thanks @cyphercodes! - Fix forwarded serverless requests with streamed bodies by preserving the required duplex: 'half' option when rewriting middleware paths.

`v10.0.5`

Compare Source

Patch Changes

Updated dependencies [99464ed, f3485c3]:
- @astrojs/internal-helpers@0.9.0

`v10.0.4`

Compare Source

Patch Changes

#16170 d0fe1ec Thanks @bittoby! - Fixes edge middleware next() dropping the HTTP method and body when forwarding requests to the serverless function, which caused non-GET API routes (POST, PUT, PATCH, DELETE) to return 404

`v10.0.3`

Compare Source

Patch Changes

#16079 aa26636 Thanks @empoulter-uclan! - Fix vercel ISR path rewrite

`v10.0.2`

Compare Source

Patch Changes

#15959 335a204 Thanks @matthewp! - Fix Vercel serverless path override handling so override values are only applied when the trusted middleware secret is present.

`v10.0.1`

Compare Source

Patch Changes

#15934 6f8f0bc Thanks @ematipico! - Updates the Astro peerDependencies#astro to be 6.0.0.

`v10.0.0`

Compare Source

Major Changes

#15413 736216b Thanks @florian-lefebvre! - Removes the deprecated @astrojs/vercel/serverless and @astrojs/vercel/static exports. Use the @astrojs/vercel export instead

Minor Changes

#15258 d339a18 Thanks @ematipico! - Stabilizes the adapter feature experimentalStatiHeaders. If you were using this feature in any of the supported adapters, you'll need to change the name of the flag:
```
export default defineConfig({
  adapter: netlify({
-    experimentalStaticHeaders: true
+    staticHeaders: true
  })
})
```
#15413 736216b Thanks @florian-lefebvre! - Updates the implementation to use the new Adapter API
#15495 5b99e90 Thanks @leekeh! - Adds new middlewareMode adapter feature and deprecates edgeMiddleware option

The edgeMiddleware option is now deprecated and will be removed in a future release, so users should transition to using the new middlewareMode feature as soon as possible.
```
export default defineConfig({
  adapter: vercel({
-    edgeMiddleware: true
+    middlewareMode: 'edge'
  })
})
```
#14946 95c40f7 Thanks @ematipico! - Removes the experimental.csp flag and replaces it with a new configuration option security.csp - (v6 upgrade guidance)

Patch Changes

#15781 2de969d Thanks @ematipico! - Adds a new clientAddress option to the createContext() function

Providing this value gives adapter and middleware authors explicit control over the client IP address. When not provided, accessing clientAddress throws an error consistent with other contexts where it is not set by the adapter.

Additionally, both of the official Netlify and Vercel adapters have been updated to provide this information in their edge middleware.
```
import { createContext } from 'astro/middleware';

createContext({
  clientAddress: context.headers.get('x-real-ip'),
});
```
#15778 4ebc1e3 Thanks @ematipico! - Fixes an issue where the computed clientAddress was incorrect in cases of a Request header with multiple values. The clientAddress is now also validated to contain only characters valid in IP addresses, rejecting injection payloads.
#15460 ee7e53f Thanks @florian-lefebvre! - Updates to use the new Adapter API
#15450 50c9129 Thanks @florian-lefebvre! - Fixes a case where build.serverEntry would not be respected when using the new Adapter API
#15461 9f21b24 Thanks @florian-lefebvre! - Updates to new Adapter API introduced in v6
#15125 6feb0d7 Thanks @florian-lefebvre! - Updates Node versions data to account for v24 as the default
Updated dependencies [4ebc1e3, 4e7f3e8, a164c77, cf6ea6b, a18d727, 240c317, 745e632]:
- @astrojs/internal-helpers@0.8.0

withastro/astro (astro)

`v7.0.0`

Compare Source

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.

When an AI coding agent is detected, astro dev now automatically starts the dev server as a detached background process. This prevents the dev server from blocking the agent's terminal and allows it to continue working while the server runs.

A lock file (.astro/dev.json) is written when the dev server starts, recording the server's URL, port, and PID. This prevents duplicate servers from being started for the same project.

New flag and subcommands

astro dev --background — Start the dev server as a background process (this is what runs automatically when an agent is detected).
astro dev stop — Stop a running background dev server.
astro dev status — Check if a dev server is running and display its URL, PID, and uptime.
astro dev logs — View logs from a background dev server. Use --follow (-f) to stream new output as it's written.

These allow you to start and manage dev servers programmatically and were designed with AI coding agents in mind.

What should I do?

No action is required. If you are not using an AI coding agent, astro dev behaves exactly as before. If you are using an agent, background mode is enabled automatically — the agent will receive the server URL and PID, and can use astro dev stop to shut it down.

To opt out of automatic background mode when an agent is detected, set the environment variable ASTRO_DEV_BACKGROUND=0 before running astro dev.

#17010 0606073 Thanks @ocavue! - Removes the @astrojs/db package as it is no longer maintained.

The @astrojs/db package were deprecated in v6.4.5 and is now removed. This means the astro db, astro login, astro logout, astro link, and astro init CLI commands have also been removed.

If you were using Astro DB in your project, remove @astrojs/db from your project's dependencies and replace it with one of the following alternatives:
- Node.js built-in SQLite: Node.js now includes a built-in node:sqlite module (available since Node.js v22.5.0). This is a good option if you are using the Node.js adapter and were using @astrojs/db for local SQLite storage.
- Drizzle ORM: If you were using @astrojs/db for its Drizzle-based schema and query API, you can use Drizzle directly with any supported database.
- Other database libraries: Use any database library that suits your deployment platform (e.g. Turso, PlanetScale, Neon).
#16462 c30a778 Thanks @Princesseuh! - Replaces the Go compiler with a Rust-based version.

The Rust-based Astro compiler (@astrojs/compiler-rs) is now the default compiler. This new compiler is faster and more reliable, leading to faster build times and iteration cycles during development.

This new compiler is more strict regarding invalid syntax. For example, unclosed HTML tags will now throw an error instead of being ignored. It also does not attempt to correct semantically invalid HTML anymore, instead leaving it to the browser to handle, similar to other tools or document.write() in JavaScript.

The previous Go-based compiler has been removed, along with the experimental.rustCompiler flag used to opt into the Rust compiler. If you were setting experimental.rustCompiler in your astro.config.mjs, you can now remove it. No other action is required.
#16966 6650ec2 Thanks @Princesseuh! - Makes Sätteri the default Markdown processor

Astro now renders .md files with satteri() from @astrojs/markdown-satteri, its native Markdown pipeline, instead of the remark/rehype pipeline. @astrojs/markdown-remark is no longer installed by default.

To keep using the remark/rehype pipeline, install @astrojs/markdown-remark and set it as your processor:
```
// astro.config.mjs
import { defineConfig } from 'astro/config';
import { unified } from '@&#8203;astrojs/markdown-remark';

export default defineConfig({
  markdown: {
    processor: unified(),
  },
});
```
The deprecated markdown.remarkPlugins, markdown.rehypePlugins, and markdown.remarkRehype options still work, but now require @astrojs/markdown-remark to be used.
#16877 3b7d76e Thanks @matthewp! - Enables advanced routing by default.

The advanced routing feature introduced behind a flag in v6.3.0 is no longer experimental and is now enabled by default.

This gives full control over how requests flow through your application, with first-class support for frameworks like Hono.

Advanced routing now uses src/fetch.ts as default entrypoint instead of src/app.ts.

If you were previously using this feature without a custom entrypoint, please configure fetchFile or rename your entrypoint to src/fetch.ts, and then remove the experimental flag from your Astro config:
```
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental {
-    advancedRouting: true,
  },
+  fetchFile: 'app.ts' // optional, you only need this if you cannot rename your entrypoint.
});
```
fetchFile is now a top-level config option instead of being nested under experimental.advancedRouting. If you were using a custom entrypoint, please update your Astro config to move its configuration:
```
// astro.config.mjs
export default defineConfig({
-  experimental: {
-    advancedRouting: {
-      fetchFile: 'my-custom-entrypoint.ts',
-    },
-  },
+  fetchFile: 'my-custom-entrypoint.ts',
})
```
You can also set fetchFile: null to disable the entrypoint if you are using src/fetch.ts for another purpose, or don’t need advanced routing features.

If you have been waiting for stabilization before using advanced routing, you can now do so.

Please see the advanced routing guide in docs for more about this feature.
#16725 10229f7 Thanks @ArmandPhilippot! - Removes deprecated APIs exported from astro:transitions.

In Astro 6.x, some helpers available in astro:transitions and astro:transitions/client were deprecated.

In Astro 7.0, the following APIs can no longer be used in your project:
- TRANSITION_BEFORE_PREPARATION
- TRANSITION_AFTER_PREPARATION
- TRANSITION_BEFORE_SWAP
- TRANSITION_AFTER_SWAP
- TRANSITION_PAGE_LOAD
- isTransitionBeforePreparationEvent()
- isTransitionBeforeSwapEvent()
- createAnimationScope()

What should I do?

Remove any occurrence of createAnimationScope():

-import { createAnimationScope } from 'astro:transitions';

Replace any occurrence of the other APIs using the lifecycle event names directly:

-import {
-	TRANSITION_AFTER_SWAP,
-	isTransitionBeforePreparationEvent,
-} from 'astro:transitions/client';

-console.log(isTransitionBeforePreparationEvent(event));
+console.log(event.type === 'astro:before-preparation');

-console.log(TRANSITION_AFTER_SWAP);
+console.log('astro:after-swap');

Learn more about all utilities available in the View Transitions Router API Reference.

Minor Changes

#16998 57dcc31 Thanks @matthewp! - Exposes getFetchState() from astro/hono as a public API

The getFetchState() function retrieves or lazily creates a FetchState from a Hono context object. This allows third-party packages to build Hono middleware that interacts with Astro's per-request state, giving the astro/hono API the same extensibility as astro/fetch.
```
import { Hono } from 'hono';
import { getFetchState, pages } from 'astro/hono';

const app = new Hono();

app.use(async (context, next) => {
  const state = getFetchState(context);
  state.locals.message = 'Hello from custom middleware';
  await next();
});

app.use(pages());

export default app;
```
#16996 300641e Thanks @florian-lefebvre! - Adds a subset field to the FontData type exposed via fontData from astro:assets. When using multiple font subsets (e.g., subsets: ["latin", "korean"]), each font data entry now includes the subset name, making it possible to distinguish between font entries for different subsets that share the same weight and style.
#16745 f864a80 Thanks @ematipico! - The custom logger feature introduced behind a flag in v6.2.0 is no longer experimental and is available for general use.

This feature provides better control over Astro's logging infrastructure by allowing you to replace the default console output with custom logging implementations (e.g., structured JSON). This is particularly useful for on-demand rendering when connecting to log aggregation services such as Kibana, Logstash, CloudWatch, Grafana, or Loki.

Astro provides three built-in log handlers (json, node, and console), and you can also create your own.

JSON logging

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

export default defineConfig({
  logger: logHandlers.json({
    pretty: true,
    level: 'warn',
  }),
});

Custom logger

import { defineConfig } from 'astro/config';

export default defineConfig({
  logger: {
    entrypoint: '@&#8203;org/custom-logger',
  },
});

Additionally, context.logger is now always available in API routes and middleware, even without a custom logger configured.

If you were previously using this feature, please remove the experimental flag from your Astro config:

import { defineConfig } from 'astro/config';

export default defineConfig({
-  experimental: {
-    logger: {
-      entrypoint: '@&#8203;org/custom-logger',
-    },
-  },
+  logger: {
+    entrypoint: '@&#8203;org/custom-logger',
+  },
});

If you have been waiting for stabilization before using custom loggers, you can now do so.

Please see the Logger docs for more about this feature.

#16981 0d6d644 Thanks @ematipico! - Removes the setting experimental.queuedRendering. The new rendering engine is now stable and replaces the old one.

As part of the stabilization, the queued rendering has been improved, and some features have been removed:
- The construction of the queue has been removed, instead now Astro uses a streaming approach where components are rendered and flushed as they are encountered.
- The node polling feature has been removed because it doesn't yield concrete savings.
- The content cache has been descoped, and how only tag names are cached.
  If you were previously using this experimental feature, you must remove this experimental flag from your configuration as it no longer exists:
```
// astro.config.mjs
import { defineConfig } from "astro/config";

export default defineConfig({
  experimental: {
-    queuedRendering: {}
  }
});
```
#17116 f95e58e Thanks @ascorbic! - Stabilizes route caching, removing the experimental.cache and experimental.routeRules flags and replacing them with the top-level cache and routeRules configuration options.

Route caching, introduced experimentally in v6.0.0, is now stable. It gives you a platform-agnostic way to cache responses from on-demand rendered pages and endpoints, based on standard HTTP caching semantics.

Update your config to move cache and routeRules out of the experimental block:
```
// astro.config.mjs
import { defineConfig, memoryCache } from 'astro/config';

export default defineConfig({
-  experimental: {
-    cache: {
-      provider: memoryCache(),
-    },
-    routeRules: {
-      '/blog/[...path]': { maxAge: 300, swr: 60 },
-    },
-  },
+  cache: {
+    provider: memoryCache(),
+  },
+  routeRules: {
+    '/blog/[...path]': { maxAge: 300, swr: 60 },
+  },
});
```
Set caching directives in your routes with Astro.cache (in .astro pages) or context.cache (in API routes and middleware), and Astro translates them into the appropriate headers or runtime behavior depending on your configured cache provider. You can also define cache rules for routes declaratively in your config using routeRules, without modifying route code.

See the route caching guide for more information.

Patch Changes

#16980 1f07343 Thanks @matthewp! - Removes state.provide(), state.resolve(), state.finalizeAll(), and App.Providers from the public advanced routing API. These context provider extension points are now internal-only. If you were using them in an integration, use locals to share per-request state instead.
#17111 c0f33ed Thanks @ematipico! - Harden the limits on the number of decoding on the URL.
#16982 1e000e2 Thanks @matthewp! - Improves the warning when accessing Astro.session without session storage configured. The session property is now always defined on the context object, and accessing it without configuration logs a helpful message instead of silently returning undefined.
#16335 9a53f77 Thanks @ascorbic! - Adds shared helper utilities for CDN cache provider authors for route caching

Exports astro/cache/provider-utils with helpers for building platform-specific cache-control headers, generating path-based invalidation tags, and normalizing invalidation options. These are used internally by the first-party Netlify, Vercel, and Cloudflare cache providers.
#17095 e84ebc0 Thanks @matthewp! - Improves build performance by removing an unfiltered transform hook from the astro:head-metadata-build plugin. Head propagation modules are now identified by their module ID (?astroPropagatedAssets) instead of scanning every module's source code.
#17041 4c4a91c Thanks @iseraph-dev! - Fixes a bug where the advanced routing astro/hono / astro/fetch pages() handler returned the host framework's default Internal Server Error response instead of rendering the custom 500.astro page when a page threw during render. Unmatched requests with a prerendered (or absent) custom 404 page now render the 404 error page instead of failing the same way.
#17097 5e340d7 Thanks @iseraph-dev! - Fixes a bug where the advanced routing astro/hono / astro/fetch middleware() handler returned the host framework's default Internal Server Error response instead of rendering the custom 500.astro page when middleware threw. Unmatched requests with a prerendered (or absent) custom 404 page now render the 404 error page instead of failing the same way. Errors surfaced through next (the host framework's downstream chain) still propagate to the host's own error handler.
#15819 cafec4e Thanks @delucis! - Fixes --port flag being ignored after a Vite-triggered server restart (e.g. when a .env file changes)
#17104 b074a37 Thanks @iseraph-dev! - Fixes the custom 500.astro page receiving an empty error prop when the error originated in middleware.
#17078 04547ec Thanks @astrobot-houston! - Fixes a spurious Astro.request.headers warning on prerendered pages when security.allowedDomains is configured. The internal allowedDomains header validation now skips prerendered routes, since they use synthetic requests with no real headers.
#16603 deaaf3f Thanks @alexanderniebuhr! - Removes the warning that Astro does not support vite v8, since Astro v7 does support vite v8
#16335 9a53f77 Thanks @ascorbic! - Passes the Request object to CacheProvider.setHeaders() for route caching

Cache providers now receive the incoming Request as a second argument to setHeaders(options, request). This allows CDN providers to read the request URL, headers, and other properties when generating cache response headers, for example to auto-tag responses with their pathname for path-based invalidation.
#17098 637a1b6 Thanks @matthewp! - Fixes internal Astro headers leaking from direct pages() handler responses
#17090 3cf76c0 Thanks @matthewp! - Fixes Vite and Rolldown build warnings
#16434 [ee079d4](https://redirect.github.com/withastro/astro/commit/ee07

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

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.

vercel · 2026-03-10T13:06:47Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
patchwork	Ready	Preview, Comment	Jun 22, 2026 6:28pm

vercel Bot deployed to Preview March 10, 2026 13:07 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 85ea1da to 405eb1b Compare March 10, 2026 18:08

renovate Bot changed the title ~~fix(deps): update astro monorepo (major)~~ fix(deps): update dependency astro to v6 Mar 10, 2026

vercel Bot had a problem deploying to Preview March 10, 2026 18:08 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 405eb1b to 2f3266c Compare March 10, 2026 21:32

renovate Bot changed the title ~~fix(deps): update dependency astro to v6~~ fix(deps): update astro monorepo (major) Mar 10, 2026

vercel Bot deployed to Preview March 10, 2026 21:32 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 2f3266c to 39479d4 Compare March 11, 2026 22:03

vercel Bot deployed to Preview March 11, 2026 22:04 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 39479d4 to 8ef514f Compare March 12, 2026 04:57

vercel Bot deployed to Preview March 12, 2026 04:58 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 8ef514f to 686e0f6 Compare March 12, 2026 14:06

vercel Bot deployed to Preview March 12, 2026 14:07 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 686e0f6 to 3ea6fe5 Compare March 12, 2026 17:06

vercel Bot deployed to Preview March 12, 2026 17:07 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 3ea6fe5 to 7cc9a6e Compare March 12, 2026 21:59

vercel Bot deployed to Preview March 12, 2026 21:59 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 7cc9a6e to ea52eb7 Compare March 16, 2026 15:02

vercel Bot deployed to Preview March 16, 2026 15:02 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from ea52eb7 to 4b5d974 Compare March 18, 2026 17:10

vercel Bot deployed to Preview March 18, 2026 17:11 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 4b5d974 to fb89a0a Compare March 19, 2026 21:55

vercel Bot deployed to Preview March 19, 2026 21:55 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from fb89a0a to 91fe3a9 Compare March 20, 2026 22:15

vercel Bot deployed to Preview March 20, 2026 22:15 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 91fe3a9 to 90af55f Compare March 26, 2026 14:39

vercel Bot deployed to Preview March 26, 2026 14:40 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 90af55f to 42c306e Compare March 26, 2026 21:31

vercel Bot deployed to Preview March 26, 2026 21:32 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 6a1dd66 to cbd247f Compare April 10, 2026 09:59

vercel Bot deployed to Preview April 10, 2026 09:59 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from cbd247f to 4f09c27 Compare April 13, 2026 18:49

vercel Bot deployed to Preview April 13, 2026 18:50 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 4f09c27 to b0413b0 Compare April 15, 2026 18:58

vercel Bot deployed to Preview April 15, 2026 18:59 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from b0413b0 to 3d9bb91 Compare April 18, 2026 13:48

vercel Bot deployed to Preview April 18, 2026 13:48 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 3d9bb91 to 117cfbe Compare April 22, 2026 20:50

vercel Bot deployed to Preview April 22, 2026 20:50 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 117cfbe to f18beb0 Compare April 28, 2026 17:42

vercel Bot deployed to Preview April 28, 2026 17:43 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from f18beb0 to 85ca381 Compare April 29, 2026 12:44

vercel Bot deployed to Preview April 29, 2026 12:45 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 85ca381 to 81d19da Compare April 30, 2026 11:07

vercel Bot deployed to Preview April 30, 2026 11:08 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 81d19da to 8aa5ed8 Compare April 30, 2026 19:33

vercel Bot deployed to Preview April 30, 2026 19:33 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 8aa5ed8 to 309931f Compare May 4, 2026 14:01

vercel Bot deployed to Preview May 4, 2026 14:01 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 309931f to 6657be4 Compare May 5, 2026 19:50

vercel Bot deployed to Preview May 5, 2026 19:50 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 6657be4 to d222629 Compare May 9, 2026 23:57

vercel Bot deployed to Preview May 9, 2026 23:57 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from d222629 to 5eb8cc2 Compare May 10, 2026 00:49

vercel Bot deployed to Preview May 10, 2026 00:49 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 5eb8cc2 to a02f759 Compare May 12, 2026 01:09

vercel Bot deployed to Preview May 12, 2026 01:09 View deployment

renovate Bot force-pushed the renovate/major-astro-monorepo branch from a02f759 to 061561d Compare May 13, 2026 21:51

fix(deps): update astro monorepo

230837e

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update astro monorepo (major)#10

fix(deps): update astro monorepo (major)#10
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-astro-monorepo

renovate Bot commented Mar 10, 2026 •

edited

Loading

Uh oh!

vercel Bot commented Mar 10, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Mar 10, 2026 • 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

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

What should I do?

Minor Changes

Patch Changes

Major Changes

Minor Changes

Setup

Caching responses

Invalidation

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Major Changes

New flag and subcommands

What should I do?

What should I do?

Minor Changes

JSON logging

Custom logger

Patch Changes

Configuration

Uh oh!

vercel Bot commented Mar 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Mar 10, 2026 •

edited

Loading

vercel Bot commented Mar 10, 2026 •

edited

Loading