Changelog

Now when you trigger a deploy from the Netlify UI or with a build hook, you’ll find a linkable Git commit SHA in the Netlify UI that you can open for more information about the changes you deployed.

This allows you to better troubleshoot and understand the code you deployed.

When using the Netlify API, you’ll also find a new commit_ref response parameter that shows your Git commit SHA.

Now you can manually test scheduled functions through your Netlify dashboard.

You can even manually invoke scheduled functions in different contexts where they may not be invoked automatically, such as Deploy Previews.

Now you can revert to a previous agent run session within an Agent Runners task. This allows you to quickly dismiss changes from a new agent run session within the same task.

For example, if your first prompt included instructions for setting up Netlify forms and your second prompt added a phone number field, now you can quickly revert to your first agent run’s set of changes.

To revert to a previous agent run session, the following must be true:

• For a given task, you have more than one agent run session (or we can say you have extended the task with a follow-up prompt)
• No agent runs are still in progress for the task

Learn more about using Agent Runners.

You now have more options for deleting an entire store or individual entries in Netlify blobs. You can also group blob stores by project or deploy in your Netlify dashboard.

Delete with Blobs API

Using the Blobs API, you can use the new deleteAll method:

import { getStore } from "@netlify/blobs";

const uploads = getStore("file-uploads");

const { deletedBlobs } = await uploads.deleteAll();

console.log(`${ deletedBlobs } blobs were 💥`);

Learn more in the Blobs API docs.

Delete and manage in dashboard

From your Netilfy dashboard, you can do the following:

• delete individual entries
• delete entire stores in one go

You can also group blob stores by project or deploy.

Learn more in our Blobs docs.

Our new Preview Server status page lets people in the Publisher and Content Editor roles restart the server without help from other team members, such as Developers.

This allows teams working across time zones or making frequent changes to use the Preview Server seamlessly.

When a Preview Server is stopped, you’ll find a status page with a Restart button, and you’ll be redirected to the preview once the restart is complete.

Learn more about Preview Servers in our docs.

Now you can better understand how your projects are consuming credits when using Netlify’s AI Gateway and/or Agent Runners

For all credit-based plans, you can now find an AI inference usage graph in your Usage and Billing dashboard.

AI inference is a usage meter that measures the costs of using AI models and agents on Netlify. This usage meter calculates costs for using Agent Runners and AI Gateway.

The new AI inference usage graph shows AI provider requests and tokens used across your Netlify team’s projects over time.

To check it out, go to Usage and Billing > Account usage insights > AI inference.

You can also review the docs to learn more about monitoring usage and costs for AI features.

Note that Netlify’s AI Gateway and Agent Runners are only available for credit-based plans.

Starting today, you can purchase credit packs directly from your Netlify Dashboard.

Only Team Owners with a credit-based Personal or Pro plan can purchase credit packs.

This gives you more control over your spending and allows you to add credits on demand without setting up auto-recharge.

Previously, you had to configure auto-recharge to purchase additional credits. Auto-recharge is still available, but you now have the flexibility to buy credit packs at any time.

For example, if you’re building new functionality using Agent Runners, you can purchase credit packs to cover the additional usage without enabling auto-recharge. You may still want to use auto-recharge, but now you have the flexibility to manage spending and credit usage in more ways.

Learn more about buying credit packs in our documentation.

React Router 7 recently launched its long-awaited middleware feature, stable since v7.9.0.

Middleware is now fully supported on Netlify.

How to use it

Ensure you’re on version 7.9.0 or later of React Router:

npm install react-router@latest @react-router/node@latest @react-router/dev@latest

Upgrade to version 2 of the Netlify React Router plugin:

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

After that, middleware works out of the box.

Next steps

• Check out the full React Router middleware docs
• Create a new React Router 7 project with our updated template
• Read the Netlify React Router plugin docs for more on loader/action context and to access type-safe Netlify context in middleware

We’ve released skew protection for all plans starting with these frameworks:

• Astro 5.15.0+
• Next.js

This feature prevents version mismatch errors when users interact with your site during a deployment.

What it fixes

When you deploy a new version of your site, users with an open browser tab may still be running the old version. If they navigate to a new page or trigger a request, the browser expects a previous version of your application, but the server returns the new version.

This version skew causes:

• Broken assets and 404 errors
• JavaScript errors
• Degraded user experience

How it works

Skew protection pins each user session to a specific Netlify deploy, ensuring the browser and server stay synchronized throughout that session.

To learn how it works more in-depth, check out our skew protection blog post.

Next steps

• Set up skew protection for your framework
• Ensure your framework can support skew protection with Netlify using our Frameworks API