Dagster 1.13.12 was published on July 2, 2026, with fixes that matter most to automated orchestration, dbt event conversion, and code location recovery. The main operational change is a fix for partitioned asset checks that could halt an automation tick when the target asset was not materialized in the same tick. This core release is paired with library version 0.29.12 and is not marked as a prerelease.

Dagster 1.13.11, published on June 25, 2026, is a focused scheduler and data engineering release for larger asset graphs, dbt metadata, and GraphQL clients. The main operator change is bounded GraphQL selection data for runs, which helps API consumers show asset and check scope without reading more run data than they need. This release is not marked as a prerelease.

Dagster is a Python data orchestration project, and this activity window is more about runtime reliability than a headline feature. Across 21 recent commits, the useful changes sit in event log writes, declarative automation for asset checks, Dagster Cloud agent recovery, and AWS EMR Serverless pipes.

The Dagster project released version 1.13.9 on June 11, 2026, bringing a significant structural update to the asset graph and selection logic. This release introduces hierarchical asset groups, new filtering capabilities for asset types, and scaling improvements for deployments running on Kubernetes through Helm.

Dagster version 1.13.7 was published on May 28, 2026, bringing critical security patches for ClickHouse integrations and refinements to asset check execution. This release also updates the Kubernetes Helm chart to improve how run pods inherit security configurations from the deployment environment.