roadmap

Accepted Date: Reference Issues/Discussions: withastro/roadmap#1064 Author: @Ely-S Champion(s): @bholmesdev Implementation PR: Summary Add support for HTTP GET requests in Astro Actions, enabling browser and CDN caching for data-fetching actions. Background & Motivation Astro Actions currently support only POST requests. POST is not cacheable, which means every action call hits the server, even for pure data reads. While it is currently possible to fetch JSON and send query parameters over GET, doing so gives up the type safety, validation, and error handling that Actions provide. Adding GET support would make Actions viable for read-heavy use cases (like search) where CDN caching is necessary. Goals Allow individual Actions to opt into the GET HTTP method Enable standard HTTP caching to be used for GET Actions Preserve type-safe input validation Non-Goals Changing the default behavior of POST Actions Supporting request bodies or file uploads in GET Actions Caching and cache management

Accepted Date: 2026-07-02 Reference Issues/Discussions: https://github.com/withastro/roadmap/discussions/1096 Author: @matthewp Champion(s): @matthewp Implementation PR: Summary Add support for incremental static builds in Astro, allowing unchanged static pages to be skipped between builds when their template dependencies and user-provided data cache keys are unchanged. Background & Motivation Large static sites often spend most of their build time regenerating pages whose output has not changed. This is especially painful for documentation sites using a small number of dynamic routes, such as a single route that renders thousands of content pages. Astro already has some persistent build caches in , such as content layer and image optimization data. However, Astro currently regenerates all prerendered pages on every build, even when a page's source template, layout, components, and data are unchanged. Goals Skip regenerating static pages whose route dependencies and path-specific data have not changed. Provide a stable API for dynamic routes to declare the cache key for each generated path. Non-Goals Changing build concurrency behavior. This is orthogonal to the existing option. Example Dynamic routes can return a for each path from . The should change whenever the data used to render that specific path changes. For content collections, is a natural cache key because it changes when the content entry changes. The exact cache key strategy is project-specific. A site should include every input that affects page output, such as content digests, CMS timestamps, or route metadata.

If you are using Astro at your company or organization, please share the URL here! https://nordvpn.org https://firebase.blog https://tech.trivago.com https://www.thinkmill.com.au https://designcember.com https://dayofthedead.holiday https://openmoji.org https://unicorn-utterances.com https://miduconf.com https://midufest.com https://theguardian.engineering https://credtrace.in/ See the full showcase → _Originally posted by @FredKSchott in https://github.com/withastro/roadmap/discussions/521_