---
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/12/"
last_updated: "2026-08-05T14:35:11.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)

-   [
    
    ## Add DNS records across teams in your organization
    
    ](/changelog/2025-11-17-cross-team-dns-records/)
    
    November 17, 2025
    
    -   [domains](/changelog/tag/domains/)
    
    If you have a Netlify Organization, you can now add a DNS record that has a DNS zone from a different team in your Netlify organization.
    
    Previously, DNS records could only be added to DNS zones in the Netlify team that managed them, limiting those with Netlify Organizations. With this new change it is easier than ever for your organization to share DNS zones across Netlify Teams and projects.
    
    Learn more about [managing DNS records](https://docs.netlify.com/domains-https/netlify-dns/dns-records/) in the Netlify documentation.
    
    [Permalink to Add DNS records across teams in your organization Permalink](/changelog/2025-11-17-cross-team-dns-records/)
    
-   [
    
    ## Skew protection available for CLI workflows
    
    ](/changelog/2025-11-13-skew-protection-cli-deploys/)
    
    November 14, 2025
    
    -   [cli announcement](/changelog/tag/cli-announcement/)
    
    Skew protection is now available for deploys triggered from the CLI starting with the Netlify CLI version 23.11.0 and above. Previously, skew protection did not work with CLI workflows.
    
    To upgrade your Netlify CLI version:
    
    ```
    npm update -g netlify-cli
    ```
    
    Note that if you use `npx` when you run your Netlify CLI commands, you will always use the latest Netlify CLI version.
    
    Learn more about the benefits of skew protection, including more stable user experiences and preventing server-client version mismatch errors in our [docs](https://docs.netlify.com/deploy/deploy-overview/#skew-protection).
    
    [Permalink to Skew protection available for CLI workflows Permalink](/changelog/2025-11-13-skew-protection-cli-deploys/)
    
-   [
    
    ## New top-level domains available
    
    ](/changelog/2025-11-13-expanded-domain-tld-support/)
    
    November 13, 2025
    
    -   [domains](/changelog/tag/domains/)
    
    Now you can purchase domains with the following top-level domains (TLDs) for even more flexibility when buying and registering a domain through Netlify:
    
    -   `.place`
    -   `.be`
    -   `.pl`
    -   `.dk`
    -   `.co.uk`
    
    For help buying a new domain, check out our docs on [registering and buying a domain](https://docs.netlify.com/manage/domains/configure-domains/register-and-buy-a-domain/).
    
    For even more help setting up a domain, check out our [domains setup wizard](https://docs.netlify.com/manage/domains/get-started-with-domains/#domains-and-dns-navigator).
    
    [Permalink to New top-level domains available Permalink](/changelog/2025-11-13-expanded-domain-tld-support/)
    
-   [
    
    ## GPT-5.1 model now available in AI Gateway
    
    ](/changelog/gpt-5-1-ai-gateway/)
    
    November 13, 2025
    
    -   [ai gateway](/changelog/tag/ai-gateway/)
    
    OpenAI’s latest GPT-5.1 model (`gpt-5.1`) is now available through Netlify’s AI Gateway. This model brings enhanced performance and efficiency with no additional setup required.
    
    Use the OpenAI SDK directly in your Netlify Functions without managing API keys. The AI Gateway handles authentication, rate limiting, and caching automatically. Here’s an example using the GPT-5.1 model:
    
    ```
    import { OpenAI } from "openai";
    export default async () => {  const openai = new OpenAI();
      const response = await openai.chat.completions.create({    model: "gpt-5.1",    messages: [      {        role: "user",        content: "Compare GPT-5.1's improvements over GPT-5 Pro"      }    ]  });
      return new Response(JSON.stringify(response), {    headers: { "Content-Type": "application/json" }  });};
    ```
    
    The GPT-5.1 model works seamlessly across Edge Functions, Background Functions, and Scheduled Functions. You also get access to Netlify’s advanced caching primitives and built-in rate limiting.
    
    Learn more in the [AI Gateway documentation](https://docs.netlify.com/build/ai-gateway/overview/).
    
    [Permalink to GPT-5.1 model now available in AI Gateway Permalink](/changelog/gpt-5-1-ai-gateway/)
    
-   [
    
    ## React Router 7 apps can now be deployed to Edge Functions
    
    ](/changelog/react-router-7-apps-can-now-be-deployed-to-edge-functions/)
    
    November 10, 2025
    
    -   [framework](/changelog/tag/framework/)
    -   [remix](/changelog/tag/remix/)
    
    React Router 7 apps on Netlify are deployed to Serverless Functions by default. Now, you can choose to deploy your app to [Edge Functions](https://docs.netlify.com/build/edge-functions/overview/) instead, bringing your page renders, data loaders, and actions closer to your users while lowering cold start times.
    
    ## How to use it
    
    1.  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
    ```
    
    2.  Update to the latest version of the Netlify React Router plugin:
    
    ```
    npm install @netlify/vite-plugin-react-router@latest
    ```
    
    3.  Enable the new `edge` option in your `vite.config.ts` (or `.js`):
    
    ```
    export default defineConfig({  plugins: [    reactRouter(),    netlifyReactRouter({ edge: true }), // <- deploy to Edge Functions    netlify(),  ],})
    ```
    
    4.  Finally, create a file at `app/entry.server.tsx` (or `.jsx`) containing this single line:
    
    ```
    export { default } from 'virtual:netlify-server-entry'
    ```
    
    On your next deploy, page renders, loaders, and actions will all run in an edge function.
    
    ## When to use it
    
    _Choose Edge Functions when:_
    
    -   You need **minimal latency** for your **globally distributed users** (edge functions run on the node closest to the user)
    -   You need to **optimize cold starts** (initialization is faster with the slim Deno edge runtime)
    -   Your data loaders and actions make requests to **databases and APIs that are also globally distributed**, or none at all
    -   You need to support very large request or response bodies (Serverless Functions have a 6 MB limit)
    
    _Choose Serverless Functions when:_
    
    -   Your data loaders and actions make requests to **databases or APIs that are centrally located** (canceling out much of the benefit of edge compute)
    -   Your server-side code is **CPU-intensive** (Serverless Functions run on more powerful machines)
    -   You need **longer execution times** (Functions allow up to 30s clock time, while Edge Functions are limited to 50ms CPU time)
    -   You cannot use Edge Functions due to their [runtime constraints](https://docs.netlify.com/build/edge-functions/api/#runtime-environment) or [limitations](https://docs.netlify.com/build/edge-functions/limits/#feature-limitations)
    
    ## Next steps
    
    -   Create a new React Router 7 project with [our 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 details on deploying to the edge
    
    [Permalink to React Router 7 apps can now be deployed to Edge Functions Permalink](/changelog/react-router-7-apps-can-now-be-deployed-to-edge-functions/)
    
-   [
    
    ## Git SHA exposed for triggered deploys
    
    ](/changelog/exposing-a-git-sha-for-triggered-deploys/)
    
    November 7, 2025
    
    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.
    
    ![Example of where you see the Git SHA in Netlify UI](https://cdn.sanity.io/images/o0o2tn5x/marketing/97fc33f54e16dfbc3447ec8017ed2b1392b55271-726x436.png)
    
    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.
    
    [Permalink to Git SHA exposed for triggered deploys Permalink](/changelog/exposing-a-git-sha-for-triggered-deploys/)
    
-   [
    
    ## Test scheduled functions in Netlify dashboard
    
    ](/changelog/test-scheduled-functions-in-netlify-ui/)
    
    November 6, 2025
    
    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.
    
    ![Netlify project dashboard showing a "Run now" button](https://cdn.sanity.io/images/o0o2tn5x/marketing/daada9a160cab9f42970c0b85c5754e09eddd214-2794x1390.png)
    
    [Permalink to Test scheduled functions in Netlify dashboard Permalink](/changelog/test-scheduled-functions-in-netlify-ui/)
    
-   [
    
    ## 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/)
    

[Previous page](/changelog/page/11) [Next page](/changelog/page/13)