Releasesby GlyphWhat's new in Sigma
Admin Add a key file for Snowflake key pair connections When configuring a Snowflake connection, you can add a PKCS#8-formatted key file ( .p8 ) instead of pasting your private key when setting up key pair authentication for the connection or an OAuth service account. For more details, see Connect to Snowflake .
Also shipped Nov 21, 2025Sigma Computing in November 2025 →
Dataflow now supports speculative execution for batch pipelines
Dataflow now supports speculative execution for batch pipelines. This feature mitigates the impact of slow-running tasks ( stragglers ) by launching a redundant execution of these tasks. The first task to finish is used, and the other is canceled, which can improve the overall completion time of your pipeline. This feature is generally available.
Containers - New CPU Pricing for Containers and Sandboxes
Containers and Sandboxes pricing for CPU time is now based on active usage only, instead of provisioned resources. This means that you now pay less for Containers and Sandboxes. An Example Before and After Imagine running the standard-2 instance type for one hour, which can use up to 1 vCPU, but on average you use only 20% of your CPU capacity.
Notifications, Conductor Queue
This week is all about staying ahead of issues: Notifications graduate from Priority Boarding to General Availability, giving everyone a real-time view of what’s happening across projects and environments. There’s also a new way for our community Conductors to triage questions faster.
Projects deployed using a zip file via API now support branch deploys
When you deploy a project using a ZIP file and the Netlify API, you can now also create branch deploys using the new branch parameter. While it was always possible to pass a branch parameter to the https://api.netlify.com/api/v1/sites/{site_id}/builds endpoint, it previously had no effect for deploys made programmatically using the API.
Faro Web SDK v2.0 is now GA
This major release brings new updates to User Actions for GA, introduces improvements to Web Vitals, simplifies configuration, cleans up deprecated internals, and adds experimental navigation instrumentation for soft navigations. Highlights: User Actions are now GA Additional configuration to manage action state Added an importance attribute (e.g.
Custom environments for EAS Environment Variables
EAS Environment variables now support custom environments on top of the default development, preview, production. Available for production and Enterprise plans.
More from SigmaEvery Sigma release →
What's new in Sigma
Admin Audit log support for GCP KSA region Sigma now supports audit log events for organizations hosted in the GCP KSA (ME Central 2) region. For a list of all supported regions, see Enable or disable audit logging .
What's new in Sigma
AI Ask Sigma supports data model relationships and Snowflake semantic views When Ask Sigma responds to questions with a data model or Snowflake semantic view, Ask Sigma can join related tables to provide higher-quality answers. For more details, see Ask natural language queries with Ask Sigma .
What's new in Sigma
Data apps If/else control flow in action sequences (GA) If/else control flow is now generally available. Use if/else statements to create dynamic workflows within action sequences. If/else control flow adds flexibility to a sequence by allowing it to check one or more conditions and execute actions for the first condition that evaluates to true.
What's new in Sigma
Admin Enable multiple identity providers for your organization (Beta) You can now enable multiple identity providers (IdPs) for your Sigma organization. If you would like to enable multiple IdPs for your organization, please contact Sigma support. For more information, see Using multiple identity providers for your Sigma organization (Beta) .
What's new in Sigma
Admin Enable a unique SAML SP entity ID (Beta) When setting up SAML-based authentication for a Sigma organization, you can now assign a unique service provider (SP) entity ID for the SAML configuration. With the unique entity ID for Sigma as an SP, you can configure your IdP to allow SAML authentication to multiple Sigma organizations.
What's new in Sigma
Admin Account type permissions for reports The following account type permissions are now available to enable access to reports: View reports : Enables users to view reports shared with them. Create, edit, and publish reports : Enables users to create new reports, manage existing ones, and share published versions.
What's new in Sigma
API Impersonate a user in API calls (Beta) A user assigned the Admin account type can impersonate other users in API calls, for example to retrieve and display the contents of their My Documents folder in embedded content. For more details and an example test Python script, see Impersonate users .
What's new in Sigma
Admin IP Allowlist for UI/Application (GA) You can configure an IP allowlist for the Sigma UI. After enabling the allowlist, you can add individual IP addresses or ranges of addresses in CIDR notation. Only users in the allowlist are able to access the Sigma application through the user interface. For more information, see Restrict access to Sigma by IP .