Databricks releases, every cloud
| Release | Date | ||||
|---|---|---|---|---|---|
| Databricks Runtime maintenance updates (07/24) Includes bug fixes, security patches, and performance improvements for versions 13.3 to 18.2. | On AWS, read it on their docs | On Azure, read it on their docs | On GCP, read it on their docs | Not on SAP | Jul 24, 2026 |
| Databricks Runtime 18 and Databricks Runtime 18 for Machine Learning have transitioned to LTS Receives 3 years of stability and security fixes. | On AWS, read it on their docs | On Azure, read it on their docs | On GCP, read it on their docs | Not on SAP | Jul 23, 2026 |
| Databricks Runtime 19: July 23, 2026 Enables Arrow-optimized Python UDFs by default, changing type-coercion behavior. | On AWS, read it on their docs | On Azure, read it on their docs | On GCP, read it on their docs | Not on SAP | Jul 23, 2026 |
| Warehouse-level statement timeouts (Beta) Set via statement_timeout field in Create or Update warehouse APIs. | On AWS, read it on their docs | On Azure, read it on their docs | On GCP, read it on their docs | Not on SAP | Jul 21, 2026 |
- Databricks Runtime maintenance updates (07/24)
Includes bug fixes, security patches, and performance improvements for versions 13.3 to 18.2.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Databricks Runtime 18 and Databricks Runtime 18 for Machine Learning have transitioned to LTS
Receives 3 years of stability and security fixes.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Databricks Runtime 19: July 23, 2026
Enables Arrow-optimized Python UDFs by default, changing type-coercion behavior.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Warehouse-level statement timeouts (Beta)
Set via statement_timeout field in Create or Update warehouse APIs.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud)
Headlines, dates and product areas are Databricks' own, and every item links to the note it came from. The one-line summaries are ours.