--- 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/7/" last_updated: "2026-08-05T07:23:34.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) - [ ## Hydrogen with React Router 7 now supported on Netlify ](/changelog/2026-03-24-hydrogen-react-router-7/) March 24, 2026 - [e-commerce](/changelog/tag/e-commerce/) - [remix](/changelog/tag/remix/) - [framework](/changelog/tag/framework/) Shopify’s Hydrogen framework now works on Netlify with React Router 7 and Hydrogen 2026.1.0. The [Netlify Hydrogen template](https://github.com/netlify/hydrogen-template) has been fully rebuilt, and [`@netlify/vite-plugin-react-router`](https://npmx.dev/package/@netlify/vite-plugin-react-router) now supports Hydrogen sites out of the box. The updated template also comes with two meaningful improvements: - **Netlify Cache API integration** — Data fetching is cached using the [Netlify Cache API](https://docs.netlify.com/build/caching/cache-api/), giving you low-latency responses without extra configuration. - **Full local platform emulation** — The Netlify Vite Plugin provides zero-config local emulation of Blobs, Functions, Edge Functions, and AI Gateway during development, so what you test locally matches what runs in production. To get started with a new Hydrogen site on Netlify, deploy the updated template: [![Deploy to Netlify](https://www.netlify.com/img/deploy/button.svg)](https://app.netlify.com/start/deploy?repository=https://github.com/netlify/hydrogen-template) To move an existing Hydrogen site over to Netlify, follow the [How to deploy a Shopify Hydrogen storefront to Netlify](https://developers.netlify.com/guides/how-to-deploy-a-shopify-hydrogen-storefront-to-netlify/) guide. Learn more: - [Hydrogen template on GitHub](https://github.com/netlify/hydrogen-template) - [`@netlify/vite-plugin-react-router` v3.1.0 release notes](https://github.com/netlify/remix-compute/releases/tag/vite-plugin-react-router-v3.1.0) - [How to deploy a Shopify Hydrogen storefront to Netlify](https://developers.netlify.com/guides/how-to-deploy-a-shopify-hydrogen-storefront-to-netlify/) [Permalink to Hydrogen with React Router 7 now supported on Netlify Permalink](/changelog/2026-03-24-hydrogen-react-router-7/) - [ ## Monitor credit usage by day ](/changelog/2026-03-24-monitor-credit-usage-by-day/) March 24, 2026 - [workflow](/changelog/tag/workflow/) Users on credit-based plans can now see a day-by-day breakdown of their credit consumption. Head to **Usage & Billing** > **Account usage insights** > **Credits** to view exactly how your credits are being used each day. Track credit usage across the following [meters](/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/#credits-usage-for-metered-billing): - AI Inference - Bandwidth - Compute - Production deploys - Web Requests ![Day-by-day credit usage breakdown in the Netlify UI](/images/changelog/credit-usage-per-day.png) This makes it easier to spot usage trends, identify spikes, and plan ahead — so you can stay on top of your credit consumption without any guesswork. Learn more about [how credits work](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/). [Permalink to Monitor credit usage by day Permalink](/changelog/2026-03-24-monitor-credit-usage-by-day/) - [ ## Invoices for Enterprise Available on the Billing Page ](/changelog/2026-03-20-invoices-for-enterprise-available-on-billing-page/) March 20, 2026 Enterprise and Grid customers can now find issued invoices directly on their billing pages in Netlify. You can review what each invoice includes and open it right away to pay or download. On the team **Usage & billing** page for Enterprise and the Organization billing page for Grid, invoices are now listed where billing work already happens. This makes it faster to confirm charges, get details, and handle payment or download in fewer steps. **Enterprise teams without an organization grid plan:** Find your invoices in your team’s **Usage & billing** dashboard. ![Issued invoices on the Enterprise team's Usage & billing dashboard](/images/changelog/enterprise-invoices-billing-page-breakdown.png) **Enterprise plans with an organization grid plan:** Find invoices on your Organization’s billing dashboard. ![Issued invoices on the Organization's billing dashboard](/images/changelog/organization-invoices-billing-page.png) You can quickly see a breakdown for each invoice and use the **Pay** button to open the invoice portal when you’re ready to take action. This update affects Enterprise teams and Grid organizations. No setup is required. Learn more about [Netlify billing](https://docs.netlify.com/manage/accounts-and-billing/billing/). [Permalink to Invoices for Enterprise Available on the Billing Page Permalink](/changelog/2026-03-20-invoices-for-enterprise-available-on-billing-page/) - [ ## Start Netlify projects from a prompt ](/blog/start-a-netlify-project-from-a-prompt/) March 18, 2026 • Article ![](/_astro/5293a537cecbb67d7be139f1857bdcaad387fb84-1200x675_phBOH.webp) Build and ship web apps faster with AI and Netlify. Start with a prompt, use production infrastructure, and grow without rebuilding. [Permalink to Start Netlify projects from a prompt Permalink](/blog/start-a-netlify-project-from-a-prompt/) - [ ## Introducing Prompt Templates ](/changelog/2026-03-18-prompt-templates/) March 18, 2026 - [agent runners](/changelog/tag/agent-runners/) - [workflow](/changelog/tag/workflow/) To help you and your agents build more effectively, we’re introducing reusable Prompt Templates available directly from within Netlify. Browse a [curated collection of reusable prompts](https://docs.netlify.com/prompt-templates/browse/) for common Netlify workflows: accessibility audits, A/B testing with Edge Functions, and more. Each template uses variable placeholders so you can adapt it to your project without starting from scratch. Prompt Templates live directly in your project’s [agent runs dashboard](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). From there you can: - **Browse** public prompt templates - **Customize and save** your own versions of any template for your team - **Submit templates** back to the community to share what is working for you Learn more about [managing Prompt Templates](https://docs.netlify.com/prompt-templates/manage/) for your team. [Permalink to Introducing Prompt Templates Permalink](/changelog/2026-03-18-prompt-templates/) - [ ## OpenAI GPT-5.4 Nano and GPT-5.4 Mini Now Available in AI Gateway ](/changelog/2026-03-17-gpt-5-4-nano-mini-ai-gateway/) March 17, 2026 - [ai gateway](/changelog/tag/ai-gateway/) OpenAI’s GPT-5.4 Nano and GPT-5.4 Mini models are 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.4 Nano model: ``` import OpenAI from 'openai'; export default async () => { const openai = new OpenAI(); const response = await openai.responses.create({ model: 'gpt-5.4-nano', input: 'Give a concise explanation of how AI works.', }); return Response.json(response);}; ``` GPT-5.4 Nano and GPT-5.4 Mini are 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.4 Nano and GPT-5.4 Mini Now Available in AI Gateway Permalink](/changelog/2026-03-17-gpt-5-4-nano-mini-ai-gateway/) - [ ## New Internal Builder role and granular project access controls ](/changelog/2026-03-16-internal-builder-role/) March 16, 2026 We’ve updated how you manage who can access what on your Netlify project and created a new role designed for the workflow needs of cross-functional AI-assisted builders. Teams have asked for clearer ways to support people building internal tools and people collaborating on existing projects with AI agents and some guardrails. With the new Internal Builder role and more granular project access control, Netlify now better supports new ways of working with AI across your cross-functional teams. ## Introducing the Internal Builder role This role is ideal for marketers building campaign pages, HR teams spinning up internal sites, or anyone using AI tools to ship without a traditional dev workflow. The **Internal Builder** role is built to cover these two use cases: - [Build with Agent Runners with guardrails](#build-with-agent-runners-with-guardrails) for existing projects - [Support internal tool builders](#support-internal-tool-builders) with their new projects ### Build with Agent Runners with guardrails Internal Builders can use Agent Runners to build and iterate on web projects with guardrails that support the ways cross-functional teams work. The Internal Builder role can iterate on existing web projects using Agent Runners but cannot publish directly to production or access Project configuration settings, such as to change environment variables. This ensures the Internal Builder doesn’t accidentally break existing functionality. For projects connected to a Git provider, the Internal Builder can open a pull request for review from their agent run. This allows Developers and Owners to decide when to go live with changes. Use cases supported: - Marketing team member who needs to build campaign landing pages quickly with stakeholder review - Designer who iterates on pricing page with AI assistance with stakeholder review ### Support internal tool builders Once someone with an Internal Builder role creates a project, they automatically get a Developer role on that project without changing their role and access permissions to other projects. This allows your cross-functional teams to own the building process for their internal tools. Use cases supported: - HR team member who wants to build an information site for a company trip to Mexico - Sales rep building internal tools for their team ## New granular project access We’ve upgraded the ways you can manage project access for your team members. Team Owners can specify project access when adding team members to projects or when they edit existing project access. They can assign a role scoped only to specific projects or to all projects (including future ones). This means the same person can be an Internal Builder on most projects but a Developer on the internal tool they’ve created. Access can be scoped to exactly what each person needs. For more details, check out our docs on [Roles and permissions](https://docs.netlify.com/manage/accounts-and-billing/team-management/roles-and-permissions) and [Manage project access](https://docs.netlify.com/manage/accounts-and-billing/team-management/manage-project-access). ## Try it out To add an Internal Builder to your team, go to your team’s Members page and invite a new member or update an existing member’s role. Let us know if you have any [feedback](https://www.netlify.com/contact/sales/). [Permalink to New Internal Builder role and granular project access controls Permalink](/changelog/2026-03-16-internal-builder-role/) - [ ## See your available credits at a glance ](/changelog/2026-03-11-display-available-credits/) March 12, 2026 - [workflow](/changelog/tag/workflow/) ![Monitor credit usage in the Netlify UI](/images/changelog/monitor-credit-usage.png) We’ve updated how credits are displayed across the Netlify UI. Instead of showing a “used credits / total credits” counter, you’ll now see your **available credits** — the number of credits you actually have left to use. Now, you’ll see exactly how many credits remain on your account without needing to do the math yourself. For a detailed breakdown of your monthly credit consumption, check the **Credit usage breakdown** card on your team’s billing page. Learn more about [how credits work](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/). [Permalink to See your available credits at a glance Permalink](/changelog/2026-03-11-display-available-credits/) - [ ## Astro 6 just works on Netlify ](/changelog/2026-03-10-astro-6/) March 10, 2026 - [framework](/changelog/tag/framework/) - [astro](/changelog/tag/astro/) [Astro 6](https://astro.build/blog/astro-6/) is out today, and it just works on Netlify on day one. To upgrade, run: ``` npx @astrojs/upgrade ``` This will update Astro, the [Netlify adapter](https://docs.netlify.com/frameworks/astro/), and all other official integrations together. ## What’s new Some highlights include: - **Vite 7 and a redesigned dev server** — Faster builds and a better dev server built from the ground up. - **Content Layer API** — Legacy content collections are fully removed. All collections must now use the [Content Layer API](https://docs.astro.build/en/guides/content-collections/). - **Node 22** — Node 18 and 20 are no longer supported. Check the full [upgrade guide](https://docs.astro.build/en/guides/upgrade-to/v6/) for all the details. ## Watch out for import.meta.env One change worth calling out: `import.meta.env` values are now **always inlined at build time** in Astro 6. This means if you were relying on `import.meta.env` to read environment variables at runtime in your server-side code, those values will be baked into your build output instead. To read environment variables at runtime, use `process.env` instead: ``` - const apiKey = import.meta.env.API_KEY;+ const apiKey = process.env.API_KEY; ``` This is especially important for secrets. If a secret is inlined into your server bundle, it’s no longer secret. The good news: Netlify’s [smart secret scanning](https://docs.netlify.com/manage/security/secret-scanning/) will automatically detect exposed secrets in your build output and fail the build before it goes live, so you’ll know right away if something slipped through. ## Deploy an Astro 6 site on Netlify If you want to get started with a new site, start with the [Astro on Netlify](https://docs.netlify.com/build/frameworks/framework-setup-guides/astro/) doc, or just click this button: [![Deploy to Netlify](https://www.netlify.com/img/deploy/button.svg)](https://app.netlify.com/start/deploy?repository=https://github.com/netlify-templates/astro-platform-starter) [Permalink to Astro 6 just works on Netlify Permalink](/changelog/2026-03-10-astro-6/) [Previous page](/changelog/page/6) [Next page](/changelog/page/8)