---
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/16/"
last_updated: "2026-07-03T03:06:12.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)

-   [
    
    ## TanStack Start Official Deployment Partner
    
    ](/blog/tanstack-start-netlify-official-deployment-partner/)
    
    March 18, 2025
    
    • Article
    
    ![](/_astro/4c84d8e50b235a1a1dbb78c919a3e8fc3bb9627a-1200x676_Z2dG5bW.webp)
    
    Netlify is now the official deployment partner for TanStack Start, the open-source, type-safe, React framework. Learn about the collaboration, key features, and try our AI chatbot template.
    
    [Permalink to TanStack Start Official Deployment Partner Permalink](/blog/tanstack-start-netlify-official-deployment-partner/)
    
-   [
    
    ## Site claiming webhook support
    
    ](/changelog/site-claiming-webhook-support/)
    
    March 17, 2025
    
    -   [ax](/changelog/tag/ax/)
    
    For Netlify integrators and AI agents deploying to Netlify, the process of “claiming” sites allows an end user to transfer a site into their ownership. It has been a challenge for systems to know when this happens.
    
    Today, Netlify added support for an optional `claim_webhook` field when generating a site claim token. This lets you receive a POST request to a specified webhook URL once a user successfully claims a site.
    
    Why is this useful? Now, your system or AI agents can automatically react when a site changes ownership—whether that’s updating internal records, triggering notifications, adjusting billing, or syncing permissions. The webhook payload includes key details like the site ID and the new owner’s account ID, making it easier to track and integrate site claims into your workflow seamlessly.
    
    Want to learn how to setup site claim flows? Check out [this guide](https://developers.netlify.com/guides/deploying-sites-from-ai-tools/#allowing-users-to-claim-a-site)!
    
    [Permalink to Site claiming webhook support Permalink](/changelog/site-claiming-webhook-support/)
    
-   [
    
    ## Enhanced security with domain DNS verification
    
    ](/changelog/enhanced-security-with-domain-dns-verification/)
    
    March 17, 2025
    
    -   [domains](/changelog/tag/domains/)
    
    ![](https://cdn.sanity.io/images/o0o2tn5x/marketing/b6063731ca54fbc015b4c1c2457d2092e2548902-800x536.png)
    
    We’ve introduced built-in domain DNS verification for subdomain configuration. Previously, customers managed DNS verification themselves—now, it’s seamlessly integrated into the app, making ownership verification easier while strengthening domain protection.
    
    [Permalink to Enhanced security with domain DNS verification Permalink](/changelog/enhanced-security-with-domain-dns-verification/)
    
-   [
    
    ## Apply specific environment variable values to all branches with a prefix
    
    ](/changelog/apply-specific-environment-variables-to-all-branches-with-a-prefix/)
    
    March 6, 2025
    
    -   [workflow](/changelog/tag/workflow/)
    -   [build](/changelog/tag/build/)
    
    ![](https://cdn.sanity.io/images/o0o2tn5x/marketing/8ce5ea01d52303bec8072d4ed7a448508c615b76-914x418.png)
    
    We now support configuring your environment variables to apply a value to groups of branches with a given prefix. Explore the new functionality in Site configuration > Environment variables. When adding a branch value for your environment variable, add a wildcard at the end to apply the value to all branches beginning with the prefix. For example setting the branch name to `release/*` will apply the supplied value to branches named `release/1.2`, `release/alpha-0.0.1`, and so on.
    
    Combine with the ability to [configure your site to deploy branches matching selected prefixes](https://docs.netlify.com/site-deploys/overview/#branch-deploy-controls) to super-charge your branch workflows!
    
    [Permalink to Apply specific environment variable values to all branches with a prefix Permalink](/changelog/apply-specific-environment-variables-to-all-branches-with-a-prefix/)
    
-   [
    
    ## Auth0 extension now available
    
    ](/changelog/auth0-extension-now-available/)
    
    February 28, 2025
    
    -   [extensions](/changelog/tag/extensions/)
    
    ![Auth0 extension](https://cdn.sanity.io/images/o0o2tn5x/production/384cc02b2811900d29c67540d024c88b61e3bc8c-2400x1350.png)
    
    Simplify authentication and authorization for your sites and apps with the [Auth0 extension](https://docs.netlify.com/integrations/auth0/#install-the-extension-and-connect-to-auth0). The Auth0 extension lets you connect your Netlify team and its apps to Auth0 from the Netlify Dashboard.
    
    You can also add authorization to your functions to manage access across multiple services. For an example, check out our docs on creating a function to use Auth0 on the backend.
    
    Learn more [about our Auth0 partnership](https://www.netlify.com/blog/auth0-extension-identity-changes) or [using the Auth0 extension](https://docs.netlify.com/integrations/auth0/).
    
    [Permalink to Auth0 extension now available Permalink](/changelog/auth0-extension-now-available/)
    
-   [
    
    ## Team selection for claimed sites
    
    ](/changelog/team-selection-for-claimed-sites/)
    
    February 26, 2025
    
    -   [ai](/changelog/tag/ai/)
    -   [ax](/changelog/tag/ax/)
    
    ![](https://cdn.sanity.io/images/o0o2tn5x/marketing/cdfe8ecee5771781504c480a2e34b13ce263ca19-2896x1130.png)
    
    When claiming apps created by partner tools or AI code generation tools like Bolt, you’re now able to select which of your Netlify teams to claim the app into, offering greater flexibility for your workflows.
    
    [Permalink to Team selection for claimed sites Permalink](/changelog/team-selection-for-claimed-sites/)
    
-   [
    
    ## Codezero extension now available
    
    ](/blog/secure-local-development-codezero/)
    
    February 21, 2025
    
    • Article
    
    ![](/_astro/b596a7453ede5fe6739bd12506636fe522828198-2400x1351_17bYCE.webp)
    
    Learn how the Codezero extension for Netlify enables secure local development with internal APIs and services through Zero Environment Development, without exposing private infrastructure.
    
    [Permalink to Codezero extension now available Permalink](/blog/secure-local-development-codezero/)
    
-   [
    
    ## New API for partners to deploy fullstack websites on Netlify
    
    ](/changelog/new-api-for-partners-to-deploy-fullstack-websites-on-netlify/)
    
    February 19, 2025
    
    -   [ax](/changelog/tag/ax/)
    -   [ai](/changelog/tag/ai/)
    
    Platforms on Netlify can now deploy fullstack websites on behalf of users - complete with functions, edge functions, extensions, redirects, and more.
    
    Sounds interesting? Get started with this [developer guide](https://developers.netlify.com/guides/deploy-zip-file-to-production-website/).
    
    [Permalink to New API for partners to deploy fullstack websites on Netlify Permalink](/changelog/new-api-for-partners-to-deploy-fullstack-websites-on-netlify/)
    
-   [
    
    ## Set up deploys for all branches with a prefix
    
    ](/changelog/set-up-deploys-for-all-branches-with-a-prefix/)
    
    February 18, 2025
    
    -   [build](/changelog/tag/build/)
    -   [workflow](/changelog/tag/workflow/)
    
    ![Netlify UI settings to deploy all branches with the prefix release](https://cdn.sanity.io/images/o0o2tn5x/marketing/1db6ae1900bb72def6e9413dc6d8a4689a17d990-1209x860.png)
    
    We now support configuring your site to deploy all branches with a specific prefix. Leverage the new functionality by configuring Branch Deploys in Site Configuration > Continuous deployment. Add a wildcard at the end of your prefix to deploy all branches beginning with the given text - for example, enter `release/*` to automatically deploy `release/alpha-1`, `release/v2`, and so on.
    
    [Permalink to Set up deploys for all branches with a prefix Permalink](/changelog/set-up-deploys-for-all-branches-with-a-prefix/)
    

[Previous page](/changelog/page/15) [Next page](/changelog/page/17)