--- 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/" last_updated: "2026-08-29T18:19:26.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) - [ ## GitHub stacked pull requests now create Deploy Previews ](/changelog/2026-08-27-github-stacked-pull-request-deploy-previews/) August 27, 2026 - [devtools](/changelog/tag/devtools/) - [workflow](/changelog/tag/workflow/) Netlify now creates a [Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/) for every pull request in a GitHub stack when the stack ultimately targets your project’s [production branch](https://docs.netlify.com/deploy/deploy-types/production-deploy/) (usually `main`). You can review and share each layer of a larger change before it merges. ![A GitHub stacked pull request showing a successful Netlify Deploy Preview check](/images/changelog/github-stacked-pull-request-deploy-preview.png) [GitHub Stacked Pull Requests](https://github.blog/changelog/2026-07-30-stacked-pull-requests-are-now-in-public-preview/) help teams split a larger update into smaller, connected pull requests. Each pull request can focus on one step of the work, making changes easier to review and merge in sequence. Previously, Netlify only created a Deploy Preview for the first pull request in your stack while additional pull requests in the stack didn’t get their own Deploy Previews. Now, every pull request in the stack gets its own Deploy Preview. There’s nothing new to configure. Create and update your stack in GitHub as usual, and Netlify automatically adds a Deploy Preview to each eligible pull request. ## Learn More - [Get an overview of GitHub Stacked Pull Requests](https://github.github.com/gh-stack/introduction/overview/) - [Follow GitHub’s quick start for creating a stack](https://github.github.com/gh-stack/getting-started/quick-start/) [Permalink to GitHub stacked pull requests now create Deploy Previews Permalink](/changelog/2026-08-27-github-stacked-pull-request-deploy-previews/) - [ ## Security Update: Two critical Next.js vulnerabilities ](/changelog/2026-08-25-nextjs-security-vulnerabilities/) August 25, 2026 - [security](/changelog/tag/security/) - [next.js](/changelog/tag/next-js/) The Next.js team has disclosed [two critical severity vulnerabilities](https://github.com/vercel/next.js/security), both of which can lead to unauthenticated remote code execution. Both are patched in **15.5.24** and **16.3.3**. **Netlify-hosted sites are not affected by the Windows issue, and do not run the Next.js code path affected by the image issue.** We still recommend upgrading. Here’s what Netlify customers need to know. ## Vulnerabilities Vulnerability Severity Affected versions CVE-2026-75604 / [GHSA-p293-qw3h-jr36](https://github.com/vercel/next.js/security/advisories/GHSA-p293-qw3h-jr36) — Unauthenticated remote code execution on Windows-hosted servers Critical ≥13.4.0 <15.5.24, ≥16.0.0 <16.3.3 [GHSA-2xp9-vwfh-vxw4](https://github.com/vercel/next.js/security/advisories/GHSA-2xp9-vwfh-vxw4) — Unauthenticated remote code execution in Image Optimization API when AVIF files are used Critical ≥10.0.0 <15.5.24, ≥16.0.0 <16.3.3 ## Impact on Netlify ### Unauthenticated remote code execution on Windows-hosted servers CVE-2026-75604 / [GHSA-p293-qw3h-jr36](https://github.com/vercel/next.js/security/advisories/GHSA-p293-qw3h-jr36): Netlify sites are **not affected**. The issue affects Windows-hosted deployments only, and [Netlify Functions](https://docs.netlify.com/build/functions/overview/) and [Edge Functions](https://docs.netlify.com/build/edge-functions/overview/) run on Linux. ### Unauthenticated remote code execution in Image Optimization API when AVIF files are used [GHSA-2xp9-vwfh-vxw4](https://github.com/vercel/next.js/security/advisories/GHSA-2xp9-vwfh-vxw4): Netlify sites **do not run the affected Next.js code path**. Requests to `/_next/image` are rewritten to [Netlify Image CDN](https://docs.netlify.com/build/image-cdn/overview/) at our edge, so the Next.js Image Optimization API is never invoked. ## What should I do? Netlify sites are not affected by the Windows issue and do not run the affected image code path, but we always strongly recommend upgrading as soon as possible to patched releases: - `next` 15.5.24 or later, or 16.3.3 or later, then redeploy. ## Resources - [Next.js August 2026 security release](https://nextjs.org/blog/august-2026-security-release) - [Next.js security advisories](https://github.com/vercel/next.js/security) [Permalink to Security Update: Two critical Next.js vulnerabilities Permalink](/changelog/2026-08-25-nextjs-security-vulnerabilities/) - [ ## Pre-launch toolbar and the Powered by Netlify badge ](/changelog/2026-08-19-pre-launch-toolbar-and-powered-by-netlify-badge/) August 19, 2026 - [workflow](/changelog/tag/workflow/) - [agent runners](/changelog/tag/agent-runners/) Private projects on Netlify will now show a pre-launch toolbar so you can share your project for review and run audits using AI checks before you make your project public. Private projects and agent runs require a [Credit pricing plan](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/). If you’re on a Legacy pricing plan, you will not have access to the pre-launch toolbar. Audits consume credits like any other [agent run](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). For public projects, **new projects created on a Free plan on or after August 19, 2026 show a Powered by Netlify badge to all visitors**. The badge is configurable for each project through your project configuration settings. To turn the Netlify badge on or off for all visitors of your site: 1. Go to **Project configuration > General > Powered by Netlify badge** and turn it on or off. Additionally, any visitor can hide the badge for themselves, and that choice is stored locally on their browser and never reaches Netlify. All projects created before August 19, 2026 have the badge off by default. Users on a Credit-based Personal and Pro plans can also turn the badge on or off per-project. For these plans, the badge is always off by default. ## Release timeline We’re rolling both overlays out gradually over the next few weeks, so a project that qualifies may not have them yet. Learn more about the [pre-launch toolbar](https://docs.netlify.com/manage/projects/pre-launch-toolbar/) and the [Powered by Netlify badge](https://docs.netlify.com/manage/projects/powered-by-netlify-badge/) in the Netlify documentation. [Permalink to Pre-launch toolbar and the Powered by Netlify badge Permalink](/changelog/2026-08-19-pre-launch-toolbar-and-powered-by-netlify-badge/) - [ ## Agent Runners can now ask clarifying questions ](/changelog/2026-08-19-agent-runners-clarifying-questions/) August 19, 2026 - [agent runners](/changelog/tag/agent-runners/) - [ai](/changelog/tag/ai/) - [workflow](/changelog/tag/workflow/) Agent Runners can now ask you clarifying questions before they start building. When a few details could significantly improve the result, the agent pauses and asks instead of guessing. ![The clarifying questions UI in an Agent Runners session, asking: What should the tracker dashboard keep track of?](/images/changelog/agent-runners-clarifying-questions.png) ## How clarifying questions work Say you start with something broad, like “Build a tracker dashboard.” Previously the agent had to make every call for you: what the dashboard should track, whether entries should be editable and saved to a database or live in the code as a read-only placeholder, whether the look should be dark and high-contrast or light, clean, and editorial. Now it can ask, and you can answer directly where the agent run works. ## Answer, skip, or add your own context Answering questions is always optional so you can answer the ones you have opinions about and skip the rest. Or you can skip all questions and let the agent decide. Finally, you can always add context in your own words alongside your answers. In our testing, even a few quick answers make the first build noticeably sharper and saves credits you’d otherwise spend on course corrections. Once you answer, the run continues as usual: the agent writes the code, works with Netlify’s platform features, and creates a Deploy Preview you can review and iterate on. ## Learn more Clarifying questions work with every agent and model available in Agent Runners. Try it out and see [how to use Agent Runners](https://docs.netlify.com/build/build-with-ai/agent-runners/make-changes-with-agent-runners/) in our docs. [Permalink to Agent Runners can now ask clarifying questions Permalink](/changelog/2026-08-19-agent-runners-clarifying-questions/) - [ ## Google Gemini 3.7 Flash now available in AI Gateway and Agent Runners ](/changelog/gemini-3-7-flash-ai-gateway-agent-runners/) August 13, 2026 - [ai gateway](/changelog/tag/ai-gateway/) - [agent runners](/changelog/tag/agent-runners/) Google’s Gemini 3.7 Flash 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 3.7 Flash model: ``` import { GoogleGenAI } from '@google/genai'; export default async () => { const ai = new GoogleGenAI({}); const response = await ai.models.generateContent({ model: 'gemini-3.7-flash', contents: 'How can AI improve my coding?' }); return Response.json(response);}; ``` Gemini 3.7 Flash 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 3.7 Flash now available in AI Gateway and Agent Runners Permalink](/changelog/gemini-3-7-flash-ai-gateway-agent-runners/) - [ ## Manage your team invitations from your Netlify dashboard ](/changelog/2026-08-12-accept-team-invites-in-app/) August 12, 2026 - [workflow](/changelog/tag/workflow/) Invitations to join an existing team now show up within your Netlify dashboard, where you can accept or decline them directly without checking your email inbox. Previously, the invitation email was the only way in. If it got buried, filtered, or sent to an address you no longer check, then getting collaboration started with your teammate took a lot longer than it needed to. Now, when you sign in to Netlify with an email address that has a pending invitation, you’ll see it waiting for you. Accept it and you’re on the team immediately. Decline it and it’s cleared out. Either way, you never have to go digging through your inbox. Nothing changes about how invitations are sent. Invitees still receive the same email they always have, and accepting from that link works exactly as before. This is simply a second, more reliable path to the same place. Learn more about inviting and managing teammates in [Manage team members](https://docs.netlify.com/manage/accounts-and-billing/team-management/manage-team-members/) in the Netlify documentation. [Permalink to Manage your team invitations from your Netlify dashboard Permalink](/changelog/2026-08-12-accept-team-invites-in-app/) - [ ## Pay for Netlify with Apple Pay and Google Pay ](/changelog/2026-08-12-apple-pay-google-pay/) August 12, 2026 - [workflow](/changelog/tag/workflow/) You can now pay for Netlify with Apple Pay or Google Pay, in addition to paying by credit card. Both options show up as you’d expect at checkout, so you can confirm a payment with the device you already have in hand instead of tracking down a card. It’s a small change, but it removes a genuine bit of friction—especially when you’re upgrading in the middle of shipping something and don’t want to break flow to go find your wallet. Credit cards continue to work exactly as they always have. If that’s what your team uses, there’s nothing to change and nothing to migrate. Apple Pay and Google Pay are simply two more ways to pay. Learn more in the [Netlify billing documentation](https://docs.netlify.com/manage/accounts-and-billing/billing/overview/). [Permalink to Pay for Netlify with Apple Pay and Google Pay Permalink](/changelog/2026-08-12-apple-pay-google-pay/) - [ ## Simplified single sign-on (SSO) process ](/changelog/2026-08-12-sso-sign-in-with-email/) August 12, 2026 - [security](/changelog/tag/security/) If your team uses SSO (single sign-on) with an identity provider, you can now sign in with just your email address without using your team ID. Netlify recognizes your domain and sends you straight to your identity provider. Previously, SSO required you to know your Team ID. That meant every new hire had to know and enter a Team ID, and anyone who forgot or didn’t know it was stuck at the login screen. It was a small detail that quietly created support work for the people administering the team. Now the flow is simplified: enter your email, get redirected to whichever identity provider your team has configured, authenticate there, and land back in Netlify. This is live for every team using SSO with an identity provider that lets you use your email address to authenticate. This means your existing SAML setup already carries everything Netlify needs to route people to the right place. Learn more about [configuring SAML SSO](https://docs.netlify.com/manage/security/secure-netlify-access/configure-organization-saml-sso/) in the Netlify documentation. [Permalink to Simplified single sign-on (SSO) process Permalink](/changelog/2026-08-12-sso-sign-in-with-email/) - [ ## SolidStart 2 just works on Netlify ](/changelog/2026-08-06-solidstart-2-on-netlify/) August 6, 2026 - [framework](/changelog/tag/framework/) [SolidStart 2](https://github.com/solidjs/solid-start/discussions/2281) is out, and it deploys to Netlify with no framework-specific adapter to install, a first for full-stack frameworks on Netlify. While SolidStart 1 deployed to Netlify through Nitro under the hood, SolidStart 2 no longer includes Nitro, [building directly on Vite’s Environment API](https://github.com/solidjs/solid-start/discussions/2281) instead. The Netlify Vite plugin can now take the server build Vite produces and prepare it for deployment on its own, with no SolidStart-specific Netlify adapter needed in between. ## How to deploy Install the [Netlify Vite plugin](https://npmx.dev/package/@netlify/vite-plugin): ``` npm install -D @netlify/vite-plugin ``` Then add it to your Vite config with its build support turned on: vite.config.ts ``` import netlify from '@netlify/vite-plugin';import { solidStart } from '@solidjs/start/config';import { defineConfig } from 'vite'; export default defineConfig({ plugins: [solidStart(), netlify({ build: { enabled: true } })],}); ``` That’s the whole setup for a new project. Netlify detects SolidStart and fills in your build settings, and your SSR pages, API routes, server functions, and middleware deploy to [Netlify Functions](https://docs.netlify.com/build/functions/overview/). Prefer to build with [Nitro](https://nitro.build/)? It became a Vite plugin in Nitro 3 and auto-detects Netlify, so adding `nitro()` works too. Just remove `build.enabled` from the Netlify Vite plugin. Either way, `vite dev` gives you the full Netlify platform emulated right in your dev server without reaching for the Netlify CLI. ## Already on SolidStart 1? Nothing breaks, and your Nitro `netlify` preset keeps working. When you’re ready to upgrade, follow the framework [upgrade guide](https://docs.solidjs.com/solid-start/v2/migrating-from-v1). We recommend then moving to the Netlify Vite plugin with build support as described above and changing your publish directory from `dist` to `dist/client`. (If you keep building with Nitro, `dist` stays as it is.) ## Why there’s no SolidStart adapter Every framework used to need its own adapter for every platform, and every adapter needed someone to keep it current. Frameworks converging on Vite’s Environment API doesn’t change this on its own. What removes it is the build support in `@netlify/vite-plugin`: it takes the server bundle a Vite-powered framework emits and turns it into Netlify deployment configuration (we call this the [Frameworks API](https://docs.netlify.com/build/frameworks/frameworks-api/)), _without knowing or caring which framework produced it_. Supporting SolidStart 2 required no SolidStart-specific code and, in fact, no changes at all. This is the same code that’s been [powering TanStack Start on Netlify the past year](https://docs.netlify.com/build/frameworks/framework-setup-guides/tanstack-start/). It’s the direction we’re heading, in collaboration with the Vite team, framework authors, other platforms like Cloudflare, and the broader ecosystem: fewer adapters to maintain, more consistent feature sets across frameworks, and more niche frameworks supported out of the box, helping to support a healthy web ecosystem. ## Resources - [SolidStart 2 announcement](https://github.com/solidjs/solid-start/discussions/2281) - [SolidStart 2 upgrade guide](https://docs.solidjs.com/solid-start/v2/migrating-from-v1) - [SolidStart on Netlify docs](https://docs.netlify.com/build/frameworks/framework-setup-guides/solidstart/) [Permalink to SolidStart 2 just works on Netlify Permalink](/changelog/2026-08-06-solidstart-2-on-netlify/) [Next page](/changelog/page/2)