Add support for Svelte 5 @render syntax

.changeset/afraid-apricots-buy.md

@@ -0,0 +1,20 @@
+---
+'astro': minor
+---
+
+Adapters can now specify the build output type they're intended for using the `adapterFeatures.buildOutput` property. This property can be used to always generate a server output, even if the project doesn't have any server-rendered pages.
+
+```ts
+{
+  'astro:config:done': ({ setAdapter, config }) => {
+    setAdapter({
+      name: 'my-adapter',
+      adapterFeatures: {
+        buildOutput: 'server',
+      },
+    });
+  },
+}
+```
+
+If your adapter specifies `buildOutput: 'static'`, and the user's project contains server-rendered pages, Astro will warn in development and error at build time. Note that a hybrid output, containing both static and server-rendered pages, is considered to be a `server` output, as a server is required to serve the server-rendered pages.

.changeset/blue-boats-relax.md

@@ -0,0 +1,9 @@
+---
+'astro': major
+---
+
+Unflag globalRoutePriority
+
+The previously experimental feature `globalRoutePriority` is now the default in Astro 5.
+
+This was a refactoring of route prioritization in Astro, making it so that injected routes, file-based routes, and redirects are all prioritized using the same logic. This feature has been enabled for all Starlight projects since it was added and should not affect most users.

.changeset/blue-sloths-stare.md

@@ -0,0 +1,14 @@
+---
+'astro': patch
+---
+
+`render()` signature now takes `renderOptions` as 2nd argument
+
+The signature for `app.render()` has changed, and the second argument is now an options object called `renderOptions` with more options for customizing rendering.
+
+The `renderOptions` are:
+
+- `addCookieHeader`: Determines whether Astro will set the `Set-Cookie` header, otherwise the adapter is expected to do so itself.
+- `clientAddress`: The client IP address used to set `Astro.clientAddress`.
+- `locals`: An object of locals that's set to `Astro.locals`.
+- `routeData`: An object specifying the route to use.

.changeset/brave-elephants-fly.md

@@ -0,0 +1,21 @@
+---
+'astro': major
+---
+
+### [changed]: `entryPoint` type inside the hook `astro:build:ssr`
+In Astro v4.x, the `entryPoint` type was `RouteData`.
+
+Astro v5.0 the `entryPoint` type is `IntegrationRouteData`, which contains a subset of the `RouteData` type. The fields `isIndex` and `fallbackRoutes` were removed. 
+
+#### What should I do?
+Update your adapter to change the type of `entryPoint` from `RouteData` to `IntegrationRouteData`.
+
+```diff
+-import type {RouteData} from 'astro';
++import type {IntegrationRouteData} from "astro"
+
+-function useRoute(route: RouteData) {
++function useRoute(route: IntegrationRouteData) {
+
+}
+```

.changeset/breezy-colts-promise.md

@@ -0,0 +1,5 @@
+---
+'@astrojs/markdoc': patch
+---
+
+Uses latest version of `@astrojs/markdown-remark` with updated Shiki APIs

.changeset/chatty-teachers-sit.md

@@ -0,0 +1,5 @@
+---
+"astro": major
+---
+
+The lowest version of Node supported by Astro is now Node v18.17.1 and higher.

.changeset/chilly-terms-know.md

@@ -0,0 +1,15 @@
+---
+'astro': major
+---
+
+Updates how the `build.client` and `build.server` option values get resolved to match existing documentation. With this fix, the option values will now correctly resolve relative to the `outDir` option. So if `outDir` is set to `./dist/nested/`, then by default:
+
+- `build.client` will resolve to `<root>/dist/nested/client/`
+- `build.server` will resolve to `<root>/dist/nested/server/`
+
+Previously the values were incorrectly resolved:
+
+- `build.client` was resolved to `<root>/dist/nested/dist/client/`
+- `build.server` was resolved to `<root>/dist/nested/dist/server/`
+
+If you were relying on the previous build paths, make sure that your project code is updated to the new build paths.

.changeset/clean-camels-drive.md

@@ -0,0 +1,7 @@
+---
+'astro': major
+---
+
+Adds a default exclude and include value to the tsconfig presets. `{projectDir}/dist` is now excluded by default, and `{projectDir}/.astro/types.d.ts` and `{projectDir}/**/*` are included by default.
+
+Both of these options can be overridden by setting your own values to the corresponding settings in your `tsconfig.json` file.

.changeset/clean-donuts-walk.md

@@ -0,0 +1,13 @@
+---
+'@astrojs/markdown-remark': major
+'astro': major
+---
+
+Cleans up Astro-specfic metadata attached to `vfile.data` in Remark and Rehype plugins. Previously, the metadata was attached in different locations with inconsistent names. The metadata is now renamed as below:
+
+- `vfile.data.__astroHeadings` -> `vfile.data.astro.headings`
+- `vfile.data.imagePaths` -> `vfile.data.astro.imagePaths`
+
+The types of `imagePaths` has also been updated from `Set<string>` to `string[]`. The `vfile.data.astro.frontmatter` metadata is left unchanged.
+
+While we don't consider these APIs public, they can be accessed by Remark and Rehype plugins that want to re-use Astro's metadata. If you are using these APIs, make sure to access them in the new locations.

.changeset/cold-bananas-hear.md

@@ -0,0 +1,5 @@
+---
+'astro': patch
+---
+
+Correctly parse values returned from inline loader

.changeset/config.json

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

.changeset/cool-mangos-shop.md

@@ -0,0 +1,25 @@
+---
+'astro': major
+---
+
+The `locals` object can no longer be overridden
+
+Middleware, API endpoints, and pages can no longer override the `locals` object in its entirety. You can still append values onto the object, but you can not replace the entire object and delete its existing values.
+
+If you were previously overwriting like so:
+
+```js
+ctx.locals = {
+  one: 1,
+  two: 2
+}
+```
+
+This can be changed to an assignment on the existing object instead:
+
+```js
+Object.assign(ctx.locals, {
+  one: 1,
+  two: 2
+})
+```

.changeset/cuddly-shoes-press.md

@@ -0,0 +1,5 @@
+---
+'astro': patch
+---
+
+Fixes an issue where the refresh context data was not passed correctly to content layer loaders

.changeset/curvy-walls-kneel.md

@@ -0,0 +1,45 @@
+---
+'astro': patch
+---
+
+Adds a new function `refreshContent` to the `astro:server:setup` hook that allows integrations to refresh the content layer. This can be used, for example, to register a webhook endpoint during dev, or to open a socket to a CMS to listen for changes.
+
+By default, `refreshContent` will refresh all collections. You can optionally pass a `loaders` property, which is an array of loader names. If provided, only collections that use those loaders will be refreshed. For example, A CMS integration could use this property to only refresh its own collections.
+
+You can also pass a `context` object to the loaders. This can be used to pass arbitrary data, such as the webhook body, or an event from the websocket.
+
+```ts
+ {
+    name: 'my-integration',
+    hooks: {
+        'astro:server:setup': async ({ server, refreshContent }) => {
+            server.middlewares.use('/_refresh', async (req, res) => {
+                if(req.method !== 'POST') {
+                  res.statusCode = 405
+                  res.end('Method Not Allowed');
+                  return
+                }
+                let body = '';
+                req.on('data', chunk => {
+                    body += chunk.toString();
+                });
+                req.on('end', async () => {
+                    try {
+                        const webhookBody = JSON.parse(body);
+                        await refreshContent({
+                          context: { webhookBody },
+                          loaders: ['my-loader']
+                        });
+                        res.writeHead(200, { 'Content-Type': 'application/json' });
+                        res.end(JSON.stringify({ message: 'Content refreshed successfully' }));
+                    } catch (error) {
+                        res.writeHead(500, { 'Content-Type': 'application/json' });
+                        res.end(JSON.stringify({ error: 'Failed to refresh content: ' + error.message }));
+                    }
+                });
+            });
+        }
+    }
+}
+```
+

.changeset/dirty-cooks-explode.md

@@ -0,0 +1,9 @@
+---
+'@astrojs/mdx': major
+---
+
+Handles the breaking change in Astro where content pages (including `.mdx` pages located within `src/pages/`) no longer respond with `charset=utf-8` in the `Content-Type` header.
+
+For MDX pages without layouts, `@astrojs/mdx` will automatically add the `<meta charset="utf-8">` tag to the page by default. This reduces the boilerplate needed to write with non-ASCII characters. If your MDX pages have a layout, the layout component should include the `<meta charset="utf-8">` tag.
+
+If you require `charset=utf-8` to render your page correctly, make sure that your layout components have the `<meta charset="utf-8">` tag added.

.changeset/dry-lamps-smile.md

@@ -0,0 +1,5 @@
+---
+'astro': patch
+---
+
+Update error link to on-demand rendering guide

.changeset/dry-worms-knock.md

@@ -0,0 +1,18 @@
+---
+'astro': major
+---
+
+The `image.endpoint` config now allow customizing the route of the image endpoint in addition to the entrypoint. This can be useful in niche situations where the default route `/_image` conflicts with an existing route or your local server setup.
+
+```js
+import { defineConfig } from "astro/config";
+
+defineConfig({
+  image: {
+    endpoint: {
+      route: "/image",
+      entrypoint: "./src/image_endpoint.ts"
+    }
+  },
+})
+```

.changeset/dull-moles-talk.md

@@ -0,0 +1,5 @@
+---
+'astro': patch
+---
+
+Prevents Vite emitting an error when restarting itself

.changeset/eight-days-sort.md

@@ -0,0 +1,14 @@
+---
+'astro': major
+'@astrojs/mdx': major
+'@astrojs/markdown-remark': major
+'@astrojs/db': minor
+'@astrojs/web-vitals': major
+'@astrojs/underscore-redirects': minor
+---
+
+Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.
+
+Starting from this release, no breaking changes will be introduced unless absolutely necessary.
+
+To learn how to upgrade, check out the [Astro v5.0 upgrade guide in our beta docs site](https://5-0-0-beta.docs.astro.build/en/guides/upgrade-to/v5/).

.changeset/eighty-bags-cross.md

@@ -0,0 +1,5 @@
+---
+'astro': patch
+---
+
+Exports the `RenderResult` type

.changeset/eighty-boxes-applaud.md

@@ -0,0 +1,48 @@
+---
+'astro': major
+---
+
+The `astro:env` feature introduced behind a flag in [v4.10.0](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md#x4100) is no longer experimental and is available for general use. If you have been waiting for stabilization before using `astro:env`, you can now do so.
+
+This feature lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client.
+
+To configure a schema, add the `env` option to your Astro config and define your client and server variables. If you were previously using this feature, please remove the experimental flag from your Astro config and move your entire `env` configuration unchanged to a top-level option.
+
+```js
+import { defineConfig, envField } from 'astro/config'
+
+export default defineConfig({
+  env: {
+    schema: {
+      API_URL: envField.string({ context: "client", access: "public", optional: true }),
+      PORT: envField.number({ context: "server", access: "public", default: 4321 }),
+      API_SECRET: envField.string({ context: "server", access: "secret" }),
+    }
+  }
+})
+```
+
+You can import and use your defined variables from the appropriate `/client` or `/server` module:
+
+```astro
+---
+import { API_URL } from "astro:env/client"
+import { API_SECRET_TOKEN } from "astro:env/server"
+
+const data = await fetch(`${API_URL}/users`, {
+  method: "GET",
+  headers: {
+    "Content-Type": "application/json",
+    "Authorization": `Bearer ${API_SECRET_TOKEN}`
+  },
+})
+---
+
+<script>
+import { API_URL } from "astro:env/client"
+
+fetch(`${API_URL}/ping`)
+</script>
+```
+
+Please see our [guide to using environment variables](https://docs.astro.build/en/guides/environment-variables/#astroenv) for more about this feature.

.changeset/eighty-donkeys-fly.md

@@ -0,0 +1,14 @@
+---
+'astro': minor
+---
+
+The following renderer fields and integration fields now accept `URL` as a type:
+
+**Renderers**:
+- `AstroRenderer.clientEntrpoint`
+- `AstroRenderer.serverEntrypoint`
+
+**Integrations**:
+- `InjectedRoute.entrypoint`
+- `AstroIntegrationMiddleware.entrypoint`
+- `DevToolbarAppEntry.entrypoint`

.changeset/eighty-ligers-punch.md

@@ -0,0 +1,5 @@
+---
+'@astrojs/svelte': patch
+---
+
+Fixes an Reference Error that occurred during client transitions

.changeset/five-jars-hear.md

@@ -0,0 +1,11 @@
+---
+'astro': patch
+---
+
+Updates Astro's default `<script>` rendering strategy and removes the `experimental.directRenderScript` option as this is now the default behavior: scripts are always rendered directly. This new strategy prevents scripts from being executed in pages where they are not used. 
+
+Scripts will directly render as declared in Astro files (including existing features like TypeScript, importing `node_modules`, and deduplicating scripts). You can also now conditionally render scripts in your Astro file.
+
+However, this means scripts are no longer hoisted to the `<head>`, multiple scripts on a page are no longer bundled together, and the `<script>` tag may interfere with the CSS styling.
+
+As this is a potentially breaking change to your script behavior, please review your `<script>` tags and ensure that they behave as expected.

.changeset/fluffy-jars-live.md

@@ -0,0 +1,7 @@
+---
+'astro': major
+---
+
+Removes the `assets` property on `supportedAstroFeatures` for adapters, as it did not reflect reality properly in many cases.
+
+Now, relating to assets, only a single `sharpImageService` property is available, determining if the adapter is compatible with the built-in sharp image service.

.changeset/forty-trains-notice.md

@@ -0,0 +1,5 @@
+---
+'astro': minor
+---
+
+Improves `defineConfig` type safety. TypeScript will now error if a group of related configuration options do not have consistent types. For example, you will now see an error if your language set for `i18n.defaultLocale` is not one of the supported locales specified in `i18n.locales`.

.changeset/fresh-pandas-drive.md

@@ -0,0 +1,5 @@
+---
+'astro': patch
+---
+
+Fixes a type and an example in documenting the `security.checkOrigin` property of Astro config.

.changeset/funny-wolves-dream.md

@@ -0,0 +1,5 @@
+---
+'astro': patch
+---
+
+Allows "slug" as a field in content layer data