[pull] main from withastro:main

.changeset/beige-doodles-bow.md

@@ -0,0 +1,5 @@
+---
+'astro': patch
+---
+
+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.

.changeset/common-pears-drive.md

@@ -0,0 +1,16 @@
+---
+'@astrojs/cloudflare': major
+'@astrojs/alpinejs': major
+'@astrojs/markdoc': major
+'@astrojs/netlify': major
+'@astrojs/preact': major
+'@astrojs/svelte': major
+'@astrojs/vercel': major
+'@astrojs/react': major
+'@astrojs/solid-js': major
+'@astrojs/mdx': major
+'@astrojs/vue': major
+'astro': major
+---
+
+Upgrade to Vite v8

.changeset/config.json

@@ -4,7 +4,7 @@
   "commit": false,
   "linked": [],
   "access": "public",
-  "baseBranch": "origin/main",
+  "baseBranch": "origin/next",
   "updateInternalDependencies": "patch",
   "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
     "onlyUpdatePeerDependentsWhenOutOfRange": true

.changeset/cozy-knives-buy.md

@@ -0,0 +1,5 @@
+---
+'astro': patch
+---
+
+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`.

.changeset/experimental-background-dev.md

@@ -0,0 +1,24 @@
+---
+'astro': major
+---
+
+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`.

.changeset/expose-get-fetch-state.md

@@ -0,0 +1,24 @@
+---
+'astro': minor
+---
+
+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`.
+
+```ts
+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;
+```

.changeset/fix-dev-port-vite-restart.md

@@ -0,0 +1,5 @@
+---
+'astro': patch
+---
+
+Fixes `--port` flag being ignored after a Vite-triggered server restart (e.g. when a `.env` file changes)

.changeset/font-data-subset-field.md

@@ -0,0 +1,5 @@
+---
+'astro': minor
+---
+
+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.

.changeset/goofy-tigers-like.md

@@ -0,0 +1,5 @@
+---
+'astro': patch
+---
+
+Removes the warning that Astro does not support vite v8, since Astro v7 does support vite v8

.changeset/plenty-meals-wonder.md

@@ -0,0 +1,57 @@
+---
+'astro': minor
+---
+
+The custom logger feature introduced behind a flag in [v6.2.0](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md#620) 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
+
+```js
+import { defineConfig, logHandlers } from 'astro/config';
+
+export default defineConfig({
+  logger: logHandlers.json({
+    pretty: true,
+    level: 'warn',
+  }),
+});
+```
+
+#### Custom logger
+
+```js
+import { defineConfig } from 'astro/config';
+
+export default defineConfig({
+  logger: {
+    entrypoint: '@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:
+
+```diff
+import { defineConfig } from 'astro/config';
+
+export default defineConfig({
+-  experimental: {
+-    logger: {
+-      entrypoint: '@org/custom-logger',
+-    },
+-  },
++  logger: {
++    entrypoint: '@org/custom-logger',
++  },
+});
+```
+
+If you have been waiting for stabilization before using custom loggers, you can now do so.
+
+Please see the [Logger docs](https://docs.astro.build/en/reference/configuration-reference/#logger) for more about this feature.

.changeset/pre.json

@@ -0,0 +1,55 @@
+{
+  "mode": "pre",
+  "tag": "beta",
+  "initialVersions": {
+    "astro": "6.0.8",
+    "@astrojs/prism": "4.0.1",
+    "@astrojs/rss": "4.0.17",
+    "create-astro": "5.0.3",
+    "@astrojs/alpinejs": "0.5.0",
+    "@astrojs/cloudflare": "13.1.3",
+    "@astrojs/markdoc": "1.0.2",
+    "@astrojs/mdx": "5.0.2",
+    "@astrojs/netlify": "7.0.4",
+    "@astrojs/node": "10.0.3",
+    "@astrojs/partytown": "2.1.5",
+    "@astrojs/preact": "5.0.2",
+    "@astrojs/react": "5.0.1",
+    "@astrojs/sitemap": "3.7.1",
+    "@astrojs/solid-js": "6.0.1",
+    "@astrojs/svelte": "8.0.3",
+    "@astrojs/vercel": "10.0.2",
+    "@astrojs/vue": "6.0.1",
+    "@astrojs/internal-helpers": "0.8.0",
+    "@astrojs/check": "0.9.8",
+    "@astrojs/language-server": "2.16.6",
+    "@astrojs/ts-plugin": "1.10.7",
+    "astro-vscode": "2.16.13",
+    "@astrojs/yaml2ts": "0.2.3",
+    "@astrojs/markdown-remark": "7.0.1",
+    "@astrojs/telemetry": "3.3.0",
+    "@astrojs/underscore-redirects": "1.0.2",
+    "@astrojs/upgrade": "0.7.1",
+    "@astrojs/markdown-satteri": "0.2.2"
+  },
+  "changesets": [
+    "beige-doodles-bow",
+    "common-pears-drive",
+    "cozy-knives-buy",
+    "experimental-background-dev",
+    "expose-get-fetch-state",
+    "fix-dev-port-vite-restart",
+    "font-data-subset-field",
+    "goofy-tigers-like",
+    "plenty-meals-wonder",
+    "remove-db-cli-command",
+    "rusty-compilers-only",
+    "seven-pots-begin",
+    "silly-spoons-write",
+    "social-paws-take",
+    "trigger-beta",
+    "two-eels-live",
+    "update-vite-plugin-svelte-v7",
+    "wacky-bugs-act"
+  ]
+}

.changeset/remove-db-cli-command.md

@@ -0,0 +1,13 @@
+---
+'astro': major
+---
+
+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`](https://nodejs.org/api/sqlite.html) 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](https://orm.drizzle.team/)**: 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](https://turso.tech/), [PlanetScale](https://planetscale.com/), [Neon](https://neon.tech/)).

.changeset/rusty-compilers-only.md

@@ -0,0 +1,11 @@
+---
+'astro': major
+---
+
+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.

.changeset/satteri-default-markdown-processor.md

@@ -0,0 +1,23 @@
+---
+'astro': major
+---
+
+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:
+
+```js
+// astro.config.mjs
+import { defineConfig } from 'astro/config';
+import { unified } from '@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.

.changeset/seven-pots-begin.md

@@ -0,0 +1,44 @@
+---
+'astro': major
+---
+
+Enables advanced routing by default.
+
+The advanced routing feature introduced behind a flag in [v6.3.0](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md#630) 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:
+
+```diff
+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:
+
+```diff
+// 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](https://docs.astro.build/en/guides/routing/#advanced-routing) for more about this feature.

.changeset/silly-spoons-write.md

@@ -0,0 +1,5 @@
+---
+'@astrojs/cloudflare': patch
+---
+
+Removes deprecations warnings added in Astro v6 for Cloudflare specific Astro.locals properties.