Releasesby GlyphRoll back one bundle to an earlier version
Each bundle on a Deployment now records a version history, and you can roll one bundle back to a version in that history. Your project image, your Astro Runtime version, and every other bundle stay as they are. Previously, the only way to undo a change to one bundle was to roll back the whole Deployment.
Also shipped Nov 2, 2026Astronomer in November 2026 →
Managed warehouse for MLflow (Beta)
Managed warehouse for MLflow is available in Beta, enabling users to view Unity Catalog traces in the MLflow UI without manually choosing a SQL warehouse.
Check out GitHub code without long-lived credentials on self-hosted agents
Self-hosted agents can now use temporary, read-only GitHub App tokens for repository checkout. This eliminates the need to distribute and rotate long-lived SSH keys or personal access tokens across your agent fleet.
Serving tuned Gemini 3.x models on global endpoints
Serving tuned Gemini 3.x models on global endpoints is available in General Availability (GA) . You can copy fine-tuned Gemini 3.x models to the global region using the Model Registry models:copy API, deploy them to global serving endpoints, and send inference requests directly to aiplatform.googleapis.com .
[Launched] Generally Available: Change from virtual network integration to a private endpoint capable network configuration in Azure Database for PostgreSQL flexible server
You now have greater flexibility in network design for Azure Database for PostgreSQL Flexible Server workloads. Now you can change existing VNet-integrated servers from delegated-subnet networking to a private endpoint-capable configuration, enabling secu
[Launched] Generally Available: Restart databases in Azure SQL DB via the Azure portal
You can now restart or fail over databases directly from the Azure portal, including single databases, Hyperscale databases, and databases in elastic pools, without writing scripts against the Rest API or contacting support. Learn more.
Lakehouse caching for cross-cloud data access is generally available (GA)
Lakehouse caching for cross-cloud data access is generally available (GA). Cross-cloud caching is disabled by default. You can opt in to caching on a Lakehouse federated catalog or a BigQuery cross-cloud connection to cache remote files in your Google Cloud region. This helps reduce cross-cloud egress costs and accelerate subsequent queries.
More from AstroEvery Astro release →
View Astro Runtime upgrade progress in the Astro UI
The Astro UI now provides a progress card and dedicated logs for Airflow database migrations during runtime upgrades.
The Astro v1 Labs API includes every Astro API v1 endpoint
The Astro v1 Labs API now serves all standard v1 endpoints under a unified base URL. This allows integrations to use a single base URL for both Labs and production endpoints.
Additional improvements
Users can now create AWS dedicated clusters in the eu-west-3 (Paris) region.
Deployment hibernation is generally available
Deployment hibernation is now generally available on Astro, allowing users to scale development deployment resources to zero on a schedule or on demand.
Astro-managed object storage for XCom and state values
Astro now stores XCom and task state values larger than 64 KB in an Astro-managed object storage bucket instead of the Airflow metadata database for improved performance.
Subscribe to upcoming changes for your Astro plan
Astronomer now publishes notices about planned changes to Astro, such as maintenance windows and control plane changes, on a separate Upcoming changes page for each Astro plan. Each plan also has its own RSS feed, so you receive only the notices that affect your Organization.
Additional improvements
- You can now turn on Development Mode for an existing Deployment from the Deployment settings in the Astro UI, regardless of your plan. Turning it on sets the scheduler size to Small and turns off high availability (HA). Turn the setting back off before you save to restore your original scheduler size and HA settings.
Deploy code to multiple Dag bundles
On an Airflow 3 Deployment, you can now split your code into named Dag bundles that you deploy and version independently. Each bundle keeps its own version history, and deploying to one bundle replaces only that bundle's contents, so teams and repositories that share a Deployment no longer have to carry each other's code on every deploy.