chore(deps): update dependency @astrojs/mdx to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/mdx (source)	^5.0.4 → ^6.0.0

---

Release Notes

withastro/astro (@​astrojs/mdx)

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

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• 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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (906 entries)...

   ╭─────────────────────────────────────────╮
   │                                         │
   │   Update available! 11.2.2 → 11.5.0.    │
   │   Changelog: https://pnpm.io/v/11.5.0   │
   │    To update, run: pnpm add -g pnpm     │
   │                                         │
   ╰─────────────────────────────────────────╯

✓ Lockfile passes supply-chain policies (906 entries in 7.3s)
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 21, reused 0, downloaded 0, added 0
Progress: resolved 120, reused 0, downloaded 0, added 0
Progress: resolved 258, reused 0, downloaded 0, added 0
Progress: resolved 395, reused 0, downloaded 0, added 0
Progress: resolved 503, reused 0, downloaded 0, added 0
Progress: resolved 510, reused 0, downloaded 0, added 0
Progress: resolved 515, reused 0, downloaded 0, added 0
Progress: resolved 525, reused 0, downloaded 0, added 0
Progress: resolved 587, reused 0, downloaded 0, added 0
Progress: resolved 628, reused 0, downloaded 0, added 0
Progress: resolved 729, reused 0, downloaded 0, added 0
Progress: resolved 856, reused 0, downloaded 0, added 0
Progress: resolved 881, reused 0, downloaded 0, added 0
Progress: resolved 903, reused 0, downloaded 0, added 0
Progress: resolved 908, reused 0, downloaded 0, added 0
[ERR_PNPM_NO_MATURE_MATCHING_VERSION] 4 versions do not meet the minimumReleaseAge constraint:
  @astrojs/internal-helpers@0.10.0 was published at 2026-05-28T09:58:57.569Z, within the minimumReleaseAge cutoff (2026-05-27T20:17:19.945Z)
  @astrojs/internal-helpers@0.10.0 was published at 2026-05-28T09:58:57.569Z, within the minimumReleaseAge cutoff (2026-05-27T20:17:19.945Z)
  @astrojs/markdown-remark@7.2.0 was published at 2026-05-28T09:59:02.354Z, within the minimumReleaseAge cutoff (2026-05-27T20:17:19.945Z)
  @astrojs/mdx@6.0.0 was published at 2026-05-28T09:58:56.623Z, within the minimumReleaseAge cutoff (2026-05-27T20:17:19.945Z)

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	guildkit-website	3ae578a	May 30 2026, 08:18 PM