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.2`

Compare Source

Patch Changes

#17252 eb6f97e Thanks @matthewp! - Fixes trailing-slash handling for request paths that begin with a backslash

With trailingSlash: 'always', the standalone Node server could append a trailing slash to a request path that begins with a backslash (for example /\example.com/foo) and echo that path back in the Location header of a 301 response. Because browsers resolve a leading \ the same way as /, the resulting Location could point off-site.

Such paths are now recognized as internal paths, matching the existing handling for paths that begin with //, so they are no longer rewritten with a trailing slash.
Updated dependencies [eb6f97e]:
- @astrojs/internal-helpers@0.10.1

`v11.0.1`

Compare Source

Patch Changes

#17249 02b73b0 Thanks @ematipico! - Fixes an issue where the peerDependencies field used incorrect dependencies.

`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.3`

Compare Source

Patch Changes

#17370 3a43cf0 Thanks @matthewp! - Improves internal ISR route handling

`v11.0.2`

Compare Source

Patch Changes

Updated dependencies [eb6f97e]:
- @astrojs/internal-helpers@0.10.1

`v11.0.1`

Compare Source

Patch Changes

#17249 02b73b0 Thanks @ematipico! - Fixes an issue where the peerDependencies field used incorrect dependencies.

`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.1.0`

Minor Changes

#17302 5f4dc03 Thanks @astrobot-houston! - Adds a new deferRender option to the glob() content loader

When set to true, renderable entries (such as Markdown) are not rendered during content sync. Instead, rendering is deferred until the entry is actually rendered in a page, using the same on-demand path that .mdx files already use.

This reduces memory usage during astro build for large collections whose rendered output is much larger than the source — for example, Markdown that uses heavy rehype plugins like rehype-katex. Such builds could previously run out of memory while storing the eagerly-rendered HTML for every entry.
```
// src/content.config.ts
import { defineCollection } from 'astro:content';
import { glob } from 'astro/loaders';

const docs = defineCollection({
  loader: glob({ pattern: '**/*.md', base: 'src/content/docs', deferRender: true }),
});
```
By default deferRender is false, preserving the existing behavior of rendering entries eagerly during sync so their rendered HTML can be cached across builds.
#17296 30698a2 Thanks @ematipico! - Adds a new experimental collectionStorage option for controlling how the content layer persists its data store

By default, Astro serializes the entire content layer data store to a single file (.astro/data-store.json). For very large content collections, this file can grow large enough to hit platform file-size limits.

Set experimental.collectionStorage: 'chunked' to instead split the data store across many smaller, content-addressed files inside a .astro/data-store/ directory, described by a manifest:
```
// astro.config.mjs
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
    collectionStorage: 'chunked',
  },
});
```
Because each part file is named by a hash of its contents, unchanged parts keep the same name across builds and are not rewritten, and identical parts are deduplicated. The default value is 'single-file', which preserves the current behavior.
#17214 44c4989 Thanks @ematipico! - Adds support for the more specific CSP directives script-src-elem, script-src-attr, style-src-elem, and style-src-attr through a new kind option.

Previously, CSP was only scoped to generic script-src/style-src directives. Now each source or hash can be scoped to a narrower directive — for example, to allow inline style attributes (such as those from define:vars or Shiki) without loosening the policy for your <style> and <link> elements.

Scoping sources and hashes in your config

Each entry in resources and hashes can be an object with a kind property. Depending on whether you use scriptDirective or styleDirective, "element" targets script-src-elem or style-src-elem, "attribute" targets script-src-attr or style-src-attr, and "default" (the same as a bare string or hash) targets script-src or style-src.

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

export default defineConfig({
  security: {
    csp: {
      scriptDirective: {
        resources: [{ resource: 'https://cdn.example.com', kind: 'element' }],
      },
      styleDirective: {
        resources: [{ resource: "'unsafe-inline'", kind: 'attribute' }],
      },
    },
  },
});

Scoping at runtime

The same kind option is available on the runtime CSP API, where the existing methods now also accept an object:

ctx.csp.insertScriptResource({ resource: 'https://cdn.example.com', kind: 'element' });
ctx.csp.insertStyleResource({ resource: "'unsafe-inline'", kind: 'attribute' });

#17258 84814d4 Thanks @astrobot-houston! - Adds a new format() option to the paginate utility. The format() option is a function that accepts the current URL of the page, and returns a new URL.

For example, when your host only supports URLs using the .html extension, you can use format() to add it to the generated URLs:

---
export async function getStaticPaths({ paginate }) {
  // Load your data with fetch(), getCollection(), etc.
  const response = await fetch(`https://pokeapi.co/api/v2/pokemon?limit=150`);
  const result = await response.json();
  const allPokemon = result.results;

  // Return a paginated collection of paths for all items
  return paginate(allPokemon, {
    pageSize: 10,
    format: (url) => `${url}.html`,
  });
}

const { page } = Astro.props;
---

#17331 7db6420 Thanks @matthewp! - Adds a --ignore-lock flag to astro dev for starting a dev server without checking or writing the lock file, so it can run alongside an already-running dev server for the same project.

The new instance is not tracked by astro dev stop, astro dev status, or astro dev logs. --ignore-lock cannot be combined with --background (or an auto-detected AI agent environment, which runs dev servers in the background automatically) or --force, since those rely on the lock file.
```
astro dev --ignore-lock
```
#17389 16de021 Thanks @florian-lefebvre! - Allows passing URL entrypoints when configuring the logger

Matching other APIs like session drivers or font providers, the logger entrypoint can now be a URL:
```
import { defineConfig } from 'astro/config';

export default defineConfig({
  logger: {
    entrypoint: new URL('./logger.js', import.meta.url),
  },
});
```

Patch Changes

#17332 4407483 Thanks @astrobot-houston! - Fixes the JSON logger crashing with process is not defined in non-Node runtimes like Cloudflare's workerd. The JSON logger now uses console.log/console.error instead of process.stdout/process.stderr, matching the pattern already used by the console logger.
#17391 186a1e7 Thanks @florian-lefebvre! - Fixes a case where an integration could not update the logger with updateConfig()
#17394 d9f99e1 Thanks @matthewp! - Fixes element-specific CSP directives to preserve the existing behavior of configured script and style resources
#17374 b2d1b3e Thanks @astrobot-houston! - Fixes dev server returning 404 for ?url imported assets when accessed via browser navigation
#17390 ed71eaf Thanks @florian-lefebvre! - Removes an unused and undocumented generic from the AstroLoggerDestination type
#17393 092da56 Thanks @matthewp! - Hardens generated transition styles, development metadata, and server island URLs when embedding dynamic values

`v7.0.9`

Compare Source

Patch Changes

#17286 a249317 Thanks @astrobot-houston! - Fixes the first browser visit after astro dev starts triggering an immediate full page reload
#17369 a94d4a5 Thanks @adamchal! - Fixes an issue where a client island could permanently fail to hydrate if the first attempt to load its component failed. Islands now reliably recover from transient import failures, which previously did not work for React components during astro dev.

`v7.0.8`

Compare Source

Patch Changes

#17363 3f4efc5 Thanks @astrobot-houston! - Fixes astro preview --open not opening a browser when using an adapter with a custom preview entrypoint, such as @astrojs/cloudflare
#17313 e2e319d Thanks @ronits2407! - Exposes the AstroRuntimeLogger interface to allow users to properly type the logger functions at runtime.
#17328 025cc74 Thanks @matthewp! - Fixes astro dev --force not replacing an already-running dev server
#17353 2bba277 Thanks @ematipico! - Updates the Astro compiler to the latest version, which fixes many regressions. Refer to the changelog for more details.
#17344 79a41e0 Thanks @adamchal! - Improves rendering performance for pages with many component instances, such as repeated MDX <Content /> components.
Updated dependencies [64b0d66]:
- @astrojs/markdown-satteri@0.3.4

`v7.0.7`

Compare Source

Patch Changes

#17318 23a4120 Thanks @astrobot-houston! - Fixes CSS module scoped-name hash mismatch in astro dev when using vite.css.transformer: 'lightningcss' with content collections. Previously, a component importing a CSS module and rendered via content collection render() would get different class name hashes in the element and the injected <style> tag, causing styles not to apply.
#17323 4298883 Thanks @ematipico! - Fixes a dev server memory leak which caused Node.js to emit warnings in the console.
#17323 4298883 Thanks @ematipico! - Fixes a dev server crash when a .html or /index.html suffixed request (such as those netlify dev probes as pretty-URL fallbacks) matched a dynamic endpoint route, causing a TypeError: Missing parameter error
#17325 cebc404 Thanks @astrobot-houston! - Fixes a bug where CSS @import rules could end up mid-stylesheet after inline CSS chunks were merged during build, causing browsers to silently ignore them
#17323 4298883 Thanks @ematipico! - Fixes a build regression that could leave unresolved preload markers in inlined scripts with external dynamic imports
Updated dependencies [4298883, 4298883]:
- @astrojs/telemetry@3.3.3

`v7.0.6`

Compare Source

Patch Changes

#17261 79aa99c Thanks @astrobot-houston! - Fixes a false deprecation warning for markdown.gfm and markdown.smartypants when using the Container API
#17247 f94280d Thanks @chatman-media! - Fixes route generation throwing "Missing parameter" (or silently dropping the segment) when a dynamic param's value is 0. The generator used truthy checks instead of checking for undefined, so paginate(posts, { params: { categoryId: 0 } }) would crash even though 0 is a perfectly valid param value.
#17278 6f11739 Thanks @astrobot-houston! - Fixes missing CSS for virtual style modules (e.g., responsive image layout styles) in dev mode when JavaScript is disabled
#17250 0b30b35 Thanks @matthewp! - Fixes the security.checkOrigin check so it is applied consistently to Astro Actions and on-demand endpoints, regardless of how the request pipeline is composed. Previously, the origin check could be skipped in the composable astro/hono pipeline depending on the order of the middleware() primitive (or when it was omitted).
#17274 8c3579b Thanks @astrobot-houston! - Fixes missing render() type overload for live collection entries. Previously, calling render() on a LiveDataEntry produced a TypeScript error when using only live.config.ts without a content.config.ts.
#17257 4208297 Thanks @astrobot-houston! - Fixes astro check failing to find @astrojs/check and typescript when astro is installed in a directory outside the project tree (e.g. pnpm virtual store)
#17272 b428648 Thanks @matthewp! - Fixes island component paths so that extensionless imports (e.g. import { Counter } from '../components/Counter') resolve to the real file on disk, matching Vite's extension order and directory index resolution. This makes the include/exclude options of JSX renderer integrations (React, Preact, Solid) match components imported without a file extension, and removes the spurious React 19 "Invalid hook call" warning logged on every request in dev when include was set alongside another JSX renderer
#17279 2aeaa44 Thanks @astrobot-houston! - Fixes a bug where <Picture inferSize> with a remote image could fail with FailedToFetchRemoteImageDimensions when the image server rate-limits requests (e.g. HTTP 429). Remote dimensions are now resolved once

✂ 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	Jul 16, 2026 1:00pm

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

2ebf978

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

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

Patch Changes

Patch 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

Minor Changes

Scoping sources and hashes in your config

Scoping at runtime

Patch Changes

Patch Changes

Patch Changes

Patch Changes

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