chore(deps): bump astro and astro-expressive-code in /website-astro

[dependabot]

Bumps astro and astro-expressive-code. These dependencies needed to be updated together.
Updates astro from 7.0.2 to 7.1.3

Release notes

Sourced from astro's releases.

astro@7.1.3

Patch Changes

• #17427 630b382 Thanks @​astrobot-houston! - Fixes image optimization during astro build using too many parallel processes in CPU-limited containers. Builds now respect the container's CPU limit, reducing peak memory usage and avoiding out-of-memory crashes.

astro@7.1.2

Patch Changes

• #17445 a5f7230 Thanks @​ocavue! - Updates dependency cookie to v2. Cookie values made entirely of URL-safe characters are no longer percent-encoded in Set-Cookie headers; encoded values round-trip exactly as before.

• #17402 a89c137 Thanks @​farrosfr! - Fixes a bug where mutated Astro.locals during the request lifecycle are lost and not passed to custom error pages (404.astro/500.astro)

• #17405 91992ef Thanks @​Araluma! - Prevents an unhandled promise rejection from the prefetch fetch fallback. In WebKit (Safari), <link rel="prefetch"> is unsupported, so prefetch uses the fetch() fallback; on a flaky connection that fetch rejects with TypeError: Load failed, and because the promise was not awaited or caught, it surfaced as an unhandled rejection to the page's global error handlers. The best-effort prefetch now swallows the failure with .catch().

astro@7.1.1

Patch Changes

• #17399 4b03702 Thanks @​matthewp! - Fixes encoded request paths being routed incorrectly when using domain-based i18n

astro@7.1.0

Minor Changes

• #17302 5f4dc03 Thanks @​astrobot-houston! - Adds a new deferRender option to the glob() content loader

  When set to true, renderable entries (such as Markdown) are not rendered during content sync. Instead, rendering is deferred until the entry is actually rendered in a page, using the same on-demand path that .mdx files already use.

  This reduces memory usage during astro build for large collections whose rendered output is much larger than the source — for example, Markdown that uses heavy rehype plugins like rehype-katex. Such builds could previously run out of memory while storing the eagerly-rendered HTML for every entry.

  // src/content.config.ts
  import { defineCollection } from 'astro:content';
  import { glob } from 'astro/loaders';
  const docs = defineCollection({
  loader: glob({ pattern: '**/*.md', base: 'src/content/docs', deferRender: true }),
  });

  By default deferRender is false, preserving the existing behavior of rendering entries eagerly during sync so their rendered HTML can be cached across builds.

• #17296 30698a2 Thanks @​ematipico! - Adds a new experimental collectionStorage option for controlling how the content layer persists its data store

  By default, Astro serializes the entire content layer data store to a single file (.astro/data-store.json). For very large content collections, this file can grow large enough to hit platform file-size limits.

  Set experimental.collectionStorage: 'chunked' to instead split the data store across many smaller, content-addressed files inside a .astro/data-store/ directory, described by a manifest:

  // astro.config.mjs

... (truncated)

Changelog

Sourced from astro's changelog.

7.1.3

Patch Changes

• #17427 630b382 Thanks @​astrobot-houston! - Fixes image optimization during astro build using too many parallel processes in CPU-limited containers. Builds now respect the container's CPU limit, reducing peak memory usage and avoiding out-of-memory crashes.

7.1.2

Patch Changes

• #17445 a5f7230 Thanks @​ocavue! - Updates dependency cookie to v2. Cookie values made entirely of URL-safe characters are no longer percent-encoded in Set-Cookie headers; encoded values round-trip exactly as before.

• #17402 a89c137 Thanks @​farrosfr! - Fixes a bug where mutated Astro.locals during the request lifecycle are lost and not passed to custom error pages (404.astro/500.astro)

• #17405 91992ef Thanks @​Araluma! - Prevents an unhandled promise rejection from the prefetch fetch fallback. In WebKit (Safari), <link rel="prefetch"> is unsupported, so prefetch uses the fetch() fallback; on a flaky connection that fetch rejects with TypeError: Load failed, and because the promise was not awaited or caught, it surfaced as an unhandled rejection to the page's global error handlers. The best-effort prefetch now swallows the failure with .catch().

7.1.1

Patch Changes

• #17399 4b03702 Thanks @​matthewp! - Fixes encoded request paths being routed incorrectly when using domain-based i18n

7.1.0

Minor Changes

• #17302 5f4dc03 Thanks @​astrobot-houston! - Adds a new deferRender option to the glob() content loader

  When set to true, renderable entries (such as Markdown) are not rendered during content sync. Instead, rendering is deferred until the entry is actually rendered in a page, using the same on-demand path that .mdx files already use.

  This reduces memory usage during astro build for large collections whose rendered output is much larger than the source — for example, Markdown that uses heavy rehype plugins like rehype-katex. Such builds could previously run out of memory while storing the eagerly-rendered HTML for every entry.

  // src/content.config.ts
  import { defineCollection } from 'astro:content';
  import { glob } from 'astro/loaders';
  const docs = defineCollection({
  loader: glob({ pattern: '**/*.md', base: 'src/content/docs', deferRender: true }),
  });

  By default deferRender is false, preserving the existing behavior of rendering entries eagerly during sync so their rendered HTML can be cached across builds.

• #17296 30698a2 Thanks @​ematipico! - Adds a new experimental collectionStorage option for controlling how the content layer persists its data store

  By default, Astro serializes the entire content layer data store to a single file (.astro/data-store.json). For very large content collections, this file can grow large enough to hit platform file-size limits.

... (truncated)

Commits

• cf9ffc7 [ci] release (#17455)
• 630b382 Use os.availableParallelism() for image optimization queue to fix OOM in CP...
• 8a7f7e0 [ci] release (#17411)
• ebbd793 chore(deps): update astro-embed (#17436)
• 311e42c [ci] format
• 1d62202 chore(deps): update neotraverse to v1 (#17446)
• a5f7230 fix(astro): update cookie to v2 (#17445)
• 91992ef fix(prefetch): swallow fetch-fallback rejection to avoid unhandled 'Load fail...
• a89c137 fix(astro): propagate mutated locals to custom error pages (#17402)
• 91c645a [ci] release (#17403)
• Additional commits viewable in compare view

Updates astro-expressive-code from 0.41.7 to 0.44.1

Release notes

Sourced from astro-expressive-code's releases.

astro-expressive-code@0.44.1

Patch Changes

• ef538d8: Prevent a white corner from appearing when themed horizontal and vertical scrollbars are both visible.
• Updated dependencies [ef538d8]
  • rehype-expressive-code@0.44.1

astro-expressive-code@0.44.0

Minor Changes

• 9169010: Adds support for Astro v7 and Sätteri v0.9

Patch Changes

• rehype-expressive-code@0.44.0

astro-expressive-code@0.43.1

Patch Changes

• d9a3942: Avoids Astro 6.4 deprecation warnings by registering Expressive Code with the Unified Markdown processor when available.
  • rehype-expressive-code@0.43.1

astro-expressive-code@0.43.0

Minor Changes

• ce8d751: Adds support for the Sätteri Markdown processor introduced in Astro 6.4.

  When your Astro config sets markdown.processor to satteri() (from @astrojs/markdown-satteri), code blocks are now processed by Expressive Code through an equivalent Sätteri HAST plugin instead of the rehype plugin, which Sätteri does not run. The default unified pipeline keeps working exactly as before, and no configuration changes are required to benefit from this.

  Thank you @​Princesseuh!

Patch Changes

• rehype-expressive-code@0.43.0

astro-expressive-code@0.42.0

Patch Changes

• rehype-expressive-code@0.42.0

Changelog

Sourced from astro-expressive-code's changelog.

0.44.1

Patch Changes

• ef538d8: Prevent a white corner from appearing when themed horizontal and vertical scrollbars are both visible.
• Updated dependencies [ef538d8]
  • rehype-expressive-code@0.44.1

0.44.0

Minor Changes

• 9169010: Adds support for Astro v7 and Sätteri v0.9

Patch Changes

• rehype-expressive-code@0.44.0

0.43.1

Patch Changes

• d9a3942: Avoids Astro 6.4 deprecation warnings by registering Expressive Code with the Unified Markdown processor when available.
  • rehype-expressive-code@0.43.1

0.43.0

Minor Changes

• ce8d751: Adds support for the Sätteri Markdown processor introduced in Astro 6.4.

  When your Astro config sets markdown.processor to satteri() (from @astrojs/markdown-satteri), code blocks are now processed by Expressive Code through an equivalent Sätteri HAST plugin instead of the rehype plugin, which Sätteri does not run. The default unified pipeline keeps working exactly as before, and no configuration changes are required to benefit from this.

  Thank you @​Princesseuh!

Patch Changes

• rehype-expressive-code@0.43.0

0.42.0

Patch Changes

• rehype-expressive-code@0.42.0

Commits

• e0f1321 [CI] Release (#462)
• a77ac26 [CI] Release (#455)
• 9169010 Support Astro v7 (#454)
• fefbae4 [CI] Release (#450)
• d9a3942 Avoid Astro 6.4 deprecation warnings (#449)
• 25b12e7 [CI] Release (#447)
• 1fe1465 Internalize Sätteri plugin to improve dependency tree (#448)
• ce8d751 Add support for the Sätteri Markdown processor introduced in Astro 6.4.0
• 24fc652 [CI] Release (#443)
• 1ff2c57 Update shiki to v4 (#442)
• Additional commits viewable in compare view