Skip to content

v2.6.0

Latest

Choose a tag to compare

@hansmartensdev hansmartensdev released this 03 Sep 20:00
· 41 commits to main since this release
d356f0e

An upgrade release: Astro 7.2.0 → 7.3.1 and @astrojs/mdx 7.0.3 → 8.0.0. Nothing a site built on this theme depends on has changed, so updating needs no changes — unless you have configured a Markdown processor yourself, which is the one case below.

Changed

  • Astro 7.3.1. 7.3.1 rather than 7.3.0: 7.3.0 carried an error that stopped projects using astro:assets from starting or building, and this theme uses astro:assets in four places. What 7.3 adds is opt-in, or for authors of custom services — an --ignore-lock flag for astro preview so several preview servers can run at once, and a logger argument for custom image services and cache providers so their messages go through the configured logger instead of straight to the console. Two of its fixes reach this theme: Astro's remaining internal warnings and errors now go through the configured logger, and build performance improves for sites with many pages drawn from many modules.
  • @astrojs/mdx 8.0.0. The major moves MDX file processing into the Markdown processors. If you have not explicitly configured a Markdown processor, you need to do nothing — the theme ships without one, so it falls through to Sätteri, and the @astrojs/markdown-satteri 0.4.0 it needs arrives with Astro 7.3.1. If your fork sets processor: unified(), you need @astrojs/markdown-remark 7.3.0 or later.
  • 117 fewer packages. @astrojs/mdx no longer carries its own processing chain. The lockfile drops from 1420 resolutions to 1297, @astrojs/markdown-remark leaves the tree entirely — it was there only because mdx 7.0.3 pinned it — and @astrojs/markdown-satteri collapses from two copies to one.

If you turn i18n on with a fallback, 7.3 fixes a route bug worth knowing about. A page such as src/pages/en/enterprise.astro under fallback: { es: 'en' } used to generate /es/esterprise, because the locale code was rewritten wherever it appeared rather than only at the front. The theme ships i18n without a fallback, so it was never affected — a site that added one was.

Verified by rendering the whole site on both versions and comparing all 90 pages: every one is identical apart from Astro's per-build random component ids. Lighthouse over three runs of each build holds performance, accessibility, best practices and SEO at 100, with CLS 0 and TBT 0.

Node.js 22.12.0+ is still the floor.

Full changelog: https://github.com/hansmartensdev/Astro-Rocket/blob/main/CHANGELOG.md