Releasesby GlyphMultiple Dag bundles are generally available
Deploying code to multiple named Dag bundles is now generally available on Astro for Airflow 3 deployments. Teams can independently deploy, version, and roll back code bundles on shared deployments using the Astro UI, CLI, or API.
Also shipped Nov 13, 2026Astronomer in November 2026 →
AI Function task support in Declarative Automation Bundles (Beta)
Databricks introduced Beta support for AI Function tasks within Declarative Automation Bundles.
Give agents only the access they need
Buildkite released token permissions and queue scopes for agent tokens, allowing teams to restrict agent capabilities and limit job acceptance to specific queues.
Many-to-many relationships in semantic views (Preview)
Snowflake Cortex AI launched a public preview for modeling many-to-many relationships between logical tables within semantic views.
BigQuery connections for MySQL, Oracle, and PostgreSQL are in preview
Google Cloud introduced BigQuery federated query connections to MySQL, Oracle, and PostgreSQL in public preview.
Upcoming deprecation of selected GitHub Copilot models in December
GitHub announced the upcoming deprecation of several Copilot models on December 14, 2026, including Claude Fable 5, Gemini 3.8 Flash, and Grok 4.6.
Aurora PostgreSQL with express configuration now supported in CloudFormation
AWS added support for Aurora PostgreSQL express configuration in CloudFormation, enabling single-property automated cluster creation and faster serverless database setup.
More from AstroEvery Astro release →
Automate work with Otto Routines
Otto Routines run Otto unattended when a Dag fails or on a schedule, and send the result to your email and Slack notification channels. You can write your own instructions or start from one of the managed Routines that Astronomer maintains: Investigate Dag failures and Daily ops report . To create a Routine, go to Build > Routines in the Astro UI.
Set Astro AI spend limits for users and API tokens
You can now set a monthly Astro AI spend limit for each user and each API token in your Organization, in addition to the Organization total spend limit: The Per-User spend limit and the Per-API Token spend limit apply to every user and API token that doesn't have a limit of its own.
API server autoscaling is generally available
API server autoscaling for Airflow 3 deployments is now generally available. It automatically adjusts replicas based on CPU utilization.
Run GPU workloads with the KubernetesPodOperator
Astronomer Astro now supports executing GPU workloads on AWS by requesting NVIDIA GPU node pool resources within KubernetesPodOperator tasks.
Roll 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.
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.