Changelog
Version 1.6.1
Fixed
-
Starlight plugins that extend the Markdown processor no longer stop working. Astro 7 renders Markdown with the Sätteri processor and hands every integration the same live processor object. Plugins extend the pipeline by changing that object. The theme replaced it with a
unified()processor from twoastro:config:setuphooks, which run after Starlight has already set up its plugins, so everything those plugins had registered was thrown away.The visible effect was
starlight-links-validator0.25 or newer: it validated zero links on every build and still printed “All internal links are valid”, so broken internal links passed unnoticed. Any plugin that configures itself against the Sätteri processor was affected the same way.defineNorthwesternConfig()now setsmarkdown.processortounified()whileastro.config.*is evaluated, beforestarlight()is created. No plugin ever sees Sätteri, and the theme only extends the processor it is given instead of replacing it. A processor you configure yourself is left alone. -
Mermaid no longer swaps the Markdown processor either.
astro-mermaid2.1 supports Sätteri on its own.