fix(deps): update astro monorepo (major) by renovate[bot] · Pull Request #189 · ishinova/tobe.quest

renovate · 2025-03-02T22:02:08Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/cloudflare (source)	`11.2.0` → `13.1.4`
astro (source)	`4.16.19` → `6.1.1`

Release Notes

withastro/astro (@astrojs/cloudflare)

`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 []:
- @astrojs/underscore-redirects@1.0.2

Patch Changes

#15888 925252e Thanks @matthewp! - Fixes a bug where dependencies imported by prerender-only server:defer islands could remain as bare imports in server output, causing module resolution failures in preview and Cloudflare Workers.
#15934 6f8f0bc Thanks @ematipico! - Updates the Astro peerDependencies#astro to be 6.0.0.
#15875 c43ef8a Thanks @matthewp! - Include workerd response details in Cloudflare prerenderer errors to make getStaticPaths() failures easier to diagnose.
Updated dependencies []:
- @astrojs/underscore-redirects@1.0.1

`v13.1.1`

Compare Source

Patch Changes

#15815 d1872ee Thanks @matthewp! - Prebundle additional Astro runtime dependencies for Cloudflare development server, speeding up initial start time and preventing required restarts.
#15872 3b47b89 Thanks @Princesseuh! - Fixes images not working in dev mode when using the cloudflare option
Updated dependencies []:
- @astrojs/underscore-redirects@1.0.1

`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 []:
- @astrojs/underscore-redirects@1.0.1

`v13.0.2`

Patch Changes

#15832 95e12a2 Thanks @Princesseuh! - Fixes return; syntax not working in the frontmatter correctly in certain contexts
#15803 e42b015 Thanks @merlinnot! - Fixes the Cloudflare adapter adding a SESSION KV binding even when sessions are explicitly configured to use a different driver, such as unstorage/drivers/null.
Updated dependencies []:
- @astrojs/underscore-redirects@1.0.1

`v13.0.1`

Patch Changes

Updated dependencies [e20474b]:
- @astrojs/underscore-redirects@1.0.1

`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! - Adds support for astro preview command

Developers can now use astro preview to test their Cloudflare Workers application locally before deploying. The preview runs using Cloudflare's workerd runtime, giving you a staging environment that matches production exactly—including support for KV namespaces, environment variables, and other Cloudflare-specific features.
#15037 8641805 Thanks @matthewp! - The Wrangler configuration file is now optional. If you don't have custom Cloudflare bindings (KV, D1, Durable Objects, etc.), Astro will automatically generate a default configuration for you.

What should I do?

If your wrangler.jsonc only contains basic configuration like this:
```
{
  "main": "@&#8203;astrojs/cloudflare/entrypoints/server",
  "compatibility_date": "2026-01-28",
  "assets": {
    "directory": "./dist",
    "binding": "ASSETS",
  },
}
```
You can safely delete the file. Astro will handle this configuration automatically.

You only need a wrangler config file if you're using:
- KV namespaces
- D1 databases
- Durable Objects
- R2 buckets
- Environment variables
- Custom compatibility flags
- Other Cloudflare-specific features
#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.
#15556 8fb329b Thanks @florian-lefebvre! - Adds support for more @cloudflare/vite-plugin options

The adapter now accepts the following options from Cloudflare's Vite plugin:
- auxiliaryWorkers
- configPath
- inspectorPort
- persistState
- remoteBindings
- experimental.headersAndRedirectsDevModeSupport
For example, you can now set inspectorPort to provide a custom port for debugging your Workers:
```
// astro.config.mjs
import { defineConfig } from 'astro/config';
import cloudflare from '@&#8203;astrojs/cloudflare';

export default defineConfig({
  adapter: cloudflare({
    inspectorPort: 3456,
  }),
});
```

Patch Changes

#15044 7cac71b Thanks @florian-lefebvre! - Removes an exposed internal API of the preview server
#15080 f67b738 Thanks @gameroman! - Updates wrangler dependency to be a peerDependency over a dependency
#15039 6cc96e7 Thanks @matthewp! - Fixes static content deployment by moving it to another folder, so Wrangler can tell the static and worker content apart
#15452 e1aa3f3 Thanks @matthewp! - Fixes server-side dependencies not being discovered ahead of time during development

Previously, imports in .astro file frontmatter were not scanned by Vite's dependency optimizer, causing a "new dependencies optimized" message and page reload when the dependency was first encountered. Astro is now able to scan these dependencies ahead of time.
#15391 5d996cc Thanks @florian-lefebvre! - Fixes types of the handle() function exported from /handler, that could be incompatible with types generated by wrangler types
#15696 a9fd221 Thanks @Princesseuh! - Fixes duplicate logging showing up in some cases when prerendering pages
#15309 4b9c8b8 Thanks @ematipico! - Update the underneath @cloudflare/workers-types library to address a warning emitted by the package manager during the installation.
#15079 4463a55 Thanks @ascorbic! - Fixes auto-provisioning of default bindings (SESSION KV, IMAGES, and ASSETS). Default bindings are now correctly applied whether or not you have a wrangler.json file.
Previously, these bindings were only added when no wrangler config file existed. Now they are added in both cases, unless you've already defined them yourself.
#15694 66449c9 Thanks @matthewp! - Fixes deployment of static sites with the Cloudflare adapter

Fixes an issue with detecting and building fully static sites that caused deployment errors when using output: 'static' with the Cloudflare adapter
#15565 30cd6db Thanks @ematipico! - Fixes an issue where the use of the Code component would result in an unexpected error.
#15121 06261e0 Thanks @ematipico! - Fixes a bug where the Astro, with the Cloudflare integration, couldn't correctly serve certain routes in the development server.
#15026 90c608c Thanks @matthewp! - Improves prebundling of internal Astro modules
#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.
#15669 d5a888b Thanks @florian-lefebvre! - Removes the cssesc dependency

This CommonJS dependency could sometimes cause errors because Astro is ESM-only. It is now replaced with a built-in ESM-friendly implementation.
#15075 ee2c260 Thanks @matthewp! - Adds deprecation errors for Astro.locals.runtime properties to help migrate from Astro v5 to v6

When accessing the removed Astro.locals.runtime properties on Cloudflare, developers now receive clear error messages explaining the migration path:
- Astro.locals.runtime.env → Use import { env } from "cloudflare:workers"
- Astro.locals.runtime.cf → Use Astro.request.cf
- Astro.locals.runtime.caches → Use the global caches object
- Astro.locals.runtime.ctx → Use Astro.locals.cfContext
#15336 9cce92e Thanks @ascorbic! - Fixes a dev server issue where framework components from linked packages would fail to load with a 504 error.

This could occur when using client:only or other client directives with components from monorepo packages (linked via file: or workspace protocol). The first request would trigger Vite's dependency optimizer mid-request, causing concurrent client module requests to fail.
#15255 a66783a Thanks @florian-lefebvre! - Fixes a case where the types of handle() could mismatch with the ones from the user's project. They now rely on globals, that can be obtained by running wrangler types
#15045 31074fc Thanks @ematipico! - Fixes an issue where using the Vue integration with the Cloudflare adapter resulted in some runtime errors.
#15386 a0234a3 Thanks @OliverSpeir! - Updates astro add cloudflare to use the latest valid compatibility_date in the wrangler config, if available
#15432 e2ad69e Thanks @OliverSpeir! - Removes unnecessary warning about sharp from being printed at start of dev server and build
#15588 425ea16 Thanks @rururux! - Fixes an issue where esbuild would throw a "Top-level return cannot be used inside an ECMAScript module" error during dependency scanning in certain environments.
#15450 50c9129 Thanks @florian-lefebvre! - Fixes a case where build.serverEntry would not be respected when using the new Adapter API
#15030 b5aa52b Thanks @ematipico! - Fixed an issue where the feature experimental.chromeDevtoolsWorkspace wasn't supported by the new version of the adapter.
#15648 802426b Thanks @rururux! - Restore and fix <Code /> component functionality on Cloudflare Workers.
#15478 ee519e5 Thanks @matthewp! - Fixes fully static sites to not output server-side worker code. When all routes are prerendered, the _worker.js directory is now removed from the build output.
#15636 5ecd04c Thanks @florian-lefebvre! - Adds an error when running on Stackblitz, since workerd doesn't support it
#15269 6f82aae Thanks @ematipico! - Fixes a regression where build.serverEntry stopped working as expected.
#15798 05771cf Thanks @rururux! - Fixes a regression where using the adapter would throw an error when using an integration that uses JSX.
#15053 674b63f Thanks @matthewp! - Excludes astro:* and virtual:astro:* from client optimizeDeps in core. Needed for prefetch users since virtual modules are now in the dependency graph.
#15495 5b99e90 Thanks @leekeh! - Refactors to use middlewareMode adapter feature (set to classic)
Updated dependencies [4ebc1e3, 4e7f3e8, a164c77, cf6ea6b, a18d727, 240c317, 745e632]:
- @astrojs/internal-helpers@0.8.0
- @astrojs/underscore-redirects@1.0.0

`v12.6.13`

Compare Source

Patch Changes

Updated dependencies [c2cd371]:
- @astrojs/internal-helpers@0.7.6
- @astrojs/underscore-redirects@1.0.0

`v12.6.12`

Compare Source

Patch Changes

#14777 9720b70 Thanks @iclectic! - Updates assets handling to use @astrojs/internal-helpers
Updated dependencies []:
- @astrojs/underscore-redirects@1.0.0

`v12.6.11`

Compare Source

Patch Changes

Updated dependencies [9e9c528, 0f75f6b]:
- @astrojs/internal-helpers@0.7.5
- @astrojs/underscore-redirects@1.0.0

`v12.6.10`

Compare Source

Patch Changes

b8ca69b Thanks @ascorbic! - Refactor remote path detection
Updated dependencies [b8ca69b]:
- @astrojs/internal-helpers@0.7.4
- @astrojs/underscore-redirects@1.0.0

`v12.6.9`

Compare Source

Patch Changes

Updated dependencies [1e2499e]:
- @astrojs/internal-helpers@0.7.3
- @astrojs/underscore-redirects@1.0.0

`v12.6.8`

Compare Source

Patch Changes

#14326 c24a8f4 Thanks @jsparkdev! - Updates vite version to fix CVE
Updated dependencies []:
- @astrojs/underscore-redirects@1.0.0

`v12.6.7`

Compare Source

Patch Changes

#14281 dfd88de Thanks @ascorbic! - Fixes a regression that broke sites that used the compile image service without nodejs_compat set
Updated dependencies []:
- @astrojs/underscore-redirects@1.0.0

`v12.6.6`

Compare Source

Patch Changes

9ecf359 Thanks @alexanderniebuhr! - Improves the image proxy endpoint when using the default compile option to adhere to user configuration regarding the allowed remote domains
Updated dependencies []:
- @astrojs/underscore-redirects@1.0.0

`v12.6.5`

Compare Source

Patch Changes

#14259 02366e9 Thanks @ascorbic! - Removes warning when using the adapter with a static build.

The Cloudflare adapter now has several uses outside of on-demand rendered pages, so this warning is misleading. Similar warnings have already been removed from other adapters.
#14234 15b55f3 Thanks @yanthomasdev! - Fixes an issue that could cause duplicate exports when configuring workerEntrypoint.namedExports
#14240 77b18fb Thanks @delucis! - Increases the minimum supported version of Astro to 5.7.0
Updated dependencies []:
- @astrojs/underscore-redirects@1.0.0

`v12.6.4`

Compare Source

Patch Changes

Updated dependencies [4d16de7]:
- @astrojs/internal-helpers@0.7.2
- @astrojs/underscore-redirects@1.0.0

`v12.6.3`

Compare Source

Patch Changes

#14066 7abde79 Thanks @alexanderniebuhr! - Refactors the internal solution which powers Astro Sessions when running local development with ˋastro devˋ.

The adapter now utilizes Cloudflare's local support for Cloudflare KV. This internal change is a drop-in replacement and does not require any change to your projectct code.

However, you now have the ability to connect to the remote Cloudflare KV Namespace if desired and use production data during local development.
Updated dependencies []:
- @astrojs/underscore-redirects@1.0.0

`v12.6.2`

Compare Source

Patch Changes

#13894 b36e72f Thanks @florian-lefebvre! - Removes special handling of the ASTRO_STUDIO_APP_TOKEN environment variable
Updated dependencies [0567fb7]:
- @astrojs/internal-helpers@0.7.1
- @astrojs/underscore-redirects@1.0.0

`v12.6.1`

Compare Source

Patch Changes

#14777 9720b70 Thanks @iclectic! - Updates assets handling to use @astrojs/internal-helpers
Updated dependencies []:
- @astrojs/underscore-redirects@1.0.0

`v12.6.0`

Compare Source

Minor Changes

#13837 7cef86f Thanks @alexanderniebuhr! - Adds new configuration options to allow you to set a custom workerEntryPoint for Cloudflare Workers. This is useful if you want to use features that require handlers (e.g. Durable Objects, Cloudflare Queues, Scheduled Invocations) not supported by the basic generic entry file.

This feature is not supported when running the Astro dev server. However, you can run astro build followed by either wrangler deploy (to deploy it) or wrangler dev to preview it.

The following example configures a custom entry file that registers a Durable Object and a queue handler:

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

export default defineConfig({
  adapter: cloudflare({
    workerEntryPoint: {
      path: 'src/worker.ts',
      namedExports: ['MyDurableObject'],
    },
  }),
});

// src/worker.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,
  };
}

Patch Changes

#13963 c667c55 Thanks @florian-lefebvre! - Fixes a case where the platform proxy would not be disposed when the dev process ended
Updated dependencies []:
- @astrojs/underscore-redirects@1.0.0

`v12.5.5`

Compare Source

Patch Changes

#13930 acb9b30 Thanks @alexanderniebuhr! - Fixes an issue where setting values for Astro.response resulted in a Cloudflare runtime exception.
Updated dependencies [de82ef2, de82ef2, de82ef2]:
- @astrojs/underscore-redirects@1.0.0

`v12.5.4`

Compare Source

Patch Changes

#13817 b7258f1 Thanks @yanthomasdev! - Clarifies and reduces a few logs when starting the dev server with @astrojs/cloudflare.

Warnings about sharp support will now be suppressed when you have explicitly set an imageService option.
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.1

`v12.5.3`

Compare Source

Patch Changes

#13792 7910fea Thanks @alexeyzimarev! - Unify imported images detection across adapters
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.1

`v12.5.2`

Compare Source

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.1

`v12.5.1`

Compare Source

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code
Updated dependencies [5dd2d3f]:
- @astrojs/underscore-redirects@0.6.1

`v12.5.0`

Compare Source

Minor Changes

#13527 2fd6a6b Thanks @ascorbic! - The experimental session API introduced in Astro 5.1 is now stable and ready for production use.

Sessions are used to store user state between requests for on-demand rendered pages. You can use them to store user data, such as authentication tokens, shopping cart contents, or any other data that needs to persist across requests:

`v12.4.1`

Compare Source

Patch Changes

#13596 3752519 Thanks @jsparkdev! - update vite to latest version to fix CVE
#13547 360cb91 Thanks @jsparkdev! - Updates vite to the latest version
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.0

`v12.4.0`

Compare Source

Minor Changes

#13514 a9aafec Thanks @ascorbic! - Automatically configures Cloudflare KV storage when experimental sessions are enabled

If the experimental.session flag is enabled when using the Cloudflare adapter, Astro will automatically configure the session storage using the Cloudflare KV driver. You can still manually configure the ses

Configuration

📅 Schedule: Branch creation - Between 07:00 AM and 07:59 AM, only on Monday and Thursday ( * 7 * * 1,4 ) in timezone Asia/Tokyo, 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.

coderabbitai · 2025-03-02T22:02:18Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai plan to trigger planning for file edits and PR creation.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json