AstroEco is Releasing…

Display your GitHub releases using astro-loader-github-releases

astro

withastro/astro

v5.7.12 May 8

Patch Changes

#13752 a079c21 Thanks @florian-lefebvre! - Improves handling of font URLs not ending with a file extension when using the experimental fonts API
#13750 7d3127d Thanks @martrapp! - Allows the ClientRouter to open new tabs or windows when submitting forms by clicking while holding the Cmd, Ctrl, or Shift key.
#13765 d874fe0 Thanks @florian-lefebvre! - Fixes a case where font sources with relative protocol URLs would fail when using the experimental fonts API
#13640 5e582e7 Thanks @florian-lefebvre! - Allows inferring weight and style when using the local provider of the experimental fonts API

If you want Astro to infer those properties directly from your local font files, leave them undefined:
```
{
  // No weight specified: infer
  style: 'normal'; // Do not infer
}
```

@astrojs/starlight

withastro/starlight

v0.34.3 May 8

Patch Changes

#3058 274cc06 Thanks @techfg! - Fixes display of focus indicator around site title
#3181 449c822 Thanks @HiDeoo! - Fixes an issue where all headings in Markdown and MDX content were rendered with a clickable anchor link, even in non-Starlight pages.
#3168 ca693fe Thanks @jsparkdev! - Updates Korean langage support with improvements and missing translations

astro

withastro/astro

v5.7.11 May 6

Patch Changes

#13734 30aec73 Thanks @ascorbic! - Loosen content layer schema types
#13751 5816b8a Thanks @florian-lefebvre! - Updates unifont to support subsets when using the google provider with the experimental fonts API
#13756 d4547ba Thanks @florian-lefebvre! - Adds a terminal warning when a remote provider returns no data for a family when using the experimental fonts API
#13742 f599463 Thanks @florian-lefebvre! - Fixes optimized fallback css generation to properly add a src when using the experimental fonts API
#13740 6935540 Thanks @vixalien! - Fix cookies set after middleware did a rewrite with next(url) not being applied
#13759 4a56d0a Thanks @jp-knj! - Improved the error handling of certain error cases.

@astrojs/starlight

withastro/starlight

v0.34.2 May 1

Patch Changes

#3153 ea31f46 Thanks @SuperKXT! - Fixes hover styles for highlighted directory in FileTree component.
#2905 b5232bc Thanks @HiDeoo! - Fixes a potential issue for projects with dynamic routes added by an user, an Astro integration, or a Starlight plugin where some styles could end up being missing.
#3165 80a7871 Thanks @KianNH! - Increases maxBuffer for an internal spawnSync() call to support larger Git commit histories when using Starlight's lastUpdated feature.
#3158 d1f3c8b Thanks @heisenberg0924! - Adds Hungarian language support

astro-antfustyle-theme

lin-stephanie/astro-antfustyle-theme

v2.0.0 Apr 30

🚨 Breaking Changes

Upgrade from Astro 4.16 to Astro 5.7 and more - by @lin-stephanie in #25 (089b9)

🏡 Chore

Update docs for Astro 5.7 upgrade - by @lin-stephanie (ef781)

View changes on GitHub

astro

withastro/astro

v5.7.10 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/vue

withastro/astro

v5.0.13 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/studio

withastro/astro

v0.1.9 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/svelte

withastro/astro

v7.0.13 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/netlify

withastro/astro

v6.3.2 Apr 30

Patch Changes

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

@astrojs/solid-js

withastro/astro

v5.0.10 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/react

withastro/astro

v4.2.7 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/preact

withastro/astro

v4.0.11 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/mdx

withastro/astro

v4.2.6 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/cloudflare

withastro/astro

v2.5.2 Apr 30

Patch Changes

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

@astrojs/db

withastro/astro

v0.14.13 Apr 30

Patch Changes

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

@astrojs/markdoc

withastro/astro

v0.14.2 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

@astrojs/alpinejs

withastro/astro

v0.4.8 Apr 30

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

astro

withastro/astro

v5.7.9 Apr 29

Patch Changes

#13711 2103991 Thanks @ascorbic! - Fixes height for responsive images

@astrojs/vue

withastro/astro

v5.0.12 Apr 29

Patch Changes

#13720 e1cd1ae Thanks @florian-lefebvre! - Fixes SSR renderer type

@astrojs/svelte

withastro/astro

v7.0.12 Apr 29

Patch Changes

#13720 e1cd1ae Thanks @florian-lefebvre! - Fixes SSR renderer type

@astrojs/react

withastro/astro

v4.2.6 Apr 29

Patch Changes

#13720 e1cd1ae Thanks @florian-lefebvre! - Fixes SSR renderer type

astro

withastro/astro

v5.7.8 Apr 28

Patch Changes

#13715 b32dffa Thanks @florian-lefebvre! - Updates unifont to fix a case where a unicodeRange related error would be thrown when using the experimental fonts API

create-astro

withastro/astro

v4.11.4 Apr 28

Patch Changes

#13703 659904b Thanks @ascorbic! - Fixes an issue when installing dependencies with pnpm.

astro-loader-bluesky-posts

lin-stephanie/astro-loaders

v1.2.2 Apr 27

Patch Changes (`aec3423`)

Update the entry Zod schema
Resolve <Content /> becomes non-functional when fetchThread: true is set

@astrojs/starlight

withastro/starlight

v0.34.1 Apr 24

Patch Changes

#3140 f6eb1d5 Thanks @HiDeoo! - Fixes a text selection issue for heading with a clickable anchor link when using double or triple click to select text.
#3148 dc8b6d5 Thanks @HiDeoo! - Fixes a regression of the Starlight icon color when using the credits configuration option.

@astrojs/upgrade

withastro/astro

v0.5.2 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/underscore-redirects

withastro/astro

v0.6.1 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/telemetry

withastro/astro

v3.2.1 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/vercel

withastro/astro

v8.1.4 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/studio

withastro/astro

v0.1.8 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/web-vitals

withastro/astro

v3.0.2 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/vue

withastro/astro

v5.0.11 Apr 23

Patch Changes

#13663 a19a185 Thanks @florian-lefebvre! - Improves type-safety of renderers

@astrojs/svelte

withastro/astro

v7.0.11 Apr 23

Patch Changes

#13663 a19a185 Thanks @florian-lefebvre! - Improves type-safety of renderers

@astrojs/solid-js

withastro/astro

v5.0.9 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/sitemap

withastro/astro

v3.3.1 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/node

withastro/astro

v9.2.1 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/react

withastro/astro

v4.2.5 Apr 23

Patch Changes

#13663 a19a185 Thanks @florian-lefebvre! - Improves type-safety of renderers

@astrojs/netlify

withastro/astro

v6.3.1 Apr 23

Patch Changes

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

@astrojs/preact

withastro/astro

v4.0.10 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

create-astro

withastro/astro

v4.11.3 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/cloudflare

withastro/astro

v2.5.1 Apr 23

Patch Changes

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

@astrojs/mdx

withastro/astro

v4.2.5 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/markdoc

withastro/astro

v0.14.1 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/alpinejs

withastro/astro

v0.4.7 Apr 23

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

@astrojs/db

withastro/astro

v0.14.12 Apr 23

Patch Changes

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

@astrojs/starlight-tailwind

withastro/starlight

v4.0.1 Apr 17

Patch Changes

#3132 5959919 Thanks @HiDeoo! - Fixes an issue where all border styles were not reset by the Starlight’s Tailwind compatibility package like in Tailwind base styles.

create-astro

withastro/astro

v4.11.2 Apr 17

Patch Changes

#13636 a9fd03f Thanks @sarah11918! - Updates the wording for choosing the "minimal" starter template options

@astrojs/starlight-tailwind

withastro/starlight

v4.0.0 Apr 16

Major Changes

#2322 f14eb0c Thanks @HiDeoo! - ⚠️ BREAKING CHANGE: The minimum supported version of Starlight is now 0.34.0

Please use the @astrojs/upgrade command to upgrade your project:
```
npx @astrojs/upgrade
```

#2322 f14eb0c Thanks @HiDeoo! - Adds support for Tailwind v4, drops support for Tailwind v3.

⚠️ BREAKING CHANGE: Tailwind v3 is no longer supported. Tailwind v4 support in Astro is now provided using a Vite plugin and the Astro Tailwind integration is no longer required.

Remove the Astro Tailwind integration. The Astro Tailwind integration is no longer required with Tailwind v4.

 // astro.config.mjs
 import { defineConfig } from "astro/config";
 import starlight from "@astrojs/starlight";
-import tailwind from "@astrojs/tailwind";

 export default defineConfig({
   integrations: [
     starlight({
       title: "Docs with Tailwind",
       customCss: ["./src/tailwind.css"],
     }),
-    tailwind({ applyBaseStyles: false }),
   ],
 });

Install Tailwind v4. Install the latest version of the tailwindcss and @tailwindcss/vite packages.

Use the astro add tailwind command to install and configure both packages:
```
npx astro add tailwind
```

Update Tailwind base styles. Tailwind CSS base styles needs to be updated for Tailwind v4 and also to use Starlight Tailwind CSS.

/* src/tailwind.css */
-@tailwind base;
-@tailwind components;
-@tailwind utilities;
+@layer base, starlight, theme, components, utilities;
+
+@import '@astrojs/starlight-tailwind';
+@import 'tailwindcss/theme.css' layer(theme);
+@import 'tailwindcss/utilities.css' layer(utilities);
+
+@theme {
+	/*
+	Configure your Tailwind theme that will be used by Starlight.
+	https://starlight.astro.build/guides/css-and-tailwind/#styling-starlight-with-tailwind
+	*/
+}
+
+/*
+Add additional Tailwind styles to this file:
+https://tailwindcss.com/docs/adding-custom-styles#using-custom-css
+*/

Update Tailwind customizations. If you previously customized your Tailwind theme configuration in the tailwind.config.mjs file, such customizations are now defined through CSS using the @theme block in your Tailwind base styles.

Locate existing customizations in your tailwind.config.mjs file. The following example defines customizations for the accent colors, gray scale, and font families used by Starlight:

// tailwind.config.mjs
import starlightPlugin from '@astrojs/starlight-tailwind';
import colors from 'tailwindcss/colors';

/** @type {import('tailwindcss').Config} */
export default {
  content: ['./src/**/*.{astro,html,js,jsx,md,mdx,svelte,ts,tsx,vue}'],
  theme: {
    extend: {
      colors: {
        // Custom accent colors.
        accent: colors.fuchsia,
        // Custom gray scale.
        gray: colors.slate,
      },
      fontFamily: {
        // Custom text font.
        sans: ['"Atkinson Hyperlegible"'],
        // Custom code font.
        mono: ['"IBM Plex Mono"'],
      },
    },
  },
  plugins: [starlightPlugin()],
};

The above customizations can be migrated to the new @theme block in the file containing your Tailwind base styles as follows:

/* src/tailwind.css */
@layer base, starlight, theme, components, utilities;

@import '@astrojs/starlight-tailwind';
@import 'tailwindcss/theme.css' layer(theme);
@import 'tailwindcss/utilities.css' layer(utilities);

@theme {
  /* Custom accent colors. */
  --color-accent-50: var(--color-fuchsia-50);
  --color-accent-100: var(--color-fuchsia-100);
  --color-accent-200: var(--color-fuchsia-200);
  --color-accent-300: var(--color-fuchsia-300);
  --color-accent-400: var(--color-fuchsia-400);
  --color-accent-500: var(--color-fuchsia-500);
  --color-accent-600: var(--color-fuchsia-600);
  --color-accent-700: var(--color-fuchsia-700);
  --color-accent-800: var(--color-fuchsia-800);
  --color-accent-900: var(--color-fuchsia-900);
  --color-accent-950: var(--color-fuchsia-950);
  /* Custom gray scale. */
  --color-gray-50: var(--color-slate-50);
  --color-gray-100: var(--color-slate-100);
  --color-gray-200: var(--color-slate-200);
  --color-gray-300: var(--color-slate-300);
  --color-gray-400: var(--color-slate-400);
  --color-gray-500: var(--color-slate-500);
  --color-gray-600: var(--color-slate-600);
  --color-gray-700: var(--color-slate-700);
  --color-gray-800: var(--color-slate-800);
  --color-gray-900: var(--color-slate-900);
  --color-gray-950: var(--color-slate-950);
  /* Custom text font. */
  --font-sans: 'Atkinson Hyperlegible';
  /* Custom code font. */
  --font-mono: 'IBM Plex Mono';
}

We recommend checking your site’s appearance when upgrading to make sure there are no style regressions caused by this change.

For full details about upgrading from Tailwind v3 to v4, see the official upgrade guide.

@astrojs/starlight

withastro/starlight

v0.34.0 Apr 16

Minor Changes

#2322 f14eb0c Thanks @HiDeoo! - Groups all of Starlight's CSS declarations into a single starlight cascade layer.

This change allows for easier customization of Starlight's CSS as any custom unlayered CSS will override the default styles. If you are using cascade layers in your custom CSS, you can use the @layer CSS at-rule to define the order of precedence for different layers including the ones used by Starlight.

We recommend checking your site’s appearance when upgrading to make sure there are no style regressions caused by this change.
#3122 3a087d8 Thanks @delucis! - Removes default attrs and content values from head entries parsed using Starlight’s schema.

Previously when adding head metadata via frontmatter or user config, Starlight would automatically add values for attrs and content if not provided. Now, these properties are left undefined.

This makes it simpler to add tags in route middleware for example as you no longer need to provide empty values for attrs and content:
```
head.push({
  tag: 'style',
  content: 'div { color: red }'
- attrs: {},
});
head.push({
  tag: 'link',
- content: ''
  attrs: { rel: 'me', href: 'https://example.com' },
});
```
This is mostly an internal API but if you are overriding Starlight’s Head component or processing head entries in some way, you may wish to double check your handling of Astro.locals.starlightRoute.head is compatible with attrs and content potentially being undefined.
#3033 8c19678 Thanks @delucis! - Adds support for generating clickable anchor links for headings.

By default, Starlight now renders an anchor link beside headings in Markdown and MDX content. A new <AnchorHeading> component is available to achieve the same thing in custom pages built using <StarlightPage>.

If you want to disable this new Markdown processing set the markdown.headingLinks option in your Starlight config to false:
```
starlight({
  title: 'My docs',
  markdown: {
    headingLinks: false,
  },
}),
```
⚠️ BREAKING CHANGE: The minimum supported version of Astro is now v5.5.0.

Please update Starlight and Astro together:
```
npx @astrojs/upgrade
```

#2322 f14eb0c Thanks @HiDeoo! - Removes Shiki css-variables theme fallback.

⚠️ BREAKING CHANGE:

Previously, Starlight used to automatically provide a fallback theme for Shiki, the default syntax highlighter built into Astro if the configured Shiki theme was not github-dark.

This fallback was only relevant when the default Starlight code block renderer, Expressive Code, was disabled and Shiki was used. Starlight no longer provides this fallback.

If you were relying on this behavior, you now manually need to update your Astro configuration to use the Shiki css-variables theme to match the previous behavior.

import { defineConfig } from 'astro/config';

export default defineConfig({
+ markdown: {
+   shikiConfig: {
+     theme: 'css-variables',
+   },
+ },
});

Additionally, you can use custom CSS to control the appearance of the code blocks. Here are the previously used CSS variables for the fallback theme:

:root {
  --astro-code-foreground: var(--sl-color-white);
  --astro-code-background: var(--sl-color-gray-6);
  --astro-code-token-constant: var(--sl-color-blue-high);
  --astro-code-token-string: var(--sl-color-green-high);
  --astro-code-token-comment: var(--sl-color-gray-2);
  --astro-code-token-keyword: var(--sl-color-purple-high);
  --astro-code-token-parameter: var(--sl-color-red-high);
  --astro-code-token-function: var(--sl-color-red-high);
  --astro-code-token-string-expression: var(--sl-color-green-high);
  --astro-code-token-punctuation: var(--sl-color-gray-2);
  --astro-code-token-link: var(--sl-color-blue-high);
}

Patch Changes

#3118 77a1104 Thanks @delucis! - Fixes passing imported SVGs to the frontmatter prop of the <StarlightPage> component in Astro ≥5.7.0

@astrojs/starlight-markdoc

withastro/starlight

v0.4.0 Apr 16

Minor Changes

#3033 8c19678 Thanks @delucis! - Adds support for generating clickable anchor links for headings.

By default, the Starlight Markdoc preset now includes a default heading node, which renders an anchor link beside headings in your Markdoc content.

If you want to disable this new feature, pass headingLinks: false in your Markdoc config:
```
export default defineMarkdocConfig({
  // Disable the default heading anchor link support
  extends: [starlightMarkdoc({ headingLinks: false })],
});
```
⚠️ BREAKING CHANGE: The minimum supported peer version of Starlight is now v0.34.0.

Please update Starlight and the Starlight Markdoc preset together:
```
npx @astrojs/upgrade
```

@astrojs/node

withastro/astro

v9.2.0 Apr 15

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:
```
---
export const prerender = false; // Not needed with 'server' output
const cart = await Astro.session.get('cart');
---

<a href="/checkout">🛒 {cart?.length ?? 0} items</a>
```
Configuring session storage

Sessions require a storage driver to store the data. The Node, Cloudflare and Netlify adapters automatically configure a default driver for you, but other adapters currently require you to specify a custom storage driver in your configuration.

If you are using an adapter that doesn't have a default driver, or if you want to choose a different driver, you can configure it using the session configuration option:
```
import { defineConfig } from 'astro/config';
import vercel from '@astrojs/vercel';

export default defineConfig({
  adapter: vercel(),
  session: {
    driver: 'upstash',
  },
});
```
Using sessions

Sessions are available in on-demand rendered pages, API endpoints, actions and middleware.

In pages and components, you can access the session using Astro.session:
```
---
const cart = await Astro.session.get('cart');
---

<a href="/checkout">🛒 {cart?.length ?? 0} items</a>
```
In endpoints, actions, and middleware, you can access the session using context.session:
```
export async function GET(context) {
  const cart = await context.session.get('cart');
  return Response.json({ cart });
}
```
If you attempt to access the session when there is no storage driver configured, or in a prerendered page, the session object will be undefined and an error will be logged in the console:
```
---
export const prerender = true;
const cart = await Astro.session?.get('cart'); // Logs an error. Astro.session is undefined
---
```
Upgrading from Experimental to Stable

If you were previously using the experimental API, please remove the experimental.session flag from your configuration:
```
import { defineConfig } from 'astro/config';
import node from '@astrojs/node';

export default defineConfig({
   adapter: node({
     mode: "standalone",
   }),
-  experimental: {
-    session: true,
-  },
});
```
See the sessions guide for more information.

@astrojs/netlify

withastro/astro

v6.3.0 Apr 15

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:
```
---
export const prerender = false; // Not needed with 'server' output
const cart = await Astro.session.get('cart');
---

<a href="/checkout">🛒 {cart?.length ?? 0} items</a>
```
Configuring session storage

Sessions require a storage driver to store the data. The Node, Cloudflare and Netlify adapters automatically configure a default driver for you, but other adapters currently require you to specify a custom storage driver in your configuration.

If you are using an adapter that doesn't have a default driver, or if you want to choose a different driver, you can configure it using the session configuration option:
```
import { defineConfig } from 'astro/config';
import vercel from '@astrojs/vercel';

export default defineConfig({
  adapter: vercel(),
  session: {
    driver: 'upstash',
  },
});
```
Using sessions

Sessions are available in on-demand rendered pages, API endpoints, actions and middleware.

In pages and components, you can access the session using Astro.session:
```
---
const cart = await Astro.session.get('cart');
---

<a href="/checkout">🛒 {cart?.length ?? 0} items</a>
```
In endpoints, actions, and middleware, you can access the session using context.session:
```
export async function GET(context) {
  const cart = await context.session.get('cart');
  return Response.json({ cart });
}
```
If you attempt to access the session when there is no storage driver configured, or in a prerendered page, the session object will be undefined and an error will be logged in the console:
```
---
export const prerender = true;
const cart = await Astro.session?.get('cart'); // Logs an error. Astro.session is undefined
---
```
Upgrading from Experimental to Stable

If you were previously using the experimental API, please remove the experimental.session flag from your configuration:
```
import { defineConfig } from 'astro/config';
import node from '@astrojs/node';

export default defineConfig({
   adapter: node({
     mode: "standalone",
   }),
-  experimental: {
-    session: true,
-  },
});
```
See the sessions guide for more information.

Patch Changes

Updated dependencies []:
- @astrojs/underscore-redirects@0.6.0

@astrojs/cloudflare

withastro/astro

v2.5.0 Apr 15

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:
```
---
export const prerender = false; // Not needed with 'server' output
const cart = await Astro.session.get('cart');
---

<a href="/checkout">🛒 {cart?.length ?? 0} items</a>
```
Configuring session storage

Sessions require a storage driver to store the data. The Node, Cloudflare and Netlify adapters automatically configure a default driver for you, but other adapters currently require you to specify a custom storage driver in your configuration.

If you are using an adapter that doesn't have a default driver, or if you want to choose a different driver, you can configure it using the session configuration option:
```
import { defineConfig } from 'astro/config';
import vercel from '@astrojs/vercel';

export default defineConfig({
  adapter: vercel(),
  session: {
    driver: 'upstash',
  },
});
```
Using sessions

Sessions are available in on-demand rendered pages, API endpoints, actions and middleware.

In pages and components, you can access the session using Astro.session:
```
---
const cart = await Astro.session.get('cart');
---

<a href="/checkout">🛒 {cart?.length ?? 0} items</a>
```
In endpoints, actions, and middleware, you can access the session using context.session:
```
export async function GET(context) {
  const cart = await context.session.get('cart');
  return Response.json({ cart });
}
```
If you attempt to access the session when there is no storage driver configured, or in a prerendered page, the session object will be undefined and an error will be logged in the console:
```
---
export const prerender = true;
const cart = await Astro.session?.get('cart'); // Logs an error. Astro.session is undefined
---
```
Upgrading from Experimental to Stable

If you were previously using the experimental API, please remove the experimental.session flag from your configuration:
```
import { defineConfig } from 'astro/config';
import node from '@astrojs/node';

export default defineConfig({
   adapter: node({
     mode: "standalone",
   }),
-  experimental: {
-    session: true,
-  },
});
```
See the sessions guide for more information.

Patch Changes

Updated dependencies []:
- @astrojs/underscore-redirects@0.6.0

@astrojs/markdoc

withastro/astro

v0.14.0 Apr 15

Minor Changes

#13578 406501a Thanks @stramel! - The SVG import feature introduced behind a flag in v5.0.0 is no longer experimental and is available for general use.

This feature allows you to import SVG files directly into your Astro project as components and inline them into your HTML.

To use this feature, import an SVG file in your Astro project, passing any common SVG attributes to the imported component.
```
---
import Logo from './path/to/svg/file.svg';
---

<Logo <Logo width={64} height={64} fill="currentColor" />
```
If you have been waiting for stabilization before using the SVG Components feature, you can now do so.

If you were previously using this feature, please remove the experimental flag from your Astro config:
```
import { defineConfig } from 'astro'

export default defineConfig({
-  experimental: {
-    svg: true,
-  }
})
```
Additionally, a few features that were available during the experimental stage were removed in a previous release. Please see the v5.6.0 changelog for details if you have not yet already updated your project code for the experimental feature accordingly.

Please see the SVG Components guide in docs for more about this feature.

@astrojs/starlight

withastro/starlight

v0.33.2 Apr 14

Patch Changes

#3090 fc3ffa8 Thanks @delucis! - Updates internal @astrojs/mdx, @astrojs/sitemap, and astro-expressive-code dependencies
#3109 b5cc1b4 Thanks @dhruvkb! - Updates Expressive Code to v0.41.1

@astrojs/starlight-markdoc

withastro/starlight

v0.3.1 Apr 14

Patch Changes

#3090 fc3ffa8 Thanks @delucis! - Adds support for newer versions of @astrojs/markdoc
#3109 b5cc1b4 Thanks @dhruvkb! - Updates Expressive Code to v0.41.1