Skip to content

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

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-astro-monorepo
Open

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

Conversation

@renovate

@renovate renovate Bot commented May 31, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@astrojs/cloudflare (source) 13.0.0-beta.14 → 14.1.2 age confidence
@astrojs/mdx (source) 5.0.0-beta.12 → 7.0.2 age confidence

Release Notes

withastro/astro (@​astrojs/cloudflare)

v14.1.2

Compare Source

Patch Changes

  • #​17323 4298883 Thanks @​ematipico! - Fixes build-time image optimization ignoring a custom image service registered by an integration

    Previously, when using imageService: 'compile' or imageService: 'custom', a custom image service was only respected if it was set directly in the image.service option of astro.config. If an integration registered the service instead, images were silently optimized with the default Sharp service at build time. A custom image service now transforms your images at build time no matter how it was configured.

  • #​17323 4298883 Thanks @​ematipico! - Prebundles astro/components and the <ClientRouter /> transition runtime modules in the dev server environment so pages using them no longer trigger a mid-session dep optimizer reload, which caused React "Invalid hook call" errors in islands on the first request after a cold cache

  • #​17323 4298883 Thanks @​ematipico! - Fixes an issue where vars weren't available at build time. Now the adapter loads vars from the Wrangler config so astro:env public variables resolve at build time

  • Updated dependencies []:

v14.1.1

Compare Source

Patch Changes

v14.1.0

Compare Source

Minor Changes

  • #​17099 fdab7ce Thanks @​adamchal! - Adds configured image service support with the compile and custom options.

    The Cloudflare adapter supports various options that affect how images are processed for both pre-rendered and on-demand routes:

    • Setting imageService: 'compile' now ensures it is used for pre-rendered routes. When no custom image service is defined, the behavior remains unchanged.
    • With imageService: 'custom', assets are now processed at build time for pre-rendered routes. If you have configured an image service, it will be bundled to handle images at runtime; otherwise, the behavior remains unchanged.
    • The other imageService options remain unchanged.

    Learn more about the image service options available in the Cloudflare adapter guide.

Patch Changes

v14.0.2

Compare Source

Patch Changes

  • #​17049 ffceaa2 Thanks @​astrobot-houston! - Fixes prerender errors being silently swallowed when pages throw during rendering in workerd, causing astro build to exit 0 and emit truncated HTML. The response body is now fully buffered inside workerd before being sent back to the build process, so streaming errors are caught and surfaced as build failures with clear error messages.

  • Updated dependencies []:

v14.0.1

Compare Source

Patch Changes

v14.0.0

Compare Source

Major Changes
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 '@&#8203;astrojs/cloudflare';
import { cacheCloudflare } from '@&#8203;astrojs/cloudflare/cache';

export default defineConfig({
  adapter: cloudflare(),
  cache: {
    provider: cacheCloudflare(),
  },
});

The adapter automatically enables the Worker caching layer when a Cloudflare cache provider is configured. No manual wrangler.jsonc changes are needed.

Caching responses

Use Astro.cache.set() in your pages and API routes to cache responses. The provider sets Cloudflare-CDN-Cache-Control and Cache-Tag headers, which are read by Cloudflare's built-in caching layer. Cache hits bypass Worker execution entirely, meaning your Worker is not invoked for cached 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: cacheCloudflare() },
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 (implemented via an auto-generated path tag)
await cache.invalidate({ path: '/products/123' });

Both tag-based and path-based invalidation are supported.

Patch Changes

v13.7.0

Compare Source

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 []:

v13.6.1

Compare Source

Patch Changes

v13.6.0

Compare Source

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 '@&#8203;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 '@&#8203;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.

Patch Changes

  • #​16868 f9bae95 Thanks @​helio-cf! - Fixes user options passed to cloudflare({...}) (remoteBindings, inspectorPort, persistState, configPath, auxiliaryWorkers) being silently ignored during astro preview. The adapter now resolves the full @cloudflare/vite-plugin config once at integration setup time and reuses that single resolved value across the dev/build plugin, the prerenderer's preview server, and the astro preview entrypoint, so user options can no longer be dropped at one of the call sites.

  • #​16468 4cff3a1 Thanks @​matthewp! - Fixes static Cloudflare builds with server islands or image endpoints that failed at preview time due to mismatched output directories.

  • Updated dependencies [f732f3c]:

v13.5.5

Compare Source

Patch Changes

v13.5.4

Compare Source

Patch Changes

  • #​16769 428cb1b Thanks @​astrobot-houston! - Forwards user-provided optimizeDeps settings (exclude, include, esbuildOptions.loader) to SSR/prerender environments. Previously, top-level vite.optimizeDeps in the Astro config was silently ignored for server environments because Vite 6 scopes it to client-only and the adapter's configEnvironment hook did not forward it. This caused packages with non-standard file types (e.g. .data files) to fail during dev-mode dependency optimization with errors like "No loader is configured for '.data' files".

  • Updated dependencies []:

v13.5.3

Compare Source

Patch Changes

v13.5.2

Compare Source

Patch Changes

v13.5.1

Compare Source

Patch Changes

  • #​16707 2ff3f8f Thanks @​helio-cf! - Fixes remoteBindings: false being ignored during astro build. The Cloudflare prerenderer's internal Vite preview server now receives the user's adapter options, so remote-flagged bindings (e.g. a D1 database with remote: true in wrangler.toml) are emulated locally during build, matching the existing astro dev behavior.

  • #​16652 98c32cc Thanks @​greatjourney589! - Fixes user-declared KV namespace bindings being duplicated in the generated dist/server/wrangler.json, which caused wrangler validation to fail with " assigned to multiple KV Namespace bindings." The Astro Cloudflare config customizer now returns only the auto-injected SESSION binding and lets @cloudflare/vite-plugin merge it with the user's wrangler config, instead of pre-merging the user's bindings into the output.

  • #​16272 4f9521e Thanks @​barry3406! - Fixes .astro files failing with No matching export in "html:..." for import "default" when default-imported from a .ts file

  • #​15723 9256345 Thanks @​rururux! - Fixes an issue where the <Prism /> component failed to work in Cloudflare Workers.

  • Updated dependencies [d365c97]:

v13.5.0

Compare Source

Minor Changes

v13.4.0

Compare Source

Minor Changes

  • #​16519 1b1c218 Thanks @​louisescher! - Adds support for redirecting URLs in remote image optimization.

    Previously, when a remote image URL meant to be optimized by Astro led to a redirect, Astro would fail silently and ignore the redirect. Now, Astro tracks up to 10 redirects for these images. If any of the redirects are not covered by a pattern in image.remotePatterns or a domain in image.domains, Astro will fail with a helpful error message.

    In the following example, the first image would be loaded successfully, while the second would lead to Astro throwing an error:

    export default defineConfig({
  image: {
    domains: ['example.com', 'cdn.example.com'],
  },
});
    {
  /* Redirects to https://cdn.example.com/assets/image.png: */
}
<Image
  src="https://example.com/assets/image.png"
  width="1920"
  height="1080"
  alt="An example image."
/>;

{
  /* Redirects to https://malicious.com/image.png: */
}
<Image
  src="https://example.com/bad-image.png"
  width="1920"
  height="1080"
  alt="An example image."
/>;

    In cases where all redirects to HTTPS hosts should be trusted, the following configuration for image.remotePatterns can be used:

    export default defineConfig({
  image: {
    remotePatterns: [
      {
        protocol: 'https',
      },
    ],
  },
});
Patch Changes

v13.3.1

Compare Source

Patch Changes

v13.3.0

Compare Source

Minor Changes

  • #​16187 fe58071 Thanks @​gllmt! - Adds a waitUntil option to the RenderOptions so that adapters can forward runtime background-task hooks to Astro.

    When provided by an adapter, runtime cache providers receive context.waitUntil in
    CacheProvider.onRequest(), which allows background cache work such as stale-while-revalidate
    without blocking the response. The Cloudflare adapter now forwards
    ExecutionContext.waitUntil to this API.

  • #​16290 a49637a Thanks @​ViVaLaDaniel! - Ensures that server.allowedHosts (and vite.preview.allowedHosts) configuration is respected when using astro preview with the @astrojs/cloudflare adapter. This improves security by preventing DNS rebinding attacks when previewing Cloudflare builds locally.

Patch Changes

v13.2.2

Compare Source

Patch Changes

  • #​16498 4efe020 Thanks @​matthewp! - Fixes the dependency scan failing with "No matching export for import 'default'" when a .ts file default-imports an .astro component

    The esbuild scan plugin now includes export default {} in its output for .astro files, preventing the scan from failing and ensuring all dependencies are discovered ahead of time.

  • Updated dependencies []:

v13.2.1

Compare Source

Patch Changes
  • #​16458 8cb1f42 Thanks @​matthewp! - Fixes Cloudflare dev and build failures caused by @cloudflare/vite-plugin defaulting compatibility_date to today's date, which can exceed the maximum date supported by the bundled workerd binary

v13.2.0

Compare Source

Minor Changes

  • #​16435 c4d321b Thanks @​jamesopstad! - Add support for Preview deployments (currently in private beta)

    Non-inheritable bindings set internally by the Cloudflare adapter are now also set in the previews section of the config so that they are inherited by Preview deployments.

Patch Changes

v13.1.10

Compare Source

Patch Changes

v13.1.9

Compare Source

Patch Changes

v13.1.8

Compare Source

Patch Changes

  • #​16225 756e7be Thanks @​travisbreaks! - Fixes ERR_MULTIPLE_CONSUMERS error when using Cloudflare Queues with prerendered pages. The prerender worker config callback now excludes queues.consumers from the entry worker config, since the prerender worker only renders static HTML and should not register as a queue consumer. Queue producers (bindings) are preserved.

  • #​16192 79d86b8 Thanks @​alexanderniebuhr! - Removes an unused function re-export from the /info package path

  • Updated dependencies []:

v13.1.7

Compare Source

Patch Changes

v13.1.6

Compare Source

Patch Changes
  • #​16151 4978165 Thanks @​matthewp! - Fixes a dev-mode crash loop in the Cloudflare adapter when using Starlight by excluding @astrojs/starlight from SSR dependency optimization

v13.1.5

Compare Source

Patch Changes

v13.1.4

Compare Source

Patch Changes

  • #​16041 56d2bde Thanks @​kylemclean! - Fixes unnecessary prerendering of redirect destinations

    Unnecessary files are no longer generated by static builds for redirected routes.

    Requests are no longer made at build time to external redirect destination URLs, which could cause builds to fail.

  • Updated dependencies []:

v13.1.3

Compare Source

Patch Changes

v13.1.2

Compare Source

Patch Changes

v13.1.1

Compare Source

Patch Changes

v13.1.0

Compare Source

Minor Changes

  • #​15711 b2bd27b Thanks @​OliverSpeir! - Adds a prerenderEnvironment option to the Cloudflare adapter.

    By default, Cloudflare uses its workerd runtime for prerendering static pages. Set prerenderEnvironment to 'node' to use Astro's built-in Node.js prerender environment instead, giving prerendered pages access to the full Node.js ecosystem during both build and dev. This is useful when your prerendered pages depend on Node.js-specific APIs or NPM packages that aren't compatible with workerd.

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

export default defineConfig({
  adapter: cloudflare({
    prerenderEnvironment: 'node',
  }),
});
Patch Changes

  • #​15845 50fcc8b Thanks @​aqiray! - fix: show actionable error when running astro preview without prior build

  • #​15794 d1ac58e Thanks @​OliverSpeir! - Fixes image serving in passthrough mode by using the Cloudflare ASSETS binding instead of generic fetch, which does not work in Workers for local assets

  • #​15850 660da74 Thanks @​tristanbes! - fix(cloudflare): forward configPath and other PluginConfig options to the Cloudflare Vite Plugin

    Options like configPath, inspectorPort, persistState, remoteBindings, and auxiliaryWorkers were accepted by the type system but never forwarded to cfVitePlugin(), making them silently ignored.

    Also fixes addWatchFile for configPath which resolved the path relative to the adapter's node_modules directory instead of the project root.

  • #​15843 fcd237d Thanks @​Calvin-LL! - fix cloudflare image transform ignoring quality parameter

  • Updated dependencies []:

v13.0.2

Patch Changes

v13.0.1

Patch Changes

v13.0.0

Compare Source

Major Changes
  • #​14306 141c4a2 Thanks @​ematipico! - Changes the API for creating a custom entrypoint, replacing the createExports() function with a direct export pattern.
What should I do?

If you're using a custom entryPoint in your Cloudflare adapter config, update your existing worker file that uses createExports() to reflect the new, simplified pattern:

my-entry.ts

import type { SSRManifest } from 'astro';
import { App } from 'astro/app';
import { handle } from '@&#8203;astrojs/cloudflare/handler';
import { DurableObject } from 'cloudflare:workers';

class MyDurableObject extends DurableObject<Env> {
  constructor(ctx: DurableObjectState, env: Env) {
    super(ctx, env);
  }
}

export function createExports(manifest: SSRManifest) {
  const app = new App(manifest);
  return {
    default: {
      async fetch(request, env, ctx) {
        await env.MY_QUEUE.send('log');
        return handle(manifest, app, request, env, ctx);
      },
      async queue(batch, _env) {
        let messages = JSON.stringify(batch.messages);
        console.log(`consumed from our queue: ${messages}`);
      },
    } satisfies ExportedHandler<Env>,
    MyDurableObject: MyDurableObject,
  };
}

To create the same custom entrypoint using the updated API, export the following function instead:

my-entry.ts

import { handle } from '@&#8203;astrojs/cloudflare/utils/handler';

export default {
  async fetch(request, env, ctx) {
    await env.MY_QUEUE.send("log");
    return handle(manifest, app, request, env, ctx);
  },
  async queue(batch, _env) {
    let messages = JSON.stringify(batch.messages);
    console.log(`consumed from our queue: ${messages}`);
  }
} satisfies ExportedHandler<Env>,

The manifest is now created internally by the adapter.

  • #​15435 957b9fe Thanks @​rururux! - Changes the default image service from compile to cloudflare-binding. Image services options that resulted in broken images in development due to Node JS incompatiblities have now been updated to use the noop passthrough image service in dev mode. - (Cloudflare v13 and Astro6 upgrade guidance)

  • #​15400 41eb284 Thanks @​florian-lefebvre! - Removes the workerEntryPoint option, which wasn't used anymore. Set the main field of your wrangler config instead

    See how to migrate

  • #​14306 141c4a2 Thanks @​ematipico! - Development server now runs in workerd

    astro dev now runs your Cloudflare application using Cloudflare's workerd runtime instead of Node.js. This means your development environment is now a near-exact replica of your production environment—the same JavaScript engine, the same APIs, the same behavior. You'll catch issues during development that would have only appeared in production, and features like Durable Objects, Workers Analytics Engine, and R2 bindings work exactly as they do on Cloudflare's platform.

New runtime

Previously, Astro.locals.runtime provided access to Cloudflare-specific APIs. These APIs have now moved to align with Cloudflare's native patterns.

What should I do?

Update occurrences of Astro.locals.runtime:

  • Astro.locals.runtime.env → Import env from cloudflare:workers
  • Astro.locals.runtime.cf → Access via Astro.request.cf
  • Astro.locals.runtime.caches → Use the global caches object
  • Astro.locals.runtime (for ExecutionContext) → Use Astro.locals.cfContext

Here's an example showing how to update your code:

Before:

---
const { env, cf, caches, ctx } = Astro.locals.runtime;
const value = await env.MY_KV.get('key');
const country = cf.country;
await caches.default.put(request, response);
ctx.waitUntil(promise);
---

<h1>Country: {country}</h1>

After:

---
import { env } from 'cloudflare:workers';

const value = await env.MY_KV.get('key');
const country = Astro.request.cf.country;
await caches.default.put(request, response);
Astro.locals.cfContext.waitUntil(promise);
---

<h1>Country: {country}</h1>

  • #​15345 840fbf9 Thanks @​matthewp! - Removes the cloudflareModules adapter option

    The cloudflareModules option has been removed because it is no longer necessary. Cloudflare natively supports importing .sql, .wasm, and other module types.

What should I do?

Remove the cloudflareModules option from your Cloudflare adapter configuration if you were using it:

import cloudflare from '@&#8203;astrojs/cloudflare';

export default defineConfig({
  adapter: cloudflare({
-   cloudflareModules: true
  })
});

  • #​14445 ecb0b98 Thanks @​florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)

  • #​15037 8641805 Thanks @​matthewp! - Updates the Wrangler entrypoint

    Previously, the main field in wrangler.jsonc pointed to the built output, since Wrangler only ran in production after the build completed:

    {
  "main": "dist/_worker.js/index.js",
}

    Now that Wrangler runs in both development (via workerd) and production, Astro provides a default entrypoint that works for both scenarios.

    What should I do?

    Update your wrangler.jsonc to use the new entrypoint:

    {
  "main": "@&#8203;astrojs/cloudflare/entrypoints/server",
}

    This single entrypoint handles both astro dev and production deployments.

  • #​15480 e118214 Thanks @​alexanderniebuhr! - Drops official support for Cloudflare Pages in favor of Cloudflare Workers

    The Astro Cloudflare adapter now only supports deployment to Cloudflare Workers by default in order to comply with Cloudflare's recommendations for new projects. If you are currently deploying to Cloudflare Pages, consider migrating to Workers by following the Cloudflare guide for an optimal experience and full feature support.

Minor Changes

  • #​15435 957b9fe Thanks @​rururux! - Adds support for configuring the image service as an object with separate build and runtime options

    It is now possible to set both a build-time and runtime service independently. Currently, 'compile' is the only available build time option. The supported runtime options are 'passthrough' (default) and 'cloudflare-binding':

    import { defineConfig } from 'astro/config';
import cloudflare from '@&#8203;astrojs/cloudflare';

export default defineConfig({
  adapter: cloudflare({
    imageService: { build: 'compile', runtime: 'cloudflare-binding' },
  }),
});

    See the Cloudflare adapter imageService docs for more information about configuring your image service.

  • #​15077 a164c77 Thanks @​matthewp! - Adds support for prerendering pages using the workerd runtime.

    The Cloudflare adapter now uses the new setPrerenderer() API to prerender pages via HTTP requests to a local preview server running workerd, instead of using Node.js. This ensures prerendered pages are built using the same runtime that serves them in production.

  • #​14306 141c4a2 Thanks [@​ematipico](https://redirect.github.com/ema

✂ 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.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented May 31, 2026 •
edited
Loading

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
❌ Deployment failed
View logs		 website 18fc75b Jul 11 2026, 07:00 PM

@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from ca7621e to b5e5d78 Compare June 1, 2026 22:15
@renovate renovate Bot changed the title fix(deps): update dependency @astrojs/mdx to v6 fix(deps): update astro monorepo to v6 Jun 2, 2026
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 022cd23 to a256546 Compare June 12, 2026 16:40
@renovate renovate Bot changed the title fix(deps): update astro monorepo to v6 fix(deps): update astro monorepo (major) Jun 22, 2026
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from db96126 to 06a0076 Compare June 28, 2026 17:09
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from e856569 to a653deb Compare July 5, 2026 22:53
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch from a653deb to 18fc75b Compare July 11, 2026 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants