Astro 7.4.13
Remember when Astro was pitched as a static site generator with islands and little else? The 7.x line has spent its energy on the parts that surround the page: a dev toolbar that audits accessibility, a font pipeline, i18n routing, and server output that scales to real content collections. Astro 7.4.13, published November 18, 2026, is a patch release, but it lands squarely in that maintenance work. Nine fixes, one dependency bump, no new APIs.
The Audit Stops Seeing Ghosts
The dev toolbar's a11y-missing-content audit used to flag anchors and headings that were hidden with visibility: hidden or nested inside an aria-hidden="true" subtree. Those elements are not exposed to assistive technology, so reporting them was noise. The audit now skips them. This is the kind of fix that does not show up in a marketing post, but it makes the toolbar trustworthy for teams that actually run its checks before shipping.
Server Bundles Get Leaner
When no server-rendered route called render() from astro:content, server bundles could still include every renderable content collection entry. That is wasted bytes in the deploy artifact and wasted memory at runtime. 7.4.13 fixes the inclusion so unused collections stay out of the bundle. Content-heavy sites with a small set of rendered routes should see the difference in build output size.
Routing and Locale Edges
i18n.fallback no longer fails with i18nNoLocaleFoundInPath when the fallback target is a locale defined with a custom path. Projects that map locales to non-standard URL prefixes were the ones hitting this, and the fix closes a gap that made fallback routing unusable for them.
Cross-origin requests from an origin allowed by security.allowedDomains also work again when the entry uses a default port, for example { hostname: 'staging.myapp.com', protocol: 'https', port: '443' }. BaseApp.validateForwardedHost() now applies the same allowed-domain rules as the rest of Astro.
Fonts, Startup, and the Dev Toolbar
<Font preload>now emits preload links when a requested weight range such as"400 700"sits inside a variable font's wider range such as"400 900".- Every
astrocommand starts faster in projects that do not configure fonts, because font resolution dependencies load only when fonts are used. - The dev toolbar no longer refetches
loading="lazy"images to measure them. That stops animated SVGs from freezing in Safari and stops images from downloading before the page intended. astro dev status,astro dev logs, and theastro previewequivalents no longer treat a server started withASTRO_DEV_BACKGROUND=0orASTRO_PREVIEW_BACKGROUND=0as a background server.
Hydration and Housekeeping
Framework components that receive sparse array props now hydrate correctly, with holes serialized as undefined. That closes a mismatch between server serialization and client expectation. The release also bumps @astrojs/runtime to 0.1.2.
What's Next
Seven of the nine fixes were merged by the astro-factory automation account, with community pull requests from KoenRijpstra, NetBr3ak, Marve10s, and hood filling out the rest. That mix says a lot about where the project is: the core team automates the long tail of patch work while outside contributors handle specific integrations. For users, the takeaway is simple. Update with npm install astro@latest or your package manager's equivalent, then run a build to confirm the leaner server bundle. If you use the dev toolbar's accessibility audits, open a page with hidden sections and watch the false positives disappear.