Changelog

Astro 7 is out today, and it just works on Netlify on day one. To upgrade, run:

npx @astrojs/upgrade

This will update Astro, the Netlify adapter, and all other official integrations together. You can also check out the official migration guide.

What’s new

Some highlights include:

• Vite 8 — Astro 7 upgrades to Vite 8, bringing faster builds and improved dev tooling.
• Sätteri is now the default markdown processor — Astro’s new native markdown pipeline replaces remark/rehype as the default. If your project uses remark or rehype plugins, you’ll need to install @astrojs/markdown-remark separately to keep them working.
• Advanced routing is stable — Previously behind an experimental flag, advanced routing is now enabled by default. The default entry point has moved from src/app.ts to src/fetch.ts.
• Streaming rendering is stable — The streaming-based rendering engine is now the default, replacing the legacy queued approach.
• Background dev server for AI coding agents — astro dev now detects AI coding environments and runs as a background process automatically. New astro dev stop, astro dev status, and astro dev logs commands let you manage it directly.
• Astro DB is deprecated — The astro db, astro login, astro logout, astro link, and astro init CLI commands have been removed. Switch to a dedicated database client.
• Custom logger is stable — context.logger is now always available in API routes and middleware, with built-in json, node, and console handlers.

Check the full upgrade guide for all the details.

Watch out for the new markdown defaults

If your site uses remark or rehype plugins, you’ll need to take action before upgrading. In Astro 7, the default markdown pipeline is Sätteri — Astro’s own native processor. The remark/rehype pipeline is no longer included by default.

To keep your existing plugins working, install the remark package separately:

npm install @astrojs/markdown-remark

Once installed, your existing markdown.remarkPlugins, markdown.rehypePlugins, and markdown.remarkRehype config options will continue to work as before. If you’re not using any remark or rehype plugins, no changes are needed — Sätteri handles standard Markdown out of the box.

Deploy an Astro 7 site on Netlify

If you want to get started with a new site, start with the Astro on Netlify doc, or just click this button:

You can now preview proposed data changes for your Netlify database with a Git-style diff view, then apply part or all of those changes to a production version of your database.

This update allows you to carefully review proposed changes from across your team and make sure you’re confident about making changes to the production version of your database before going live. Learn more in our docs on Data changes for Netlify Database.

When you provision new users through SAML SSO, you now have more options for assigning a default role.

Before this update, the Developer role was assigned by default. Now you can assign other roles with fewer permissions, such as Reviewers and Internal Builders.

Learn more about your options for provisioning with SAML SSO on Netlify.

React Router 8 was just released and is already supported on Netlify.

The breaking changes are largely limited to these new minimums:

• Node.js 22.22.0+
• React 19.2.7+
• Vite 7+

How to upgrade

To upgrade your existing Netlify project follow the React Router 8 upgrade guide and upgrade the Netlify React Router Vite plugin to v4.0.0+:

npm i @netlify/vite-plugin-react-router@latest

Try it now

To deploy a brand new, React Router 8 application to Netlify, click this button:

What you get

Full framework feature support, serverless and edge functions included, plus full Netlify platform emulation in local dev for you and your agents.

• React Router on Netlify
• @netlify/vite-plugin-react-router release notes

Team Owners on the credit-based Pro plan can now create and assign labels to organize projects across their team, a capability previously limited to Enterprise.

Use labels to group projects by environment, purpose, or team—for example, staging, marketing, or production—then filter and find projects faster from your team’s project list.

Learn more in Organize projects in the Netlify documentation.

You can now use as many environment variables as your Serverless Functions need. The 4KB total size limit on environment variables no longer applies to functions running on the current Netlify Functions runtime.

This limit was a common source of friction. Teams with several API keys, connection strings, or feature flags could quietly bump into the cap and see their functions fail to deploy or run, often with confusing errors. With the limit gone, you no longer have to ration space or work around the ceiling for the configuration your functions legitimately need.

The limit still applies to functions running in Lambda compatibility mode. If your functions are using Lambda compatibility mode and you want to remove the size limit entirely, consider upgrading to the current Netlify Functions runtime.

Learn more about environment variables in Netlify Functions in our documentation.

Netlify is now listed in the Cursor marketplace, so you can connect your AI-assisted coding environment directly to Netlify without leaving your editor.

Whether you’re spinning up a new project or iterating on an existing site, having Netlify available from within Cursor means fewer context switches between building and deploying.

Find it at cursor.com/marketplace/netlify.

Update — June 13, 2026

Anthropic has suspended access to Claude Fable 5. Requests to claude-fable-5 through Netlify AI Gateway will fail until access is restored.

Anthropic’s Claude Fable 5 model is now available through Netlify’s AI Gateway with zero configuration required.

Use the Anthropic SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the Claude Fable 5 model:

import Anthropic from '@anthropic-ai/sdk';

export default async () => {
    const anthropic = new Anthropic();

    const response = await anthropic.messages.create({
        model: 'claude-fable-5',
        max_tokens: 4096,
        messages: [
            {
                role: 'user',
                content: 'How can AI improve my cybersecurity?'
            }
        ]
    });

    return new Response(JSON.stringify(response), {
        headers: { 'Content-Type': 'application/json' }
    });
};

Claude Fable 5 is available for all Function types. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure.

Learn more in the AI Gateway documentation.

Angular v22 was released today and it is supported on Netlify on day one.

To upgrade, follow the Angular upgrade steps and update @netlify/angular-runtime to v4.0.0 or later.

Notable changes

• Minimum Node.js version: Angular v22 requires Node.js 22.12.0 or later. Make sure your Netlify site is configured to use a supported Node.js version.
• allowedHosts config: Angular v21.x (specifically, @angular/ssr) introduced an allowedHosts option in the AngularAppEngine configuration, giving you explicit control over which hosts are permitted to connect. Angular 22 started returning a HTTP 400 for requests with other host headers. @netlify/angular-runtime handles adding the most common URLs for a Netlify deploy to the allowedHosts config automatically allowing developers to use Netlify’s branch and deploy previews without the HTTP 400 error.
• Forwarded headers support withtrustProxyHeaders: A new trustProxyHeaders option lets Angular applications behind a reverse proxy correctly read forwarded headers such as X-Forwarded-For and X-Forwarded-Proto. @netlify/angular-runtime handles adding the required headers automatically.

Learn more:

• Angular v22 Release
• Angular on Netlify
• Angular Runtime