What's new in Astro - May 2026
Summary
Astro's May 2026 roundup covers two minor releases (6.3 and 6.4), the ongoing Astro 7 alpha with Vite 8 and Rust compiler support, TinaCMS defaulting to Astro, and a deep bench of community integrations and migration stories.
Astro Blog published its May 2026 monthly roundup, packaging together release notes, ecosystem updates, and community content into one post. The highlights worth your time are the two minor releases, the Astro 7 alpha status, and a notable CMS default shift.
What’s actually new
Astro 6.3 introduced experimental advanced routing with Hono support, image redirect handling, and what they call “resilient island hydration.” Astro 6.4 followed with a pluggable Markdown pipeline, a new Rust-based Markdown processor, and Cloudflare-specific helpers for advanced routing. Both are minor releases, so they should be non-breaking upgrades from 6.x.
The Astro 7 alpha preview continues, with Vite 8 support and the stable Rust compiler listed as headline features. TinaCMS now defaults to Astro as its framework target, which is a meaningful signal for content-heavy teams evaluating CMS options. ImageKit also shipped an official Astro integration for image/video optimization and uploading. On the Starlight side, version 0.39 brings more flexible autogenerated sidebars and improved multilingual docs support.
The community content section is unusually rich this month. Several migration write-ups stand out: one documenting a Next.js site that shipped 900 KB of JavaScript and what replaced it, another covering a React-to-native-web migration that cut 100 KB, and a practical walkthrough of upgrading from Astro 5 to Astro 6. There’s also a case study on Express’s site redesign using Astro.
What it means for your config
Astro 6.3’s Hono-based routing is marked experimental, so expect it behind a feature flag in your astro.config.* file. If you’re on Cloudflare, 6.4’s new helpers and routing options likely mean additions to your config — check the release notes for specifics before adopting.
The Rust-based Markdown processor in 6.4 is the one to watch for config impact. If you’ve customized remark/rehype plugins in your Astro config, a different processing backend could change how those plugins are loaded or whether they’re compatible. The announcement doesn’t detail the exact config surface for opting in or out, so test your existing Markdown pipeline before upgrading.
For the Astro 7 alpha: Vite 8 support will eventually ripple into vite config blocks inside your Astro config. Don’t adopt the alpha in production, but if you maintain custom Vite plugins, now is the time to check Vite 8 compatibility upstream. The stable Rust compiler mention suggests the current experimental compiler flag may become the default — another reason to start testing.
The new @scale.digital/astro-bun adapter is worth noting if you’re targeting Bun as a runtime. It handles SSR, hybrid, and static modes via Bun.serve, which means a different adapter value in your config compared to the Node or Deno adapters.
Recommended next step
If you’re on Astro 6.x, upgrading to 6.4 is the practical move — minor releases are additive. Read the 6.3 and 6.4 changelogs before bumping, particularly if you rely on custom Markdown processing or deploy to Cloudflare. If you’re starting a new project or re-evaluating your Astro setup, you can scaffold a fresh configuration with our tool: Generate an Astro config.
Read the full announcement on Astro Blog → What’s new in Astro - May 2026
Need a Astro config file?
Generate the latest config in seconds with ConfigDeck.