--- title: "Changelog | Netlify" description: "Stay updated with the latest features, fixes, and improvements. Realize the speed, agility and performance of a scalable, composable web architecture with Netlify. Explore the composable web platform now!" source: "https://www.netlify.com/changelog/page/14/" last_updated: "2026-08-31T10:16:59.000Z" --- # Changelog All Tags Agent-runners AI Ai-gateway Angular Astro AX Build CLI Database Design Devtools Domains E-commerce Extensions Forms Framework Functions Logs Next.js Nuxt.js Remix SDK Security Updates Workflow [Subscribe to feed](https://www.netlify.com/changelog/feed.xml) - [ ## Revert agent run in a task ](/changelog/revert-agent-run/) November 6, 2025 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. ![Close-up of Agent Runners product UI showing a drop-down menu and the Revert to this run option](https://cdn.sanity.io/images/o0o2tn5x/marketing/43a539ac8dce225fb7f3dcf7f99666c8bf5a3fa4-748x496.png) 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](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). [Permalink to Revert agent run in a task Permalink](/changelog/revert-agent-run/) - [ ## Deletion improvements with Netlify Blobs ](/changelog/blobs-ui-improve/) November 6, 2025 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](https://docs.netlify.com/build/data-and-storage/netlify-blobs/#api-reference). ### 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](https://docs.netlify.com/build/data-and-storage/netlify-blobs). [Permalink to Deletion improvements with Netlify Blobs Permalink](/changelog/blobs-ui-improve/) - [ ## Preview Server restart for cross-functional collaborators ](/changelog/preview-server-restart-status-page/) November 6, 2025 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. ![Preview Server status page with a restart button](https://cdn.sanity.io/images/o0o2tn5x/marketing/5228dbfa01a7988840ffb3c5ca23078373c2518b-2244x1276.png) Learn more about Preview Servers in our [docs](https://docs.netlify.com/manage/preview-servers/overview/). [Permalink to Preview Server restart for cross-functional collaborators Permalink](/changelog/preview-server-restart-status-page/) - [ ## AI inference usage graphs ](/changelog/ai-inference-usage-graphs/) October 31, 2025 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](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/monitor-usage-for-credit-based-plans/#ai-inference-usage) 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. [Permalink to AI inference usage graphs Permalink](/changelog/ai-inference-usage-graphs/) - [ ## Buy credit packs on demand ](/changelog/buy-credit-packs/) October 30, 2025 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. Plan Credits per pack Price Personal 500 $5 USD Credit-based Pro 1,500 $10 USD 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](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/buy-add-on-credits/) in our documentation. [Permalink to Buy credit packs on demand Permalink](/changelog/buy-credit-packs/) - [ ## React Router 7 middleware now supported ](/changelog/react-router-7-middleware-now-supported/) October 24, 2025 - [framework](/changelog/tag/framework/) - [remix](/changelog/tag/remix/) React Router 7 [recently launched its long-awaited middleware feature](https://remix.run/blog/middleware), 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](https://reactrouter.com/how-to/middleware) - [Create a new React Router 7 project with our updated template](https://github.com/netlify/react-router-template/) - [Read the Netlify React Router plugin docs](https://github.com/netlify/remix-compute/tree/main/packages/vite-plugin-react-router#react-router-adapter-for-netlify) for more on loader/action context and to access type-safe [Netlify context](https://docs.netlify.com/build/functions/api/#netlify-specific-context-object) in middleware [Permalink to React Router 7 middleware now supported Permalink](/changelog/react-router-7-middleware-now-supported/) - [ ## Skew protection now available ](/changelog/skew-protection/) October 23, 2025 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](https://www.netlify.com/blog/introducing-netlify-skew-protection/). ### Next steps - [Set up skew protection](https://docs.netlify.com/deploy/deploy-overview/#skew-protection) for your framework - [Ensure your framework can support skew protection](https://docs.netlify.com/build/frameworks/frameworks-api/#netlifyv1skew-protectionjson) with Netlify using our Frameworks API [Permalink to Skew protection now available Permalink](/changelog/skew-protection/) - [ ## Next.js 16 is ready to deploy on Netlify ](/changelog/next-js-16-deploy-on-netlify/) October 21, 2025 - [framework](/changelog/tag/framework/) - [next.js](/changelog/tag/next-js/) The [Next.js 16 release](https://nextjs.org/blog/next-16) is here and Netlify is ready. Deploy the latest version, including Turbopack, React Compiler, and enhanced caching APIs, with zero configuration. - Turbopack (stable): Up to 10× faster Fast Refresh and 2-5× faster builds - React Compiler (stable): Automatic memoization for smoother re-renders - Improved caching APIs: `revalidateTag` with `cacheLife` profile argument for Stale-While-Revalidate behavior and Server Actions-only `updateTag` to immediately refresh cached data **Template update** We’ve updated the [Next Platform Starter](https://github.com/netlify-templates/next-platform-starter) to v16, showcasing Turbopack and the new caching APIs in action. In our tests, the project saw a 2.8× faster `next build` with Turbopack. **Upgrading to v16 on Netlify** If you’re upgrading from v15, no Netlify configuration changes are required. Teams that have opted out of automatic updates for Netlify’s OpenNext adapter will need to [manually upgrade](https://docs.netlify.com/build/frameworks/framework-setup-guides/nextjs/legacy-runtime/upgrading-or-reverting-adapter/#upgrade-to-the-latest-adapter), or simply opt back in to receive automatic updates. **Resources** - [Deploy the demo](https://github.com/netlify-templates/next-platform-starter) - [Read the Next.js 16 release](https://nextjs.org/blog/next-16) - [View Next.js on Netlify docs](https://docs.netlify.com/build/frameworks/framework-setup-guides/nextjs/overview/) [Permalink to Next.js 16 is ready to deploy on Netlify Permalink](/changelog/next-js-16-deploy-on-netlify/) - [ ## Enforce Git-based workflows for production deploys ](/changelog/enforce-git-based-workflows/) October 21, 2025 Now you can require all production deploys to go through a Git-based workflow. When enabled in your project settings, this setting prevents: - Accidental production publishes from the Netlify CLI, MCP server, or API - Promoting Deploy Previews or branch deploys to production through the Netlify UI This ensures that both team members and AI agents follow your preferred Git-based workflow before your project’s code reaches production. Learn more in our [Git workflow docs](https://docs.netlify.com/build/git-workflows/overview/#enforce-git-based-deployments). [Permalink to Enforce Git-based workflows for production deploys Permalink](/changelog/enforce-git-based-workflows/) [Previous page](/changelog/page/13) [Next page](/changelog/page/15)