Astro released version 6.0 on March 10 with built-in APIs for fonts and Content Security Policy, live content collections, and a substantial development-server refactor. The release announcement says the new pipeline uses Vite’s Environment API so adapters can run a production-like runtime during local development.
More site concerns move into the framework
The Fonts API gives projects a framework-level path for declaring and optimizing typefaces. The CSP API can generate policy information alongside rendered output, reducing the manual coordination between emitted scripts, styles, and security headers. Live Content Collections add request-time fetching for externally hosted material. Astro 5’s Content Layer could already load APIs and CMS sources during a build, but content changes required another build; Astro 6 can fetch live entries on each request.
The deeper architectural change is shared code between development and build paths. For adapters that implement a custom runtime environment, local execution can better resemble the eventual deployment target. That should help expose differences in globals, request handling, and platform bindings before a deploy, although parity still depends on each adapter’s implementation.
Upgrade around boundaries, not just pages
A safe migration should inventory integrations and custom Vite plugins before focusing on page output. Exercise server-rendered routes, content loaders, redirects, and error paths in both development and a production build. CSP adoption deserves its own observation phase: collect violations, identify inline code and third-party origins, and tighten the policy after legitimate resources are accounted for.
Astro also labels its Rust compiler, queued rendering, and route caching as experimental in this release. Those options can be useful for representative benchmarks, but teams should keep them behind reversible configuration and avoid making a migration depend on preview behavior. Start with the stable framework upgrade, compare generated HTML and asset URLs, then opt into experiments one at a time with a known baseline.
See the original announcement for availability and release details.