--- 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://preview--www.netlify.app/changelog/" last_updated: "2026-10-29T09:00:05.000Z" --- # Changelog All Tags Agent-runners AI Ai-gateway Angular Astro AX Billing Build CLI Database Design Devtools Domains E-commerce Edge-functions Extensions Forms Framework Functions Logs Next.js Nuxt.js Remix SDK Security Sveltekit Updates Workflow [Subscribe to feed](https://www.netlify.com/changelog/feed.xml) - [ ## GPT-6.1 Terra now available in AI Gateway and Agent Runners ](/changelog/gpt-6-1-terra-ai-gateway-agent-runners/) October 26, 2026 - [ai gateway](/changelog/tag/ai-gateway/) - [agent runners](/changelog/tag/agent-runners/) OpenAI’s GPT-6.1 Terra model is now available through Netlify’s AI Gateway and Agent Runners with zero configuration required. Use the OpenAI SDK directly in your Netlify Functions without managing API keys or authentication. AI Gateway handles everything automatically. Here’s an example using GPT-6.1 Terra with the Responses API: ``` import OpenAI from 'openai'; export default async () => { const openai = new OpenAI(); const response = await openai.responses.create({ model: 'gpt-6.1-terra', input: 'Give a concise explanation of how AI works.', }); return Response.json(response);}; ``` GPT-6.1 Terra is also available across Scheduled Functions, Background Functions, and Edge Functions. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure. Learn more in the [AI Gateway documentation](https://docs.netlify.com/build/ai-gateway/overview/) and [Agent Runners documentation](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). [Permalink to GPT-6.1 Terra now available in AI Gateway and Agent Runners Permalink](/changelog/gpt-6-1-terra-ai-gateway-agent-runners/) - [ ## Build and deploy to Netlify from Grok ](/changelog/2026-10-23-netlify-connector-for-grok/) October 23, 2026 - [ai](/changelog/tag/ai/) - [workflow](/changelog/tag/workflow/) You can now connect Netlify to [Grok](https://grok.com/) with the Netlify connector, so your Grok agent can answer questions about your projects, update supported project settings, and deploy to Netlify through conversation. The connector gives Grok up-to-date context for building and deploying to Netlify, and it works across Grok Bot, Grok CLI, and [grok.com](https://grok.com/). You don’t need to call the connector by name. Describe what you want, and when the task needs Netlify access, Grok uses the connector for you. For example, you can ask Grok to: - “Deploy this project to Netlify.” - “What’s the status of my latest deploy?” - “Show me my Netlify projects.” - “Build me a website for my restaurant and deploy it to Netlify.” To get started, open [Connectors](https://grok.com/connectors) in Grok, search for **Netlify**, then select **Add** and follow the setup prompts. You’ll need a Grok account with access to connectors and a [Netlify account](https://app.netlify.com/signup). Learn more in our guide to [setting up Grok for Netlify](https://docs.netlify.com/build/build-with-ai/agent-setup-guides/set-up-grok-for-netlify/). [Permalink to Build and deploy to Netlify from Grok Permalink](/changelog/2026-10-23-netlify-connector-for-grok/) - [ ## MiniMax M3.1 Flash now available in AI Gateway and Agent Runners ](/changelog/minimax-m3-1-flash-ai-gateway-agent-runners/) October 23, 2026 - [ai gateway](/changelog/tag/ai-gateway/) - [agent runners](/changelog/tag/agent-runners/) MiniMax’s M3.1 Flash model is now available through Netlify’s AI Gateway and Agent Runners with zero configuration required. Use the OpenRouter SDK directly in your Netlify Functions without managing API keys or authentication. AI Gateway handles everything automatically. Here’s an example using MiniMax M3.1 Flash: ``` import { OpenRouter } from '@openrouter/sdk'; export default async () => { const client = new OpenRouter(); const response = await client.chat.send({ chatRequest: { model: 'minimax/minimax-m3.1-flash', messages: [{ role: 'user', content: 'How can AI improve my coding?' }], maxTokens: 400, }, }); return Response.json(response);}; ``` MiniMax M3.1 Flash is also available across Scheduled Functions, Background Functions, and Edge Functions. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure. Learn more in the [AI Gateway documentation](https://docs.netlify.com/build/ai-gateway/overview/) and [Agent Runners documentation](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). [Permalink to MiniMax M3.1 Flash now available in AI Gateway and Agent Runners Permalink](/changelog/minimax-m3-1-flash-ai-gateway-agent-runners/) - [ ## Introducing the Support Hub ](/changelog/2026-10-16-support-tickets-in-the-netlify-ui/) October 16, 2026 - [workflow](/changelog/tag/workflow/) Enterprise teams can now create, track, and reply to support tickets without leaving Netlify in our new Support Hub. Go to **User settings > Support** to see your tickets, check their status, and continue your conversation with the Netlify support team. Team Owners can see every ticket their team members created, not just their own. The **Requester** column shows who opened each ticket. Members on your team can only view the tickets they opened. ## What you can do - **Create tickets** with a subject, a Markdown description, and CC recipients. - **Track progress** with clear statuses: Open, Awaiting customer response, and Closed. - **Search, sort, and filter** your tickets, including tickets you’re CC’d on. - **Reply from the dashboard.** Your reply goes straight to the support team. ## Not on Enterprise? Support is available on every plan, including Free plans. Use the [Netlify Support page](https://www.netlify.com/support/) or email [support@netlify.com](mailto:support@netlify.com). ## Learn more Learn more from our [Support Hub guide](https://docs.netlify.com/manage/support/overview/) [Permalink to Introducing the Support Hub Permalink](/changelog/2026-10-16-support-tickets-in-the-netlify-ui/) - [ ## TypeSafe Jev 1.14.0 Now Available in AI Gateway ](/changelog/typesafe-jev-1-14-0-ai-gateway/) October 16, 2026 - [ai gateway](/changelog/tag/ai-gateway/) - [ai](/changelog/tag/ai/) TypeSafe’s Jev 1.14.0 model is now available through Netlify’s AI Gateway with zero configuration required. Install `@typesafe-ai/sdk` and use it directly in your Netlify Functions without managing API keys or authentication. AI Gateway handles credentials automatically, and usage is billed to your Netlify credits. Jev answers typed questions about your application state. Here’s an example using `jev-1.14.0` to categorize a support ticket as a bug, feature request, or question: ``` import { choice, TypeSafeClient } from '@typesafe-ai/sdk'; export default async () => { const typesafe = new TypeSafeClient(); const response = await typesafe.systemOne({ model: 'jev-1.14.0', state: { issue: 'App crashes when I click Save.' }, questions: { label: choice('Categorize this ticket', { bug: null, feature: null, question: null, }), }, }); return Response.json(response);}; ``` Jev 1.14.0 is also available across Scheduled Functions, Background Functions, and Edge Functions. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure. Learn more in the [AI Gateway documentation](https://docs.netlify.com/build/ai-gateway/overview/) and the [TypeSafe documentation](https://docs.typesafe.ai/). [Permalink to TypeSafe Jev 1.14.0 Now Available in AI Gateway Permalink](/changelog/typesafe-jev-1-14-0-ai-gateway/) - [ ## Security Update: Next.js and React vulnerabilities (October 2026) ](/changelog/2026-10-14-nextjs-react-security-vulnerabilities/) October 14, 2026 - [security](/changelog/tag/security/) - [next.js](/changelog/tag/next-js/) The Next.js and React teams have disclosed three security vulnerabilities (two critical, one high), released on October 14, 2026: a remote code execution (RCE) in SVG image processing, an RCE in `use cache` (Cache Components), and a denial of service (DoS) in App Router Server Actions. Here’s what Netlify customers need to know. ## Summary If you run Next.js on Netlify, **we strongly recommend upgrading `next` to 15.5.28 or 16.4.1** and redeploying. Several of these have limited or no impact on Netlify; see [Impact on Netlify](#impact-on-netlify). See [What should I do?](#what-should-i-do) for steps. ## Vulnerabilities All issues are patched in **15.5.28** and **16.4.1**. Vulnerability Severity Affected [GHSA-673q-mjm6-r5xr](https://github.com/vercel/next.js/security/advisories/GHSA-673q-mjm6-r5xr) — Unauthenticated Remote Code Execution in `use cache` functions returning typed arrays Critical 16.x apps using Cache Components with a `use cache` function returning typed arrays [GHSA-2464-fhr4-w9xw](https://github.com/vercel/next.js/security/advisories/GHSA-2464-fhr4-w9xw) — Unauthenticated Remote Code Execution in Image Optimization API when SVG files are used ([CVE-2026-96889](https://www.cve.org/CVERecord?id=CVE-2026-96889)) Critical Processing untrusted SVGs via `sharp` (Node.js runtime, glibc Linux); on Netlify, reachable through `next/og` `ImageResponse` [GHSA-p3m5-59mp-jv5r](https://github.com/vercel/next.js/security/advisories/GHSA-p3m5-59mp-jv5r) — Denial of Service in App Router using Server Actions High 13.x–16.x App Router apps with at least one Server Action ## Impact on Netlify ### Remote code execution [GHSA-673q-mjm6-r5xr](https://github.com/vercel/next.js/security/advisories/GHSA-673q-mjm6-r5xr) is a **Critical** RCE affecting Next.js 16.x apps using Cache Components, triggered by a `use cache` function that returns typed arrays — an unusual configuration not expected in normally functioning applications. On Netlify, apps that meet those conditions are **affected**; upgrading Next.js resolves it. [GHSA-2464-fhr4-w9xw](https://github.com/vercel/next.js/security/advisories/GHSA-2464-fhr4-w9xw) ([CVE-2026-96889](https://www.cve.org/CVERecord?id=CVE-2026-96889)) is an RCE in the image library (`sharp`) Next.js uses to process SVGs. The advisory describes it through the next/image Image Optimization API — which on Netlify is served by [Netlify Image CDN](https://docs.netlify.com/build/image-cdn/overview/), not your function, so that path is **not exercised on Netlify**. The same flaw is reachable through `next/og` `ImageResponse`, which does run in your Netlify function: apps that render untrusted input via `ImageResponse` are **affected**. There, the impact is limited to a crashed function invocation, not code execution — **minimal impact** on our autoscaling serverless architecture, though active exploitation could increase your function costs. Upgrading Next.js (which also updates the bundled `sharp`) resolves it. ### Denial of service [GHSA-p3m5-59mp-jv5r](https://github.com/vercel/next.js/security/advisories/GHSA-p3m5-59mp-jv5r) is a server-side DoS affecting App Router apps that define a Server Action. **On Netlify, this has minimal impact**: our autoscaling serverless architecture means a malicious request that consumes excessive CPU in one function does not affect other requests. However, active exploitation could increase your function costs. Upgrading Next.js resolves it. ## What should I do? We strongly recommend **upgrading `next` to 15.5.28 or 16.4.1** and redeploying as soon as possible. Note that any publicly available deploy previews and branch deploys may remain vulnerable until they are [automatically deleted](https://docs.netlify.com/deploy/manage-deploys/manage-deploys-overview/#automatic-deploy-deletion). Consider [deleting these deploys manually](https://docs.netlify.com/deploy/manage-deploys/manage-deploys-overview/#manual-deploy-deletion-through-the-netlify-ui). ## Resources - [Next.js Security Update for Upstream Vulnerabilities](https://nextjs.org/blog/nextjs-security-update-october-14-2026) - [Next.js security advisories](https://github.com/vercel/next.js/security) [Permalink to Security Update: Next.js and React vulnerabilities (October 2026) Permalink](/changelog/2026-10-14-nextjs-react-security-vulnerabilities/) - [ ## TanStack Start 1.0 deploys on Netlify ](/changelog/2026-10-13-tanstack-start-1-0/) October 13, 2026 - [framework](/changelog/tag/framework/) - [agent runners](/changelog/tag/agent-runners/) TanStack Start is now 1.0, and Start apps deploy on Netlify. SSR, server routes, server functions, and middleware run on Netlify Functions. It’s also what new Agent Runners projects start with by default. ## Start a new app Deploy the official template, or generate your own: ``` npx create-tsrouter-app@latest --template file-router --add-ons tanchat,netlify ``` ## Deploy an existing app Install the Netlify plugin: ``` npm install -D @netlify/vite-plugin-tanstack-start ``` Then add it to `vite.config.ts` after `tanstackStart()`: ``` import { defineConfig } from 'vite'import { tanstackStart } from '@tanstack/react-start/plugin/vite'import netlify from '@netlify/vite-plugin-tanstack-start' export default defineConfig({ plugins: [tanstackStart(), netlify()],}) ``` Add a `netlify.toml` with your build settings: ``` [build] command = "vite build" publish = "dist/client" ``` ## Develop locally against the real platform The plugin emulates Netlify in your dev server, so you can build against the same primitives you’ll use in production, without the Netlify CLI: - Serverless functions and edge functions - Blobs and Netlify Database - Cache API and Image CDN - Redirects, rewrites, and headers - Environment variables - AI Gateway ## Start with Agent Runners New projects you start with Agent Runners use TanStack Start 1.0 unless another framework is specified. [Read the TanStack Start guide](https://docs.netlify.com/build/frameworks/framework-setup-guides/tanstack-start/) · [Explore the template](https://github.com/netlify-templates/tanstack-template) [Permalink to TanStack Start 1.0 deploys on Netlify Permalink](/changelog/2026-10-13-tanstack-start-1-0/) - [ ## Google Gemini 4 Argon now available in AI Gateway and Agent Runners ](/changelog/gemini-4-argon-ai-gateway-agent-runners/) October 13, 2026 - [ai gateway](/changelog/tag/ai-gateway/) - [agent runners](/changelog/tag/agent-runners/) Google’s Gemini 4 Argon model is now available through Netlify’s AI Gateway and Agent Runners with zero configuration required. Use the Google GenAI SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the Gemini 4 Argon model: ``` import { GoogleGenAI } from '@google/genai'; export default async () => { const ai = new GoogleGenAI({}); const response = await ai.models.generateContent({ model: 'gemini-4-argon', contents: 'How can AI improve my coding?' }); return Response.json(response);}; ``` Gemini 4 Argon is available for all Function types and Agent Runners. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure. Learn more in the [AI Gateway documentation](https://docs.netlify.com/build/ai-gateway/overview/) and [Agent Runners documentation](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). [Permalink to Google Gemini 4 Argon now available in AI Gateway and Agent Runners Permalink](/changelog/gemini-4-argon-ai-gateway-agent-runners/) - [ ## Mistral Large 4 now available in Agent Runners ](/changelog/mistral-large-4-agent-runners/) October 13, 2026 - [agent runners](/changelog/tag/agent-runners/) Mistral AI’s Mistral Large 4 model is now available in Netlify Agent Runners. With a 524K-token context window, it’s built for agentic coding and long-context work, making it a good fit for multi-step tasks across larger codebases. Select it from the model picker to try it today. Learn more in [docs](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). [Permalink to Mistral Large 4 now available in Agent Runners Permalink](/changelog/mistral-large-4-agent-runners/) [Next page](/changelog/page/2)