--- 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/3/" last_updated: "2026-07-02T11:33:58.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) - [ ## Gemini 3.5 Flash now available in AI Gateway ](/changelog/gemini-3-5-flash-ai-gateway/) May 19, 2026 - [ai gateway](/changelog/tag/ai-gateway/) Google’s Gemini 3.5 Flash model is now available through Netlify’s AI Gateway 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 3.5 Flash model: ``` import { GoogleGenAI } from '@google/genai'; export default async () => { const ai = new GoogleGenAI({}); const response = await ai.models.generateContent({ model: 'gemini-3.5-flash', contents: 'How can AI improve my coding?' }); return Response.json(response);}; ``` Gemini 3.5 Flash is available for all Function types. 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/). [Permalink to Gemini 3.5 Flash now available in AI Gateway Permalink](/changelog/gemini-3-5-flash-ai-gateway/) - [ ## Agent Runners workflow improvements ](/changelog/2026-05-13-agent-runners-workflow-improvements/) May 13, 2026 - [agent runners](/changelog/tag/agent-runners/) We’re making it easier to use Agent Runners in the existing workflows you have. Now you can do the following in a more seamless way: - Prompt new changes using Agent Runners more quickly from a GitHub pull request link - Copy output from Agent Runners faster so you can get back to what you’re doing - Track pull request ownership so you can understand who is doing what at-a-glance ## Start prompting updates from GitHub PR comment link GitHub-linked sites already receive a comment on each pull request with links to build logs, failure diagnostics, and more. That comment now also includes a **Make changes** link that opens Agent Runner for the site, with the pull request‘s branch pre-selected in the dropdown. This makes it faster to act on review feedback or investigate a failing build. Learn more about [Agent Runners](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). ## Copy to clipboard in single click You can now copy Agent Runner output with a single click. Previously, grabbing output text — especially long responses or anything on mobile — meant manually selecting it all. A new copy-to-clipboard button now appears alongside Agent Runner output, making it easy to drop results into a doc, a message, or wherever you need them. ## Pull requests auto-assign people for clearer ownership Agent Runner–created pull requests now automatically assign the person who opened them, provided their GitHub account is linked with Netlify. Before this change, pull requests opened by an agent runner had no assignee, making it harder for teams to track ownership at a glance. Now, when Netlify can match the user to a GitHub account, the pull request is assigned to them automatically. To take advantage of this, make sure your GitHub account is connected under your [Netlify account settings](https://docs.netlify.com/manage/accounts-and-billing/user-settings/). [Permalink to Agent Runners workflow improvements Permalink](/changelog/2026-05-13-agent-runners-workflow-improvements/) - [ ## Block project transfers out of your team ](/changelog/2026-05-08-block-project-transfers/) May 8, 2026 - [security](/changelog/tag/security/) - [workflow](/changelog/tag/workflow/) Team Owners can now guarantee that projects stay within the team to meet compliance or ownership requirements by blocking every project from being transferred to another team. Once a Team Owner blocks project transfers out of the team, even the Team Owner cannot transfer projects out of the team unless they change this setting, which is tracked in the team’s audit log. ## Try it out To change the setting, go to **Team settings > Access & security > Transfer site settings** and select **Edit settings**. ![Transfer project settings panel showing Allowed and Blocked options for project transfers](/images/changelog/block-project-transfers-setting.png) When transfers are blocked, the **Transfer project** action is hidden for every project owned by the team and the backend rejects transfer requests for those projects. ## Enterprise defaults Enterprise teams start with project transfers set to **Blocked** for security reasons, but Team Owners can change this setting to **Allowed** at any time. Only Team Owners can change this setting and changes are recorded in the team audit log. ## Learn more Learn more in our docs on [Transferring a project](https://docs.netlify.com/manage/accounts-and-billing/team-management/team-owned-sites/). [Permalink to Block project transfers out of your team Permalink](/changelog/2026-05-08-block-project-transfers/) - [ ## Security Update: Multiple vulnerabilities in Next.js and React ](/changelog/2026-05-08-react-nextjs-security-vulnerabilities/) May 8, 2026 - [security](/changelog/tag/security/) - [next.js](/changelog/tag/next-js/) The Next.js and React teams have disclosed [twelve security vulnerabilities](https://github.com/vercel/next.js/security): one in React Server Components and eleven in Next.js, all patched on May 6, 2026, plus a follow-up advisory on May 7. The issues span middleware/proxy bypass, cross-site scripting (XSS), server-side request forgery (SSRF), cache poisoning, and denial of service (DoS). No detailed proof-of-concept information has been published. Here’s what Netlify customers need to know. ## Summary If you run Next.js on Netlify, **we strongly recommend upgrading `next` to 15.5.18 or 16.2.6** and redeploying. This also brings in the patched React Server Components dependency. Projects using Pages Router with i18n and Next.js Middleware / Proxy also need [OpenNext Netlify Next.js adapter v5.15.11](https://github.com/opennextjs/opennextjs-netlify/releases/tag/v5.15.11). If you use `react-server-dom-*` outside of Next.js, upgrade to 19.0.6 / 19.1.7 / 19.2.6 matching your React minor. See [What should I do?](#what-should-i-do) for full steps. Netlify’s platform is **not** vulnerable to several of these CVEs. Image Optimization, WebSocket SSRF, RSC cache poisoning, and the cache-poisoned-redirect bypass do not affect Netlify projects. See [Impact on Netlify](#impact-on-netlify) for the per-CVE verdict. ## Vulnerabilities ### React (`react-server-dom-*`) This affects `react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack`. The Next.js advisory [GHSA-8h8q-6873-q5fj](https://github.com/vercel/next.js/security/advisories/GHSA-8h8q-6873-q5fj) tracks the same issue downstream. Vulnerability Severity Affected versions Fixed in [GHSA-rv78-f8rc-xrxh](https://github.com/facebook/react/security/advisories/GHSA-rv78-f8rc-xrxh) — DoS in Server Components ([CVE-2026-23870](https://www.cve.org/CVERecord?id=CVE-2026-23870)) High 19.0.0–19.0.5, 19.1.0–19.1.6, 19.2.0–19.2.5 19.0.6, 19.1.7, 19.2.6 ### Next.js All Next.js issues are patched in **15.5.18** and **16.2.6**. Earlier minors of 15.x and 16.x will not be patched; affected projects must upgrade to a patched minor. Vulnerability Severity Affected versions [GHSA-8h8q-6873-q5fj](https://github.com/vercel/next.js/security/advisories/GHSA-8h8q-6873-q5fj) — DoS with Server Components High ≥13.0.0 [GHSA-267c-6grr-h53f](https://github.com/vercel/next.js/security/advisories/GHSA-267c-6grr-h53f) — Middleware / Proxy bypass in App Router via segment-prefetch routes High ≥15.2.0 [GHSA-26hh-7cqf-hhc6](https://github.com/vercel/next.js/security/advisories/GHSA-26hh-7cqf-hhc6) — Follow-up to [GHSA-267c-6grr-h53f](https://github.com/vercel/next.js/security/advisories/GHSA-267c-6grr-h53f): incomplete fix for `middleware.ts` with Turbopack High ≥15.2.0 [GHSA-mg66-mrh9-m8jx](https://github.com/vercel/next.js/security/advisories/GHSA-mg66-mrh9-m8jx) — DoS via connection exhaustion in apps using Cache Components High ≥15.0.0 (apps using Cache Components) [GHSA-492v-c6pp-mqqv](https://github.com/vercel/next.js/security/advisories/GHSA-492v-c6pp-mqqv) — Middleware / Proxy bypass through dynamic route parameter injection High ≥15.4.0 [GHSA-c4j6-fc7j-m34r](https://github.com/vercel/next.js/security/advisories/GHSA-c4j6-fc7j-m34r) — SSRF in applications using WebSocket upgrades High ≥13.4.13 [GHSA-36qx-fr4f-26g5](https://github.com/vercel/next.js/security/advisories/GHSA-36qx-fr4f-26g5) — Middleware / Proxy bypass in Pages Router applications using i18n High ≥12.2.0 [GHSA-ffhc-5mcf-pf4q](https://github.com/vercel/next.js/security/advisories/GHSA-ffhc-5mcf-pf4q) — XSS in App Router applications using CSP nonces Medium ≥13.4.0 [GHSA-gx5p-jg67-6x7h](https://github.com/vercel/next.js/security/advisories/GHSA-gx5p-jg67-6x7h) — XSS in `beforeInteractive` scripts with untrusted input Medium ≥13.0.0 [GHSA-h64f-5h5j-jqjh](https://github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jqjh) — DoS in the Image Optimization API Medium ≥10.0.0 [GHSA-wfc6-r584-vfw7](https://github.com/vercel/next.js/security/advisories/GHSA-wfc6-r584-vfw7) — Cache poisoning in React Server Component responses Medium ≥14.2.0 [GHSA-vfv6-92ff-j949](https://github.com/vercel/next.js/security/advisories/GHSA-vfv6-92ff-j949) — Cache poisoning via collisions in React Server Component cache-busting Low ≥13.4.6 [GHSA-3g8h-86w9-wvmq](https://github.com/vercel/next.js/security/advisories/GHSA-3g8h-86w9-wvmq) — Middleware / Proxy redirects can be cache-poisoned Low ≥12.2.0 ## Impact on Netlify ### Denial of service [GHSA-8h8q-6873-q5fj](https://github.com/vercel/next.js/security/advisories/GHSA-8h8q-6873-q5fj) and [GHSA-mg66-mrh9-m8jx](https://github.com/vercel/next.js/security/advisories/GHSA-mg66-mrh9-m8jx) are server-side denial-of-service (DoS) vulnerabilities. On Netlify, these have **minimal impact**: our autoscaling serverless architecture means that a malicious request resulting in a crashed or hung function does not affect other requests. However, active exploitation could increase your function costs. Note that Cache Components ([GHSA-mg66-mrh9-m8jx](https://github.com/vercel/next.js/security/advisories/GHSA-mg66-mrh9-m8jx)) is an opt-in Next.js feature that is not enabled by default. Upgrading Next.js resolves both. [GHSA-h64f-5h5j-jqjh](https://github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jqjh) affects the Next.js Image Optimization API. Netlify projects are **not affected**: this Next.js code path is not used on Netlify — image optimization is handled by [Netlify Image CDN](https://docs.netlify.com/build/image-cdn/overview/), a separate service that runs outside your project’s functions with its own protections against this class of issue. ### Middleware / proxy bypass These four CVEs affect Next.js middleware and proxy routing. Because Netlify runs Next.js middleware via our own edge function adapter, the impact varies per CVE: - [GHSA-3g8h-86w9-wvmq](https://github.com/vercel/next.js/security/advisories/GHSA-3g8h-86w9-wvmq) (cache-poisoned redirects): Netlify projects are **not affected**. Our OpenNext Netlify Next.js adapter already varies cached responses on the `x-nextjs-data` header. - [GHSA-492v-c6pp-mqqv](https://github.com/vercel/next.js/security/advisories/GHSA-492v-c6pp-mqqv) (dynamic route parameter injection): Netlify projects are **affected**, and the upstream Next.js fix applies. Upgrading Next.js resolves the issue. - [GHSA-36qx-fr4f-26g5](https://github.com/vercel/next.js/security/advisories/GHSA-36qx-fr4f-26g5) (Pages Router i18n bypass): Netlify projects using Pages Router with i18n and Next.js Middleware / Proxy are **affected**. The upstream Next.js patch alone does not resolve this on Netlify; a Netlify-specific fix shipped in [OpenNext Netlify Next.js adapter v5.15.11](https://github.com/opennextjs/opennextjs-netlify/releases/tag/v5.15.11). See [how to upgrade](#what-should-i-do) below. - [GHSA-267c-6grr-h53f](https://github.com/vercel/next.js/security/advisories/GHSA-267c-6grr-h53f) (App Router segment-prefetch bypass) and [GHSA-26hh-7cqf-hhc6](https://github.com/vercel/next.js/security/advisories/GHSA-26hh-7cqf-hhc6) (follow-up): Netlify projects are **affected**, and the upstream Next.js fix applies. Upgrading Next.js resolves both. ### Cross-site scripting [GHSA-ffhc-5mcf-pf4q](https://github.com/vercel/next.js/security/advisories/GHSA-ffhc-5mcf-pf4q) and [GHSA-gx5p-jg67-6x7h](https://github.com/vercel/next.js/security/advisories/GHSA-gx5p-jg67-6x7h) are client-side XSS vulnerabilities. Regardless of hosting provider, all apps using CSP nonces in App Router or passing untrusted input to `beforeInteractive` scripts may be **vulnerable**. Upgrade Next.js to remediate. ### Server-side request forgery [GHSA-c4j6-fc7j-m34r](https://github.com/vercel/next.js/security/advisories/GHSA-c4j6-fc7j-m34r) affects applications using WebSocket upgrades. Netlify projects are **not affected**: Netlify Functions and Edge Functions do not support WebSocket upgrades, so this Next.js code path cannot be exercised on Netlify. ### Cache poisoning [GHSA-wfc6-r584-vfw7](https://github.com/vercel/next.js/security/advisories/GHSA-wfc6-r584-vfw7) and [GHSA-vfv6-92ff-j949](https://github.com/vercel/next.js/security/advisories/GHSA-vfv6-92ff-j949) affect React Server Component response caching. Netlify projects are **not affected**: Netlify’s CDN does not rely on the `_rsc` cache-busting query parameter (so collisions in it cannot poison cache entries), and it honors `Vary` on RSC-related request headers. ## What should I do? We strongly recommend upgrading as soon as possible to patched releases: - **Next.js projects:** upgrade `next` to 15.5.18 or 16.2.6. This bundles the patched React Server Components dependency, so a separate `react-server-dom-*` upgrade is not needed. - **Direct `react-server-dom-*` users** (React Router RSC, Vite RSC plugin, custom RSC setups): upgrade `react-server-dom-webpack`, `react-server-dom-parcel`, or `react-server-dom-turbopack` to 19.0.6, 19.1.7, or 19.2.6 — matching your React minor. For Next.js 13.x and 14.x users: patches are not planned for these versions. Consider upgrading to Next.js 15.x or 16.x. For projects using Pages Router with i18n and Next.js Middleware / Proxy ([GHSA-36qx-fr4f-26g5](https://github.com/vercel/next.js/security/advisories/GHSA-36qx-fr4f-26g5)), the upstream Next.js fix does not fully apply on Netlify. The fix ships in [OpenNext Netlify Next.js adapter v5.15.11](https://github.com/opennextjs/opennextjs-netlify/releases/tag/v5.15.11): - Auto-installed adapter (default): redeploy. - Manually installed adapter: upgrade `@netlify/plugin-nextjs` to v5.15.11 and redeploy. We recommend [not pinning the adapter version](https://docs.netlify.com/build/frameworks/framework-setup-guides/nextjs/overview/#how-netlify-runs-your-nextjs-app) so future fixes ship automatically. 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 - [React security advisory (GHSA-rv78-f8rc-xrxh)](https://github.com/facebook/react/security/advisories/GHSA-rv78-f8rc-xrxh) - [CVE-2026-23870](https://www.cve.org/CVERecord?id=CVE-2026-23870) - [Next.js security advisories](https://github.com/vercel/next.js/security) [Permalink to Security Update: Multiple vulnerabilities in Next.js and React Permalink](/changelog/2026-05-08-react-nextjs-security-vulnerabilities/) - [ ## Gemini 3.1 Flash-Lite now available in AI Gateway ](/changelog/gemini-3-1-flash-lite-ai-gateway/) May 7, 2026 - [ai gateway](/changelog/tag/ai-gateway/) Google’s Gemini 3.1 Flash-Lite model is now available through Netlify’s AI Gateway with zero configuration required. The [Preview version](https://www.netlify.com/changelog/gemini-3-1-flash-lite-preview-ai-gateway/) of this model was available as of March 3, 2026. 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 3.1 Flash-Lite model: ``` import { GoogleGenAI } from '@google/genai'; export default async () => { const ai = new GoogleGenAI({}); const response = await ai.models.generateContent({ model: 'gemini-3.1-flash-lite', contents: 'How can AI improve my coding?' }); return Response.json(response);}; ``` Gemini 3.1 Flash-Lite is available for all Function types. 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/). [Permalink to Gemini 3.1 Flash-Lite now available in AI Gateway Permalink](/changelog/gemini-3-1-flash-lite-ai-gateway/) - [ ## OpenAI GPT-5.5 Instant now available in AI Gateway ](/changelog/2026-05-05-gpt-5-5-instant-ai-gateway/) May 5, 2026 - [ai gateway](/changelog/tag/ai-gateway/) OpenAI’s GPT-5.5 Instant model is now available through Netlify’s AI Gateway with zero configuration required. Use the OpenAI SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the GPT-5.5 Instant model: ``` import OpenAI from 'openai'; export default async () => { const openai = new OpenAI(); const response = await openai.responses.create({ model: 'chat-latest', input: 'How does AI work?' }); return Response.json(response);}; ``` **Note:** The model API name is `chat-latest`. GPT-5.5 Instant is available for all Function types. 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/). [Permalink to OpenAI GPT-5.5 Instant now available in AI Gateway Permalink](/changelog/2026-05-05-gpt-5-5-instant-ai-gateway/) - [ ## Netlify Identity package update: CSRF protection with new \`verifyRequestOrigin\` helper ](/changelog/2026-05-02-netlify-identity-verify-request-origin/) May 2, 2026 `@netlify/identity` 1.1.0 introduces a new `verifyRequestOrigin` helper to make it easier for developers and AI agents to add CSRF (Cross-Site Request Forgery) protection when running authentication on the server. You can call `login()`, `signup()`, or `logout()` from a Netlify Function or Edge Function to handle authentication entirely on the server. The library reads and writes the `nf_jwt` and `nf_refresh` cookies through the Netlify runtime, so the user’s browser receives the session via the response. netlify/functions/login.ts ``` import { login, verifyRequestOrigin } from '@netlify/identity'import type { Context } from '@netlify/functions' export default async (req: Request, context: Context) => { verifyRequestOrigin(req) const { email, password } = await req.json() await login(email, password) return new Response(null, { status: 302, headers: { Location: '/dashboard' } })} ``` When `login()`, `signup()`, or `logout()` runs inside an HTTP endpoint that you expose, that endpoint needs Cross-Site Request Forgery (CSRF) protection. Without it, an attacker can trick a victim’s browser into logging into the attacker’s account, then collect anything the victim does inside that session. Call `verifyRequestOrigin(request)` at the start of the handler. It compares the request’s `Origin` header against the request’s own origin and throws a 403 on mismatch. If your framework already checks `Origin` on state-changing requests by default, the call is redundant but harmless. Refer to the [`@netlify/identity` CSRF protection documentation](https://www.npmjs.com/package/@netlify/identity#security-csrf-protection) for the full threat model and the `allowedOrigins` option. [Permalink to Netlify Identity package update: CSRF protection with new \`verifyRequestOrigin\` helper Permalink](/changelog/2026-05-02-netlify-identity-verify-request-origin/) - [ ## New \`netlify logs\` CLI command ](/changelog/2026-05-01-netlify-logs-cli-command/) May 1, 2026 - [cli announcement](/changelog/tag/cli-announcement/) The Netlify CLI now includes a `netlify logs` command, giving you a powerful and flexible way to access logs for your projects whether you’re a developer debugging locally or an AI agent processing structured output. ## Filter by source Use `--source` to pull logs from functions, edge functions, deploys, or any combination of them together. Color-coded output makes it easy to tell sources apart at a glance when you’re tailing multiple at once. ![netlify logs CLI showing colour-coded output from functions and edge functions](/images/changelog/netlify-logs-cli-colour-coded.png) Need to narrow it down further? The `--function` and `--edge-function` flags let you filter to a specific function by name, and `--url` lets you target the exact deploy you want logs from. ## Historical and real-time views The `--since` and `--until` flags let you query logs over any specific time window — useful for tracking down what happened during a past deploy or incident. When you want to watch logs as they come in, `--follow` streams them in real time. ## JSON Lines support Pass `--json` to get structured output in JSON Lines format. This works in both historical and real-time modes, making `netlify logs` easy to pipe into your own tooling or integrate into automated workflows. ![netlify logs CLI with --json flag showing JSON Lines output](/images/changelog/netlify-logs-cli-json.png) Update to the latest Netlify CLI to start using it: ``` npm install -g netlify-cli@latest ``` Then run `netlify logs --help` to see all available options. [Permalink to New \`netlify logs\` CLI command Permalink](/changelog/2026-05-01-netlify-logs-cli-command/) - [ ## Deploy to Netlify with Stripe Projects ](/changelog/2026-04-29-stripe-projects/) April 29, 2026 You can now deploy projects to Netlify using Stripe Projects, a tool that helps you manage all the services your site needs from a single CLI without context switching between dashboards. Learn more about this update and what it means for your workflow and working with AI agents in our blog post [Agent experience moves upstream](https://www.netlify.com/blog/agent-experience-moves-upstream/). Get started with our [Stripe Projects docs](https://docs.netlify.com/extend/install-and-use/setup-guides/stripe-projects), or check out Stripe’s official [Stripe Projects docs](https://docs.stripe.com/projects) for the full list of supported services and configuration options. [Permalink to Deploy to Netlify with Stripe Projects Permalink](/changelog/2026-04-29-stripe-projects/) [Previous page](/changelog/page/2) [Next page](/changelog/page/4)