Repository navigation
fix(deps): update dependency @astrojs/mdx to v8 - #229
renovate[bot] wants to merge 1 commit into
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
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: falsenow uses a clean default processor for.mdx(passmdx({ processor })to opt in).- Deprecated
remarkPlugins/rehypePlugins/recmaPlugins/remarkRehypenow 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 AstroHeaderLink+ 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
| "dependencies": { | ||
| "@astrojs/check": "^0.9.9", | ||
| "@astrojs/mdx": "^5.0.0", | ||
| "@astrojs/mdx": "^7.0.0", |
There was a problem hiding this comment.
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.
1 participant
This PR contains the following updates:
^7.0.0→^8.0.0Release Notes
withastro/astro (@astrojs/mdx)
v8.1.0Compare Source
Minor Changes
#18277
2715958Thanks @florian-lefebvre! - Increases the minimum Node.js version to 22.22.0The minimum supported Node.js version is now 22.22.0, the latest Node.js 22 release supported by StackBlitz. This change is in line with Astro's Node.js support policy.
Patch Changes
b7a1bd9]:v8.0.3Compare Source
Patch Changes
6987261Thanks @renovate! - Adds YAML parsing with timestamp and merge key support, and formats YAML errors consistently across Astro, Markdown, MDX, and Markdoc.6987261,62b13ba]:v8.0.2Compare Source
Patch Changes
f4444ebThanks @astro-factory! - Fixes an incompatibility where@astrojs/mdxv8 could be installed withastroversions that bundle an older@astrojs/markdown-satterilacking MDX support. Also improves the error message when the processor is too old to suggest updatingastroitself.3fd16ee,8358d59]:v8.0.1Compare Source
Patch Changes
a548223]:v8.0.0Compare Source
Major Changes
#17262
f8e9458Thanks @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-satteri0.4.0 or later if you usesatteri()@astrojs/markdown-remark7.3.0 or later if you useunified()Patch Changes
#17262
f8e9458Thanks @Princesseuh! - Fixes.mdxfiles still usingmarkdown.processorwhenextendMarkdownConfigisfalse. They now use a clean default processor instead; passmdx({ processor })to choose one explicitly.#17262
f8e9458Thanks @Princesseuh! - Adds a warning when the deprecatedremarkPlugins,rehypePlugins,recmaPluginsandremarkRehypeoptions are ignored because your Markdown processor does not run them. They still apply when your processor isunified(), and were previously dropped silently otherwise.Updated dependencies [
f8e9458,f8e9458]:Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.