# Astro astro@7.0.0 — Release & Upgrade Intelligence
- **Product:** Astro (https://astro.build)
- **Version:** astro@7.0.0
- **Released:** Jun 22, 2026
- **Impact Score:** 5/10
- **Breaking Changes:** Not verified
- **Canonical Analysis:** https://changelogs.us/astro/updates/astro-7.0.0/

## Executive Summary (TL;DR)
Astro astro@7.0.0. Source highlight: Upgrade to Vite v8

## New Features
- Adds background dev server management for AI coding agents.
- Adds a `subset` field to the `FontData` type exposed via `fontData` from `astro:assets`. When using multiple font subsets (e.g., `subsets: ["latin", "korean"]`), each font data entry now includes the subset name, making it possible to distinguish between font entries for different subsets that share the same weight and style.
- The custom logger feature introduced behind a flag in v6.2.0 is no longer experimental and is available for general use.
- The node polling feature has been removed because it doesn't yield concrete savings.

## Bug Fixes
- Removes `state.provide()`, `state.resolve()`, `state.finalizeAll()`, and `App.Providers` from the public advanced routing API. These context provider extension points are now internal-only. If you were using them in an integration, use `locals` to share per-request state instead.
- Harden the limits on the number of decoding on the URL.
- Improves the warning when accessing `Astro.session` without session storage configured. The `session` property is now always defined on the context object, and accessing it without configuration logs a helpful message instead of silently returning `undefined`.
- Adds shared helper utilities for CDN cache provider authors for route caching
- Improves build performance by removing an unfiltered transform hook from the `astro:head-metadata-build` plugin. Head propagation modules are now identified by their module ID (`?astroPropagatedAssets`) instead of scanning every module's source code.
- Fixes a bug where the advanced routing `astro/hono` / `astro/fetch` `pages()` handler returned the host framework's default `Internal Server Error` response instead of rendering the custom `500.astro` page when a page threw during render. Unmatched requests with a prerendered (or absent) custom 404 page now render the 404 error page instead of failing the same way.

## Upgrade Command
```bash
npm install --save-exact astro@7.0.0
```