Bump astro from 5.5.5 to 5.7.0

[dependabot]

Bumps astro from 5.5.5 to 5.7.0.

Release notes

Sourced from astro's releases.

astro@5.7.0

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:

... (truncated)

Changelog

Sourced from astro's changelog.

5.7.0

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:

... (truncated)

Commits

• 59af0cb [ci] release (#13610)
• 406501a feat: unflag svg component feature (#13578)
• 93470a1 add missing message to a Fonts API error (#13612)
• 0e5b4ce [ci] format
• f5de51e fix(routing): handle base path with trailing slash 'never' configuration (#13...
• 29ab38e [ci] format
• b1fe521 feat(fonts): experimental release (#12775)
• 762cc7f [ci] format
• df3fd54 feat: make astro:config stable (#13560)
• 3903068 [ci] format
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)