Releasesby GlyphAdditional improvements
- Updated Astro infrastructure to improve reliability and performance.
Also shipped Jul 1, 2026Astronomer in July 2026 →
Fivetran Context Layer is in public preview
Context Layer builds a context layer from documentation sources, systems of record and analytical sources, then connects it to an organization's AI coding and chat tools.
Fivetran sunsets the AVEVA PI and Delighted connectors
New AVEVA PI and Delighted connections are blocked from July 1, 2026. Existing AVEVA PI connections stop syncing July 23, 2026, and Delighted connections are paused after the Delighted API deprecation.
Fivetran Move a Connection REST API endpoint enters beta
A new beta endpoint moves connections from one destination group to another.
Workload identity federation for Snowflake workloads that access external services (General availability)
Snowflake can now act as the OpenID Connect (OIDC) provider when Snowflake workloads authenticate to external services. To use this capability, create a secret of type WORKLOAD_IDENTITY_FEDERATION and share its issuer URL and subject identifier with the external service to establish trust.
Veeva Vault connector (Beta)
The Veeva Vault connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. The connector uses Veeva's Direct Data API to ingest all standard objects, custom objects, system tables, and audit trail tables from your Vault instance into Databricks.
MySQL integrated CDC pipeline is now in Beta
The integrated CDC pipeline for MySQL is now in Beta . An integrated CDC pipeline ingests change data from MySQL into Databricks using a single pipeline, combining extraction and application into one pipeline update. Unlike the standard gateway-based architecture, an integrated CDC pipeline requires no separate ingestion gateway.
More from AstroEvery Astro release →
New Deployment analytics experience
Astro now offers a new version of the Deployment analytics experience with expanded Airflow visibility, including API server and webserver metrics, Dag processor coverage, Kubernetes executor and KubernetesPodOperator coverage, parse time, and richer per-status and per-component breakdowns.
Enable Sub-Second Pipelines
You can now enable Sub-Second Pipelines on Airflow 3.2+ Deployments that use the Astro executor . Sub-Second Pipelines pair the Astro executor with a dedicated event-driven Event Scheduler that picks up and dispatches API-triggered Dag runs in under a second and sustains approximately 1,000 Dag runs per minute, where the Celery executor queues and falls...
Test against an existing Deployment in the Astro IDE
You can now test code in the Astro IDE against an existing Astro Deployment in your Workspace, instead of only an ephemeral test Deployment. Testing against an existing Deployment reuses its configuration, connections, and resources, and skips provisioning a new environment.
Review code with Otto
You can now use Otto to review your Airflow code automatically when you open a pull request or merge request. The Otto review action posts a sticky summary comment, adds inline comments where it finds issues, and offers commit suggestions where a concrete fix is available.
Try the new Astro experience
Astro's navigation now gives you a single view across your entire Organization instead of a single Workspace. Deployments, Dags, and Astro IDE projects all appear across Workspaces in one view, with Workspace context on every row. Filter to a specific Workspace when you need to, or work from the full picture across your Organization.
Additional improvements
- When you add the first IP address range to your organization's IP access list, the Astro API now rejects the request with a 400 Bad Request error if your current IP address falls outside the submitted ranges, which prevents you from accidentally locking yourself out.
Investigate Dag failures with Otto
You can now use Otto to investigate Dag failures on Astro from the Astro UI, Astro alerts, or the Astro API. Each investigation produces a structured diagnosis with a root cause type, severity, suggested fix, and a checklist of Dag- and task-level checks, drawing on Airflow, Astro, and Astro Observe context.
Dag-level access control is generally available
Dag-level access control is now generally available. You can assign roles scoped to individual Dags within a Deployment to enforce least-privilege security and enable multiple teams to collaborate in a single Deployment without exposing Dags across team boundaries.