fix(deps): update dependency @astrojs/mdx to v8

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/mdx (source)	^7.0.0 → ^8.0.0

---

Release Notes

withastro/astro (@​astrojs/mdx)

v8.0.1

Compare Source

Patch Changes

• Updated dependencies [a548223]:
  • @​astrojs/markdown-satteri@0.4.1

v8.0.0

Compare Source

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

---

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 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.

[cursor]

Dependency review: @astrojs/mdx 7 → 8

This PR is not mergeable as it stands. The remote branch is still the old Astro 7 monorepo bump (already landed in #228). GitHub reports CONFLICTING on package-lock.json, and package.json on the branch still has @astrojs/mdx: ^7.0.0 — so the advertised v8 update is not actually on the PR yet.

Breaking changes (@astrojs/mdx@8.0.0)

MDX compilation is now delegated to the Markdown processor (changelog):

• Default mdx() with no custom processor needs no config change.
• If a processor is configured: @astrojs/markdown-satteri@0.4.0+ or @astrojs/markdown-remark@7.3.0+.
• extendMarkdownConfig: false now uses a clean default processor for .mdx (pass mdx({ processor }) to opt in).
• Deprecated remarkPlugins / rehypePlugins / recmaPlugins / remarkRehype now warn when the processor ignores them (previously silent).

This repo is on the no-op path. astro.config.mjs uses mdx() with no options, no remark/rehype/recma plugins, and no custom processor. Peers are satisfied by the current astro@7.3.1 lock (astro@^7.2.6, @astrojs/markdown-satteri@^0.4.0; markdown-remark is optional). No application code changes are required.

Lockfile conflict — resolved locally, could not push

I merged origin/master, took master’s lockfile, set @astrojs/mdx to ^8.0.0, and ran npm install. Local HEAD 1893369c0f99d78b449edbd10e8ebb0b728f15e4 has:

• @astrojs/mdx@8.0.0
• @astrojs/markdown-satteri@0.4.0 (required peer)
• astro@7.3.1 (unchanged from master)

git push to renovate/major-astro-monorepo was rejected by ruleset Default (Visual snapshot tests + CodeQL on the new SHA before the ref can update) — same blocker as #228.

Verification (local, on the regenerated tree)

• npm run build (astro check + static build): 0 errors, 11 pages
• Compiled archived using-mdx.mdx (embedded Astro HeaderLink + markdown headings): OK
• npm run test:visual: 8/8 snapshots passed

What to do next

Tick Renovate’s rebase/retry checkbox so it rebases onto master and writes the v8 bump + lockfile itself. After that, no astro.config.mjs or content-schema changes should be needed. A maintainer with ruleset bypass can also push 1893369 if you’d rather land the already-tested local resolution.

  

_{Sent by Cursor Automation: Dep review}

[cursor]

On the current PR HEAD this is still ^7.0.0 (the Astro 7 bump already merged in #228). After rebasing onto master, this needs to be ^8.0.0.

@astrojs/mdx@8.0.0 peers astro@^7.2.6 and @astrojs/markdown-satteri@^0.4.0. Master already locks astro@7.3.1; a lockfile regen pulls satteri 0.4.0. This config uses bare mdx() with no plugins, so no astro.config.mjs change is required.