---
title: "Functions | Netlify Changelog"
description: "Get the latest updates on Netlify products and features to meet your developer needs."
source: "https://www.netlify.com/changelog/tag/functions/"
last_updated: "2026-07-06T07:14:14.000Z"
---
# Posts tagged "Functions"

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/tag/functions/feed.xml)

-   [
    
    ## Functions redesigned for agents
    
    ](/changelog/2026-06-25-functions-redesigned-for-agents/)
    
    June 25, 2026
    
    -   [functions](/changelog/tag/functions/)
    -   [agent runners](/changelog/tag/agent-runners/)
    -   [ai](/changelog/tag/ai/)
    
    We have redesigned Netlify functions for an improved agent experience.
    
    With these updates, functions are more discoverable, easier to autocomplete, update, and manage for people and agents alike. They move function configuration into code, making it type-safe and immediately visible to editors, tools, and agents, with no platform-specific naming conventions to memorize or get wrong. None of these changes are breaking, so you can adopt them on your own timeline.
    
    Netlify Functions are serverless functions that run on-demand in response to HTTP requests or platform events. They handle server-side logic without any infrastructure to manage, and live in your repository at `netlify/functions/`.
    
    To learn more about these updates in depth, check out our [blog on redesigning Netlify functions for agent experience](https://www.netlify.com/blog/netlify-functions-designed-for-agent-experience). See the table below for a summary.
    
    Feature
    
    What changed
    
    What it means for agents
    
    What you need to do
    
    [Event handlers](https://docs.netlify.com/build/functions/overview/#platform-events)
    
    Export typed event handlers from the default export object
    
    Typed handlers are discoverable like any API, with no magic filenames to guess or get wrong.
    
    Nothing required. Adopt the new syntax for new event handlers for better agent discoverability and updates.
    
    [Background functions](https://docs.netlify.com/build/functions/background-functions/)
    
    Declare with `background: true` in config instead of the `-background` filename suffix
    
    Type-safe and config-driven, not name-driven. Agents can set it in code without guessing platform naming conventions, and get an error if the value is wrong.
    
    Nothing required. The `-background` suffix still works.
    
    [Region selection](https://docs.netlify.com/build/functions/configuration/#region)
    
    Set per-function via the `region` config property, replacing the global UI setting
    
    Agents can set region as a type-safe config property, catching invalid values before deploy rather than at runtime. Use deploy previews to test before going live.
    
    Nothing required. Optionally move region out of the UI into config for per-function control.
    
    [Memory and vCPU](https://docs.netlify.com/build/functions/configuration/#memory-or-vcpu)
    
    Set via `memory` or `vcpu` config properties; both values scale together automatically
    
    Agents provisioning compute-heavy workloads (inference, large payloads) can do so in code.
    
    Nothing. Defaults unchanged. Set only if your workload needs more than 1 GB / 0.5 vCPU. Requires a credit-based Pro plan.
    
    [`getContext()`](https://docs.netlify.com/build/functions/api/#getcontext)
    
    Named import from `@netlify/functions`, replacing the `Netlify.context` global
    
    Named imports surface in autocomplete and carry type information. Globals are invisible to agents; named imports are not.
    
    Nothing required. `Netlify.context` still works. Switch to `getContext()` for better discoverability.
    
    Learn more in the [Netlify Functions documentation](https://docs.netlify.com/build/functions/overview/), which has also been recently revamped.
    
    [Permalink to Functions redesigned for agents Permalink](/changelog/2026-06-25-functions-redesigned-for-agents/)
    
-   [
    
    ## Environment variable size limit removed for Serverless Functions
    
    ](/changelog/2026-06-12-serverless-functions-env-var-size-limit-removed/)
    
    June 12, 2026
    
    -   [functions](/changelog/tag/functions/)
    
    You can now use as many environment variables as your Serverless Functions need. The 4KB total size limit on environment variables no longer applies to functions running on the current Netlify Functions runtime.
    
    This limit was a common source of friction. Teams with several API keys, connection strings, or feature flags could quietly bump into the cap and see their functions fail to deploy or run, often with confusing errors. With the limit gone, you no longer have to ration space or work around the ceiling for the configuration your functions legitimately need.
    
    The limit still applies to functions running in Lambda compatibility mode. If your functions are using Lambda compatibility mode and you want to remove the size limit entirely, consider upgrading to the current Netlify Functions runtime.
    
    Learn more about [environment variables in Netlify Functions](https://docs.netlify.com/build/functions/environment-variables/) in our documentation.
    
    [Permalink to Environment variable size limit removed for Serverless Functions Permalink](/changelog/2026-06-12-serverless-functions-env-var-size-limit-removed/)
    
-   [
    
    ## Security Update: DoS vulnerability in Node.js
    
    ](/changelog/2026-01-16-nodejs-async-hooks-dos-vulnerability/)
    
    January 16, 2026
    
    -   [security](/changelog/tag/security/)
    -   [functions](/changelog/tag/functions/)
    
    The Node.js team has released a [security update addressing a denial-of-service vulnerability](https://nodejs.org/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks) affecting applications that use `async_hooks` (including in dependencies). Here’s what Netlify customers need to know.
    
    ## Vulnerability
    
    When `async_hooks` are enabled on certain versions of Node.js, a stack overflow causes the Node.js process to exit immediately rather than throw a catchable error. This bypasses `try-catch` blocks and uncaught exception handlers entirely.
    
    A malicious actor could send a crafted payload to crash a server.
    
    Note that many common tools and frameworks use `async_hooks` under the hood, notably APM and tracing tools (e.g. DataDog, NewRelic, OpenTelemetry) as well as Next.js App Router and other React Server Components implementations. You can find [more details on that here](https://nodejs.org/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks#important-react-and-nextjs-impact-by-version).
    
    ## Impact on Netlify
    
    This is a server-side denial-of-service (DoS) vulnerability. **On Netlify, this has 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 cold starts and your function costs.
    
    Note that Node.js used during your project’s _build_ is not impacted at all.
    
    ## What should I do?
    
    If you have [opted your Netlify Functions into Node.js 18](https://docs.netlify.com/build/functions/optional-configuration/?fn-language=js&data-tab=TypeScript#nodejs-version-for-runtime), we **recommend upgrading to Node.js 20 or later**. Node.js 18 reached end-of-life in April 2025 and thus will not be patched.
    
    Otherwise, there is **no action for you to take**. Although this CVE’s impact to Netlify sites is limited, deployed Netlify Functions will be updated to patched Node.js versions automatically on a rolling basis.
    
    For completeness, please note that [the Node.js version used during your project’s _build_](https://docs.netlify.com/build/configure-builds/manage-dependencies/#nodejs-and-javascript) is not relevant to this CVE. There is no action for you to take and this will not be automatically patched.
    
    ## Resources
    
    -   [Node.js security release announcement](https://nodejs.org/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks)
    -   [Netlify Functions Node.js version configuration](https://docs.netlify.com/build/functions/optional-configuration/?fn-language=js&data-tab=TypeScript#nodejs-version-for-runtime)
    
    [Permalink to Security Update: DoS vulnerability in Node.js Permalink](/changelog/2026-01-16-nodejs-async-hooks-dos-vulnerability/)
    
-   [
    
    ## Observability is here
    
    ](/changelog/2025-12-16-observability/)
    
    December 16, 2025
    
    -   [logs](/changelog/tag/logs/)
    -   [functions](/changelog/tag/functions/)
    
    Netlify Observability offers real-time visibility into your project’s production performance and resource usage.
    
    Monitor requests, bandwidth, runtime behavior, functions, and Edge Functions to understand how your web project operates in production, fix errors, and optimize web performance.
    
    Get a deep feature tour from our [Observability blog post](https://www.netlify.com/blog/introducing-observability-stop-guessing-what-s-happening/).
    
    ## Try Observability
    
    From your project overview, select **Logs & metrics** > **Observability**. To expand details for a request, select a request.
    
    ![Observability dashboard](/images/changelog/observability-dashboard.png)
    
    ## Availability
    
    Observability is available for Credit-based plans and Enterprise plans. If you have a Legacy pricing plan, you can get a sneak peek at your observability data by checking out the widget from your Project Overview.
    
    ![Observability widget on project overview showing past hour of request data](/images/changelog/observability-widget-past-hour.png)
    
    Credit-based plan
    
    Time filter available
    
    Free
    
    Past 24 hours
    
    Personal
    
    Past 7 days
    
    Pro
    
    Past 30 days
    
    Enterprise plan
    
    Time filter available
    
    Any opted-in Enterprise plan
    
    Past 30 days
    
    Note that if you have a Credit-based plan or have Observability enabled for an Enterprise plan, then Function Metrics will no longer be available to you as it is replaced by Observability.
    
    If you do not have Observability, then Function Metrics will continue to be available to you.
    
    Learn more in our [Function metrics](https://docs.netlify.com/manage/monitoring/function-metrics/) docs.
    
    ## Other monitoring updates
    
    As part of monitoring updates, we have also updated the names of some of our monitoring features.
    
    Old name
    
    New name
    
    Real User Metrics
    
    Real User Monitoring
    
    Project analytics (formerly site analytics)
    
    Web analytics
    
    ## Further info
    
    To learn more, check out [Observability docs](https://docs.netlify.com/manage/monitoring/observability/overview).
    
    [Permalink to Observability is here Permalink](/changelog/2025-12-16-observability/)
    
-   [
    
    ## New Netlify-Sentry Integration for Improved Error Monitoring for Functions
    
    ](/blog/sentry-integration/)
    
    February 16, 2023
    
    • Article
    
    -   [functions](/changelog/tag/functions/)
    
    ![](/_astro/75f5d31cb4f0b4f50521e5967f7544af51fab972-2560x1440_1S7Sbp.webp)
    
    Netlify and Sentry provide a powerful combination of tools that help developers build, deploy, and monitor your web projects with ease and accuracy. The latest Sentry integration provides error monitoring for Netlify Functions, Background & Scheduled Functions.
    
    [Permalink to New Netlify-Sentry Integration for Improved Error Monitoring for Functions Permalink](/blog/sentry-integration/)