Data and AI releases

811 this month · 176 companies

DeepSeek V4 Pro (0813) is scheduled for retirement

DeprecationNot yet verified

DeepSeek V4 Pro (0813) will be retired on October 30, 2026. DeepSeek V4.1 Flash is the recommended replacement. See Deprecated and retired models for migration guidance.

Read on docs.databricks.com

Also shipped Sep 23, 2026Databricks in September 2026 →

More ways to request and configure Copilot code reviews

GitHub Copilot code review now offers additional personal configurations to an expanded set of Copilot plans and an enterprise-level default setting. These improvements are now generally available: A dedicated personal settings page for automatic review and your default review effort An enterprise-wide default review effort setting for organization-owned...

GA
Source ↗

Node 20 is no longer available in GitHub Actions

This is the final notification that Node 20 is no longer available on GitHub Actions runners. Runners now use Node 24 for JavaScript actions. The temporary ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION opt-out is no longer available. If you maintain a JavaScript action, update its runs.using value to node24 and publish a new release as soon as possible.

Deprecation
Source ↗

Unlimited Vercel Blob stores on every plan

You can now create as many Vercel Blob stores as you need. The previous limits of 100 stores on Hobby, 500 on Pro, and 1,000 on Enterprise no longer apply. Blob store creation is now billed alongside other Blob Advanced Operations , including put() , copy() , and list() calls. On Pro that's $5.00 per million.

Preview
Source ↗

More from Databricks Data Intelligence PlatformEvery Databricks Data Intelligence Platform release →

Bundled BigQuery JDBC driver removal in Databricks Runtime 20

Starting with Databricks Runtime 20, Databricks Runtime no longer includes the bundled BigQuery JDBC driver, while Databricks Runtime 19 and earlier continue to include it. Classic compute workloads that use Spark JDBC with a jdbc:bigquery: URL fail with a driver-not-found error unless a BigQuery JDBC driver is installed.

Update
Source ↗

The query history system table is now generally available

The system.query.history system table is now generally available. Use it to access account-wide records for queries run on SQL warehouses or serverless compute, including execution status, duration metrics, and query source. See Query history system table reference .

GA
Source ↗