[ci] release #13610

astrobot-houston · 2025-04-14T09:01:20Z

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

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.
#12775 b1fe521 Thanks @florian-lefebvre! - Adds a new, experimental Fonts API to provide first-party support for fonts in Astro.

This experimental feature allows you to use fonts from both your file system and several built-in supported providers (e.g. Google, Fontsource, Bunny) through a unified API. Keep your site performant thanks to sensible defaults and automatic optimizations including fallback font generation.

To enable this feature, configure an experimental.fonts object with one or more fonts:
```
import { defineConfig, fontProviders } from "astro/config"

export default defineConfig({
    experimental: {
        fonts: [{
            provider: fontProviders.google(),
      `      name: "Roboto",
            cssVariable: "--font-roboto",
        }]
    }
})
```
Then, add a <Font /> component and site-wide styling in your <head>:
```
---
import { Font } from 'astro:assets';
---

<Font cssVariable="--font-roboto" preload />
<style>
  body {
    font-family: var(--font-roboto);
  }
</style>
```
Visit the experimental Fonts documentation for the full API, how to get started, and even how to build your own custom AstroFontProvider if we don't yet support your preferred font service.

For a complete overview, and to give feedback on this experimental API, see the Fonts RFC and help shape its future.
#13560 df3fd54 Thanks @ematipico! - The virtual module astro:config introduced behind a flag in v5.2.0 is no longer experimental and is available for general use.

This virtual module exposes two sub-paths for type-safe, controlled access to your configuration:
- astro:config/client: exposes config information that is safe to expose to the client.
- astro:config/server: exposes additional information that is safe to expose to the server, such as file and directory paths.
Access these in any file inside your project to import and use select values from your Astro config:
```
// src/utils.js
import { trailingSlash } from 'astro:config/client';

function addForwardSlash(path) {
  if (trailingSlash === 'always') {
    return path.endsWith('/') ? path : path + '/';
  } else {
    return path;
  }
}
```
If you were previously using this feature, please remove the experimental flag from your Astro config:
```
// astro.config.mjs
export default defineConfig({
-  experimental: {
-    serializeConfig: true
-  }
})
```
If you have been waiting for feature stabilization before using configuration imports, you can now do so.

Please see the astro:config reference for more about this feature.
#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.

Patch Changes

#13602 3213450 Thanks @natemoo-re! - Updates the Audit dev toolbar app to automatically strip data-astro-source-file and data-astro-source-loc attributes in dev mode.
#13598 f5de51e Thanks @dreyfus92! - Fix routing with base paths when trailingSlash is set to 'never'. This ensures requests to '/base' are correctly matched when the base path is set to '/base', without requiring a trailing slash.
#13603 d038030 Thanks @sarah11918! - Adds the minimal starter template to the list of create astro options

Good news if you're taking the introductory tutorial in docs, making a minimal reproduction, or just want to start a project with as little to rip out as possible. Astro's minimal (empty) template is now back as one of the options when running create astro@latest and starting a new project!

@astrojs/[email protected]

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/[email protected]

@astrojs/[email protected]

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/[email protected]

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/[email protected]

@astrojs/[email protected]

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.

codspeed-hq · 2025-04-14T09:13:37Z

CodSpeed Performance Report

Merging #13610 will create unknown performance changes

_{Comparing changeset-release/main (8603b8c) with main (2fd6a6b)}

Summary

🆕 6 new benchmarks

Benchmarks breakdown

	Benchmark	`BASE`	`HEAD`	Change
🆕	`Rendering: streaming [false], .astro file`	N/A	886.4 ms	N/A
🆕	`Rendering: streaming [false], .md file`	N/A	12.8 ms	N/A
🆕	`Rendering: streaming [false], .mdx file`	N/A	715.6 ms	N/A
🆕	`Rendering: streaming [true], .astro file`	N/A	936.3 ms	N/A
🆕	`Rendering: streaming [true], .md file`	N/A	12.8 ms	N/A
🆕	`Rendering: streaming [true], .mdx file`	N/A	720.2 ms	N/A

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

github-actions bot added pkg: example Related to an example package (scope) pkg: astro Related to the core `astro` package (scope) labels Apr 14, 2025

github-actions bot force-pushed the changeset-release/main branch 3 times, most recently from 6d6e21c to 71a2b84 Compare April 14, 2025 09:03

github-actions bot force-pushed the changeset-release/main branch 8 times, most recently from 2af9795 to 70474c4 Compare April 15, 2025 08:42

[ci] release

c048dc0

github-actions bot force-pushed the changeset-release/main branch from 70474c4 to c048dc0 Compare April 15, 2025 09:14

ematipico merged commit 59af0cb into main Apr 15, 2025

ematipico deleted the changeset-release/main branch April 15, 2025 09:36

openscript pushed a commit to openscript/astro that referenced this pull request Sep 12, 2025

[ci] release (withastro#13610)

4b62be7

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

[ci] release #13610

[ci] release #13610

Uh oh!

astrobot-houston commented Apr 14, 2025 •

edited

Loading

Uh oh!

codspeed-hq bot commented Apr 14, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

[ci] release #13610

[ci] release #13610

Uh oh!

Conversation

astrobot-houston commented Apr 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Releases

[email protected]

Minor Changes

Configuring session storage

Using sessions

Upgrading from Experimental to Stable

Patch Changes

@astrojs/[email protected]

Minor Changes

Configuring session storage

Using sessions

Upgrading from Experimental to Stable

Patch Changes

@astrojs/[email protected]

Minor Changes

@astrojs/[email protected]

Minor Changes

Configuring session storage

Using sessions

Upgrading from Experimental to Stable

Patch Changes

@astrojs/[email protected]

Minor Changes

Configuring session storage

Using sessions

Upgrading from Experimental to Stable

Uh oh!

codspeed-hq bot commented Apr 14, 2025

CodSpeed Performance Report

Merging #13610 will create unknown performance changes

Summary

Benchmarks breakdown

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

astrobot-houston commented Apr 14, 2025 •

edited

Loading