Bump the astro-stack group across 1 directory with 3 updates

[dependabot]

Bumps the astro-stack group with 3 updates in the / directory: @astrojs/mdx, @astrojs/sitemap and astro.

Updates @astrojs/mdx from 7.0.8 to 8.0.0

Release notes

Sourced from @​astrojs/mdx's releases.

@​astrojs/mdx@​8.0.0

Major Changes

• #17262 f8e9458 Thanks @​Princesseuh! - Moves MDX file processing to the Markdown processors.

  '@​astrojs/mdx' is still required to add MDX support to your project. However, it now delegates the MDX files processing to Markdown processors.

  What should I do?

  If you haven't explicitly installed a Markdown processor, you don't need to do anything.

  Otherwise, ensure that your configured Markdown processor uses the following version:

  • @astrojs/markdown-satteri 0.4.0 or later if you use satteri()
  • @astrojs/markdown-remark 7.3.0 or later if you use unified()

Patch Changes

• #17262 f8e9458 Thanks @​Princesseuh! - Fixes .mdx files still using markdown.processor when extendMarkdownConfig is false. They now use a clean default processor instead; pass mdx({ processor }) to choose one explicitly.

• #17262 f8e9458 Thanks @​Princesseuh! - Adds a warning when the deprecated remarkPlugins, rehypePlugins, recmaPlugins and remarkRehype options are ignored because your Markdown processor does not run them. They still apply when your processor is unified(), and were previously dropped silently otherwise.

• Updated dependencies [f8e9458, f8e9458]:

  • @​astrojs/internal-helpers@​0.11.0
  • @​astrojs/markdown-satteri@​0.4.0

Changelog

Sourced from @​astrojs/mdx's changelog.

8.0.0

Major Changes

• #17262 f8e9458 Thanks @​Princesseuh! - Moves MDX file processing to the Markdown processors.

  '@​astrojs/mdx' is still required to add MDX support to your project. However, it now delegates the MDX files processing to Markdown processors.

  What should I do?

  If you haven't explicitly installed a Markdown processor, you don't need to do anything.

  Otherwise, ensure that your configured Markdown processor uses the following version:

  • @astrojs/markdown-satteri 0.4.0 or later if you use satteri()
  • @astrojs/markdown-remark 7.3.0 or later if you use unified()

Patch Changes

• #17262 f8e9458 Thanks @​Princesseuh! - Fixes .mdx files still using markdown.processor when extendMarkdownConfig is false. They now use a clean default processor instead; pass mdx({ processor }) to choose one explicitly.

• #17262 f8e9458 Thanks @​Princesseuh! - Adds a warning when the deprecated remarkPlugins, rehypePlugins, recmaPlugins and remarkRehype options are ignored because your Markdown processor does not run them. They still apply when your processor is unified(), and were previously dropped silently otherwise.

• Updated dependencies [f8e9458, f8e9458]:

  • @​astrojs/internal-helpers@​0.11.0
  • @​astrojs/markdown-satteri@​0.4.0

Commits

• 2fdf731 [ci] release (#17849)
• bd7af0b chore(deps): update react to v19 in fixtures (#16905)
• f8e9458 feat: move MDX into the processors themselves (#17262)
• eb87a23 Escape set:text values in Astro JSX (#17847)
• See full diff in compare view

Updates @astrojs/sitemap from 3.7.3 to 3.7.4

Release notes

Sourced from @​astrojs/sitemap's releases.

@​astrojs/sitemap@​3.7.4

Patch Changes

• #17851 52d3f56 Thanks @​astro-factory! - Fixes the sitemap outputting a URL with an empty path for the homepage (e.g. https://example.com instead of https://example.com/) when trailingSlash is set to "never" or build.format is set to "file"

Changelog

Sourced from @​astrojs/sitemap's changelog.

3.7.4

Patch Changes

• #17851 52d3f56 Thanks @​astro-factory! - Fixes the sitemap outputting a URL with an empty path for the homepage (e.g. https://example.com instead of https://example.com/) when trailingSlash is set to "never" or build.format is set to "file"

Commits

• 2fdf731 [ci] release (#17849)
• 52d3f56 fix(@​astrojs/sitemap): preserve root path / in sitemap URLs when trailingSl...
• 2bfb179 chore: simpler package.json types (#17229)
• See full diff in compare view

Updates astro from 7.2.9 to 7.3.1

Release notes

Sourced from astro's releases.

astro@7.3.1

Patch Changes

• #17899 0389640 Thanks @​ematipico! - Fixes an error that prevented projects using astro:assets from starting or building

astro@7.3.0

Minor Changes

• #17767 ce7c91f Thanks @​astro-factory! - Adds --ignore-lock flag to astro preview, allowing multiple preview servers to run simultaneously on different ports. This is useful for E2E testing workflows (e.g., Playwright) that need to run several preview servers at once.

• #17818 c0b6581 Thanks @​florian-lefebvre! - Adds a logger parameter to image services hooks

  Custom image services now receive Astro's runtime logger as an extra argument. Messages logged with it are routed through the destination configured in logger and respect your log level, instead of being written straight to the console:

  import type { LocalImageService } from 'astro';
  const service: LocalImageService = {
  // ...
  async transform(inputBuffer, transform, imageConfig, logger) {
  logger.warn(Could not optimize "${transform.src}". Passing it through unchanged.);
  return { data: inputBuffer, format: 'png' };
  },
  };

  Astro's built-in Sharp service now uses this logger for the warnings it emits when it encounters an unexpected or unsupported source format.

• #17818 c0b6581 Thanks @​florian-lefebvre! - Adds logger to the context object passed to cache providers

  Custom cache providers now receive Astro's runtime logger on the context passed to onRequest(). Messages logged with it are routed through the destination configured in logger and respect your log level, instead of being written straight to the console:

  import type { CacheProvider } from 'astro';
  const provider: CacheProvider = {
  name: 'my-cache',
  async onRequest({ request, url, logger }, next) {
  logger.warn(Skipping cache for ${url.pathname} because the response sets a cookie.);
  return next();
  },
  // ...
  };

  Astro's built-in memoryCache() provider now uses this logger for the warnings it emits when it skips caching a response that sets cookies, and when a background revalidation fails.

Patch Changes

• #17818 c0b6581 Thanks @​florian-lefebvre! - Updates Astro's remaining internal warnings and errors to be written through the configured logger instead of directly to the console, when possible

... (truncated)

Changelog

Sourced from astro's changelog.

7.3.1

Patch Changes

• #17899 0389640 Thanks @​ematipico! - Fixes an error that prevented projects using astro:assets from starting or building

7.3.0

Minor Changes

• #17767 ce7c91f Thanks @​astro-factory! - Adds --ignore-lock flag to astro preview, allowing multiple preview servers to run simultaneously on different ports. This is useful for E2E testing workflows (e.g., Playwright) that need to run several preview servers at once.

• #17818 c0b6581 Thanks @​florian-lefebvre! - Adds a logger parameter to image services hooks

  Custom image services now receive Astro's runtime logger as an extra argument. Messages logged with it are routed through the destination configured in logger and respect your log level, instead of being written straight to the console:

  import type { LocalImageService } from 'astro';
  const service: LocalImageService = {
  // ...
  async transform(inputBuffer, transform, imageConfig, logger) {
  logger.warn(Could not optimize "${transform.src}". Passing it through unchanged.);
  return { data: inputBuffer, format: 'png' };
  },
  };

  Astro's built-in Sharp service now uses this logger for the warnings it emits when it encounters an unexpected or unsupported source format.

• #17818 c0b6581 Thanks @​florian-lefebvre! - Adds logger to the context object passed to cache providers

  Custom cache providers now receive Astro's runtime logger on the context passed to onRequest(). Messages logged with it are routed through the destination configured in logger and respect your log level, instead of being written straight to the console:

  import type { CacheProvider } from 'astro';
  const provider: CacheProvider = {
  name: 'my-cache',
  async onRequest({ request, url, logger }, next) {
  logger.warn(Skipping cache for ${url.pathname} because the response sets a cookie.);
  return next();
  },
  // ...
  };

  Astro's built-in memoryCache() provider now uses this logger for the warnings it emits when it skips caching a response that sets cookies, and when a background revalidation fails.

Patch Changes

... (truncated)

Commits

• 92f23cc [ci] release (#17900)
• 0389640 fix: dont use internal paths (#17899)
• f800de1 [ci] release (#17881)
• 1e0b7e6 [ci] format
• 4671a5c chore(deps): update react to v19 in 0-css fixture (#17888)
• 31b886b Update bundled Zod to 4.5 (#17862)
• e747cba Skip unsupported Vary responses in the memory cache (#17886)
• fb5b0d0 [ci] format
• ce7c91f Add --ignore-lock flag support to astro preview (#17767)
• c0b6581 feat: use logger instead of console where possible (#17818)
• Additional commits viewable in compare view