fix(deps): update astro monorepo (major)

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/mdx (source)	0.19.7 → 6.0.3
@astrojs/react (source)	2.3.2 → 5.0.7
@astrojs/rss (source)	2.4.4 → 4.0.18
@astrojs/sitemap (source)	1.4.0 → 3.7.3
@astrojs/tailwind (source)	3.1.3 → 6.0.2
astro (source)	2.10.15 → 6.4.8

---

Release Notes

withastro/astro (@​astrojs/mdx)

v6.0.3

Compare Source

Patch Changes

• #​16969 4a31f90 Thanks @​Princesseuh! - Adds support for Prism syntax highlighting to the Sätteri Markdown and MDX processors. Setting markdown.syntaxHighlight to 'prism' now highlights your code blocks with Prism.

  // astro.config.mjs
  import { satteri } from '@​astrojs/markdown-satteri';
  
  export default defineConfig({
    markdown: {
      processor: satteri(),
      syntaxHighlight: 'prism',
    },
  });

v6.0.2

Patch Changes

• #​16955 9a93d68 Thanks @​Princesseuh! - Updates Sätteri processor to v0.8.0. See its changelog for details on bugs fixed and features added.

• Updated dependencies [9a93d68]:

  • @​astrojs/markdown-satteri@​0.2.2

v6.0.1

Patch Changes

• Updated dependencies [eeb064c]:
  • @​astrojs/markdown-satteri@​0.2.1

v6.0.0

Compare Source

Major Changes

• #​16848 f732f3c Thanks @​Princesseuh! - Adds a new markdown.processor configuration option, allowing you to choose an alternative Markdown processor.

  Websites with many Markdown/MDX files tend to be slow to build because the unified ecosystem (e.g., remark, rehype) is slow to process. This feature introduces the ability to replace this part of the build pipeline with another processor.

  The default processor is unified(). This means that existing configurations remain unchanged and your remark/rehype plugins continue to work.

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  import { unified } from '@​astrojs/markdown-remark';
  import remarkToc from 'remark-toc';
  
  export default defineConfig({
    markdown: {
      processor: unified({
        remarkPlugins: [remarkToc],
      }),
    },
  });

  In addition to this new configuration option, Astro provides a new alternative processor based on Rust: Sätteri. You can choose to use it now by installing @astrojs/markdown-satteri, importing the satteri() processor, and adapting your existing configuration:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  import { satteri } from '@​astrojs/markdown-satteri';
  
  export default defineConfig({
    markdown: {
      processor: satteri({
        features: { directive: true },
      }),
    },
  });

  This processor does not support the remark and rehype plugins. This means you may need to convert them to MDAST or HAST plugins to retain your current functionality.

  The existing top-level markdown.remarkPlugins, markdown.rehypePlugins, markdown.remarkRehype, markdown.gfm, and markdown.smartypants options still work, but are now deprecated and will be removed in a future major update. The matching remarkPlugins, rehypePlugins, and remarkRehype options on the MDX integration are also deprecated for the same reason. To anticipate their removal, move them onto unified({...}) (or your preferred plugin processor) :

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  import remarkToc from 'remark-toc';
  import rehypeSlug from 'rehype-slug';
  + import { unified } from '@​astrojs/markdown-remark';
  
  export default defineConfig({
    markdown: {
  +    processor: unified({
  +      remarkPlugins: [remarkToc],
  +      rehypePlugins: [rehypeSlug],
  +      remarkRehype: true,
  +      gfm: true,
  +      smartypants: true,
  +    }),
  -    remarkPlugins: [remarkToc],
  -    rehypePlugins: [rehypeSlug],
  -    remarkRehype: true,
  -    gfm: true,
  -    smartypants: true,
    },
  });

  For more information on enabling and using this feature in your project, see our Markdown guide. To give feedback on this new Rust processor, see the Native Markdown / MDX parsing and processing RFC.

Minor Changes

• #​16848 f732f3c Thanks @​Princesseuh! - Adds support for using @astrojs/markdown-satteri to parse .mdx files.

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  import mdx from '@​astrojs/mdx';
  import { satteri } from '@​astrojs/markdown-satteri';
  
  export default defineConfig({
    markdown: {
      processor: satteri({
        features: { directive: true },
      }),
    },
    integrations: [mdx()],
  });

  Note that the recmaPlugins option is not supported when using Sätteri as your MDX processor. If you would like to use Sätteri for Markdown files, but still use Unified for MDX, you can pass a different Markdown processor to the MDX integration:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  import mdx from '@​astrojs/mdx';
  import { satteri } from '@​astrojs/markdown-satteri';
  import { unified } from '@​astrojs/markdown-remark';
  import myPlugin from './my-recma-plugin.js';
  
  export default defineConfig({
    markdown: {
      processor: satteri({
        features: { directive: true },
      }),
    },
    integrations: [
      mdx({
        recmaPlugins: [myPlugin],
        processor: unified(),
      }),
    ],
  });

Patch Changes

• Updated dependencies [f732f3c, f732f3c, f732f3c]:
  • @​astrojs/internal-helpers@​0.10.0
  • @​astrojs/markdown-remark@​7.2.0
  • @​astrojs/markdown-satteri@​0.2.0

v5.0.6

Compare Source

Patch Changes

• #​16579 49e10e3 Thanks @​igor-koop! - Fixes an issue where the smartypants option was ignored.

v5.0.5

Compare Source

Patch Changes

• Updated dependencies [9256345]:
  • @​astrojs/markdown-remark@​7.1.2

v5.0.4

Compare Source

Patch Changes

• Updated dependencies [f3485c3]:
  • @​astrojs/markdown-remark@​7.1.1

v5.0.3

Compare Source

Patch Changes

• Updated dependencies [10a1a5a]:
  • @​astrojs/markdown-remark@​7.1.0

v5.0.2

Compare Source

Patch Changes

• #​15864 d3c7de9 Thanks @​florian-lefebvre! - Removes temporary support for Node >=20.19.1 because Stackblitz now uses Node 22 by default

• Updated dependencies []:

  • @​astrojs/markdown-remark@​7.0.1

v5.0.1

Compare Source

Patch Changes

• #​15934 6f8f0bc Thanks @​ematipico! - Updates the Astro peerDependencies#astro to be 6.0.0.

v5.0.0

Compare Source

Major Changes

• #​14494 727b0a2 Thanks @​florian-lefebvre! - Updates Markdown heading ID generation - (v6 upgrade guidance)

• #​14427 e131261 Thanks @​florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance)

• #​14445 ecb0b98 Thanks @​florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)

Patch Changes

• #​15187 bbb5811 Thanks @​matthewp! - Update to Astro 6 beta

• #​15475 36fc0e0 Thanks @​delucis! - Fixes edge cases where an export const components = {...} declaration would fail to be detected with the optimize option enabled

• #​15264 11efb05 Thanks @​florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22

• Updated dependencies [bbb5811, cb99214, 80f0225, 727b0a2, 1fa4177, 7c55f80, 6f19ecc, f94d3c5]:

  • @​astrojs/markdown-remark@​7.0.0

v4.3.14

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.11

v4.3.13

Compare Source

Patch Changes

• Updated dependencies [d8305f8]:
  • @​astrojs/markdown-remark@​6.3.10

v4.3.12

Compare Source

Patch Changes

• #​14813 e1dd377 Thanks @​ematipico! - Removes picocolors as dependency in favor of the fork piccolore.

v4.3.11

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.9

v4.3.10

Compare Source

Patch Changes

• #​14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

  The getContainerRenderer() function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint.

  See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

v4.3.9

Patch Changes

• #​14621 e3175d9 Thanks @​GameRoMan! - Updates vite version to fix CVE

v4.3.8

Patch Changes

• #​14591 3e887ec Thanks @​matthewp! - Adds TypeScript support for the components prop on MDX Content component when using await render(). Developers now get proper IntelliSense and type checking when passing custom components to override default MDX element rendering.

• #​14598 7b45c65 Thanks @​delucis! - Reduces terminal text styling dependency size by switching from kleur to picocolors

v4.3.7

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.8

v4.3.6

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.7

v4.3.5

Compare Source

Patch Changes

• #​14326 c24a8f4 Thanks @​jsparkdev! - Updates vite version to fix CVE

v4.3.4

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.6

v4.3.3

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.5

v4.3.2

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.4

v4.3.1

Compare Source

Patch Changes

• Updated dependencies [6bd5f75]:
  • @​astrojs/markdown-remark@​6.3.3

v4.3.0

Compare Source

Minor Changes

• #​13809 3c3b492 Thanks @​ascorbic! - Increases minimum Node.js version to 18.20.8

  Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

  ⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.2

v4.2.6

Compare Source

Patch Changes

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

v4.2.5

Compare Source

Patch Changes

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

v4.2.4

Compare Source

Patch Changes

• #​13596 3752519 Thanks @​jsparkdev! - update vite to latest version to fix CVE

• #​13547 360cb91 Thanks @​jsparkdev! - Updates vite to the latest version

v4.2.3

Compare Source

Patch Changes

• #​13526 ff9d69e Thanks @​jsparkdev! - update vite to the latest version

v4.2.2

Patch Changes

• #​13505 a98ae5b Thanks @​ematipico! - Updates the dependency vite to the latest.

v4.2.1

Patch Changes

• #​13448 91c9503 Thanks @​ematipico! - Upgrade to shiki v3

• Updated dependencies [91c9503]:

  • @​astrojs/markdown-remark@​6.3.1

v4.2.0

Compare Source

Minor Changes

• #​13352 cb886dc Thanks @​delucis! - Adds support for a new experimental.headingIdCompat flag

  By default, Astro removes a trailing - from the end of IDs it generates for headings ending with
  special characters. This differs from the behavior of common Markdown processors.

  You can now disable this behavior with a new configuration flag:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  
  export default defineConfig({
    experimental: {
      headingIdCompat: true,
    },
  });

  This can be useful when heading IDs and anchor links need to behave consistently across your site
  and other platforms such as GitHub and npm.

  If you are using the rehypeHeadingIds plugin directly, you can also pass this new option:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  import { rehypeHeadingIds } from '@​astrojs/markdown-remark';
  import { otherPluginThatReliesOnHeadingIDs } from 'some/plugin/source';
  
  export default defineConfig({
    markdown: {
      rehypePlugins: [
        [rehypeHeadingIds, { experimentalHeadingIdCompat: true }],
        otherPluginThatReliesOnHeadingIDs,
      ],
    },
  });

Patch Changes

• Updated dependencies [cb886dc, a3327ff]:
  • @​astrojs/markdown-remark@​6.3.0

v4.1.1

Compare Source

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.2.1

v4.1.0

Compare Source

Minor Changes

• #​13254 1e11f5e Thanks @​p0lyw0lf! - Adds the ability to process and optimize remote images in Markdown syntax in MDX files.

  Previously, Astro only allowed local images to be optimized when included using ![]() syntax. Astro's image service could only display remote images without any processing.

  Now, Astro's image service can also optimize remote images written in standard Markdown syntax. This allows you to enjoy the benefits of Astro's image processing when your images are stored externally, for example in a CMS or digital asset manager.

  No additional configuration is required to use this feature! Any existing remote images written in Markdown will now automatically be optimized. To opt-out of this processing, write your images in Markdown using the JSX <img/> tag instead. Note that images located in your public/ folder are still never processed.

Patch Changes

• Updated dependencies [1e11f5e]:
  • @​astrojs/markdown-remark@​6.2.0

v4.0.8

Compare Source

Patch Changes

• Updated dependencies [db252e0]:
  • @​astrojs/markdown-remark@​6.1.0

v4.0.7

Compare Source

Patch Changes

• #​13011 cf30880 Thanks @​ascorbic! - Upgrades Vite

v4.0.6

Compare Source

Patch Changes

• Updated dependencies [3d89e62]:
  • @​astrojs/markdown-remark@​6.0.2

v4.0.5

Compare Source

Patch Changes

• #​12959 3a267f3 Thanks @​bluwy! - Reverts 9a3b48c which caused a regression for rendering inline MDX components and MDX files from content collections

v4.0.4

Compare Source

Patch Changes

• #​12921 aeb7e1a Thanks @​ascorbic! - Fixes a bug that caused Image component to be imported on MDX pages that did not include images

• #​12913 9a3b48c Thanks @​bluwy! - Makes internal check() function a no-op to allow faster component renders and prevent React 19 component warnings

v4.0.3

Compare Source

Patch Changes

• #​12799 739dbfb Thanks @​ascorbic! - Upgrades Vite to pin esbuild

v4.0.2

Compare Source

Patch Changes

• Updated dependencies [f13417b, 87231b1, a71e9b9]:
  • @​astrojs/markdown-remark@​6.0.1

v4.0.1

Compare Source

Patch Changes

• #​12594 4f2fd0a Thanks @​Princesseuh! - Fixes compatibility with Astro 5

v4.0.0

Compare Source

Major Changes

• #​12231 90ae100 Thanks @​bluwy! - Handles the breaking change in Astro where content pages (including .mdx pages located within src/pages/) no longer respond with charset=utf-8 in the Content-Type header.

  For MDX pages without layouts, @astrojs/mdx will automatically add the <meta charset="utf-8"> tag to the page by default. This reduces the boilerplate needed to write with non-ASCII characters. If your MDX pages have a layout, the layout component should include the <meta charset="utf-8"> tag.

  If you require charset=utf-8 to render your page correctly, make sure that your layout components have the <meta charset="utf-8"> tag added.

• #​12008 5608338 Thanks @​Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.

  Starting from this release, no breaking changes will be introduced unless absolutely necessary.

  To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.

Minor Changes

• #​12539 827093e Thanks @​bluwy! - Drops node 21 support

• #​11741 6617491 Thanks @​bluwy! - Updates adapter server entrypoint to use @astrojs/mdx/server.js

  This is an internal change. Handling JSX in your .mdx files has been moved from Astro internals and is now the responsibility of this integration. You should not notice a change in your project, and no update to your code is required.

Patch Changes

• #​12075 a19530e Thanks @​bluwy! - Parses frontmatter ourselves

• #​11861 3ab3b4e Thanks @​bluwy! - Updates @astrojs/markdown-remark and handle its breaking changes

• #​12533 1b61fdf Thanks @​ematipico! - Fixes a case where the MDX renderer couldn't be loaded when used as a direct dependency of an Astro integration.

• Updated dependencies [3ab3b4e, 5608338, 560ef15, 83a2a64, 3ab3b4e, a19530e]:

  • @​astrojs/markdown-remark@​6.0.0

v3.1.9

Compare Source

Patch Changes

• #​12245 1d4f6a4 Thanks @​bmenant! - Add components property to MDXInstance type definition (RenderResult and module import)

v3.1.8

Compare Source

Patch Changes

• Updated dependencies [710a1a1]:
  • @​astrojs/markdown-remark@​5.3.0

v3.1.7

Compare Source

Patch Changes

• #​12026 40e7a1b Thanks @​bluwy! - Initializes the MDX processor only when there's .mdx files

v3.1.6

Compare Source

Patch Changes

• #​11975 c9ae7b1 Thanks @​bluwy! - Handles nested root hast node when optimizing MDX

v3.1.5

Compare Source

Patch Changes

• #​11818 88ef1d0 Thanks @​bluwy! - Fixes CSS in the layout component to be ordered first before any other components in the MDX file

v3.1.4

Compare Source

Patch Changes

• #​11717 423614e Thanks @​bluwy! - Fixes stack trace location when failed to parse an MDX file with frontmatter

v3.1.3

Compare Source

Patch Changes

• Updated dependencies [49b5145]:
  • @​astrojs/markdown-remark@​5.2.0

v3.1.2

Compare Source

Patch Changes

• Updated dependencies [b6afe6a]:
  • @​astrojs/markdown-remark@​5.1.1

v3.1.1

Compare Source

Patch Changes

• #​11263 7d59750 Thanks @​wackbyte! - Refactor to use Astro's integration logger for logging

v3.1.0

Compare Source

Minor Changes

• #​11144 803dd80 Thanks @​ematipico! - The integration now exposes a function called getContainerRenderer, that can be used inside the Container APIs to load the relative renderer.

  import { experimental_AstroContainer as AstroContainer } from 'astro/container';
  import ReactWrapper from '../src/components/ReactWrapper.astro';
  import { loadRenderers } from 'astro:container';
  import { getContainerRenderer } from '@​astrojs/react';
  
  test('ReactWrapper with react renderer', async () => {
    const renderers = await loadRenderers([getContainerRenderer()]);
    const container = await AstroContainer.create({
      renderers,
    });
    const result = await container.renderToString(ReactWrapper);
  
    expect(result).toContain('Counter');
    expect(result).toContain('Count: <!-- -->5');
  });

v3.0.1

Compare Source

Patch Changes

• #​10813 3cc3e2c Thanks @​Xetera! - Omitting compiler-internal symbol from user components to fix breaking error messages

v3.0.0

Compare Source

Major Changes

• #​10935 ddd8e49 Thanks @​bluwy! - Refactors the MDX transformation to rely only on the unified pipeline. Babel and esbuild transformations are removed, which should result in faster build times. The refactor requires using Astro v4.8.0 but no other changes are necessary.

• #​10935 ddd8e49 Thanks @​bluwy! - Allows integrations after the MDX integration to update markdown.remarkPlugins and markdown.rehypePlugins, and have the plugins work in MDX too.

  If your integration relies on Astro's previous behavior that prevents integrations from adding remark/rehype plugins for MDX, you will now need to configure @astrojs/mdx with extendMarkdownConfig: false and explicitly specify any remarkPlugins and rehypePlugins options instead.

• #​10935 ddd8e49 Thanks @​bluwy! - Renames the optimize.customComponentNames option to optimize.ignoreElementNames to better reflect its usecase. Its behaviour is not changed and should continue to work as before.

• #​10935 ddd8e49 Thanks @​bluwy! - Replaces the internal remark-images-to-component plugin with rehype-images-to-component to let users use additional rehype plugins for images

Patch Changes

• #​10935 ddd8e49 Thanks @​bluwy! - Simplifies plain MDX components as hast element nodes to further improve HTML string inlining for the optimize option

• #​10935 ddd8e49 Thanks @​bluwy! - Allows Vite plugins to transform .mdx files before the MDX plugin transforms it

• #​10935 ddd8e49 Thanks @​bluwy! - Updates the optimize option to group static sibling nodes as a <Fragment />. This reduces the number of AST nodes and simplifies runtime rendering of MDX pages.

• #​10935 ddd8e49 Thanks @​bluwy! - Tags the MDX component export for quicker component checks while rendering

• #​10935 ddd8e49 Thanks @​bluwy! - Fixes export const components keys detection for the optimize option

• #​10935 ddd8e49 Thanks @​bluwy! - Improves optimize handling for MDX components with attributes and inline MDX components

v2.3.1

Compare Source

Patch Changes

• #​10754 3e7a12c8532411e580fcfdb8445cad8fc8499291 Thanks @​rishi-raj-jain! - Fixes an issue where images in MDX required a relative specifier (e.g. ./)

  Now, you can use the standard ![](img.png) syntax in MDX files for images colocated in the same folder: no relative specifier required!

  There is no need to update your project; your existing images will still continue to work. However, you may wish to remove any relative specifiers from these MDX images as they are no longer necessary:

  - ![A cute dog](./dog.jpg)
  + ![A cute dog](dog.jpg)
  <!-- This dog lives in the same folder as my article! -->

• #​10770 88ee63a3ba4488c60348cb821034e6d4a057efd0 Thanks @​bluwy! - Removes internal MDX processor on buildEnd to free up memory

v2.3.0

Compare Source

Minor Changes

• #​10689 683d51a5eecafbbfbfed3910a3f1fbf0b3531b99 Thanks @​ematipico! - Deprecate support for versions of Node.js older than v18.17.1 for Node.js 18, older than v20.0.3 for Node.js 20, and the complete Node.js v19 release line.

  This change is in line with Astro's Node.js support policy.

Patch Changes

• Updated dependencies [ccafa8d230f65c9302421a0ce0a0adc5824bfd55]:
  • [@

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
astro-typescript-react-tailwind	Error			Aug 31, 2025 11:07am

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}