- Added a new blocking parameter for freshness checks, raised the default gRPC request/response limit to 100 MB, introduced Definitions.map for asset spec transformations and stricter partition‑mapping validation.
- Improved reliability of PipesK8sClient log streaming and Dagster Cloud job launches; merged dagster‑components into dagster and added dg.toml support with updated scaffolding conventions.
- Fixed numerous bugs across run monitoring, UI filters, Fivetran integration, AutomationCondition tagging, and Pydantic compatibility, and announced deprecation of the dg.library entry point.
1.10.10 (core) / 0.26.10 (libraries)
Official Dagster changelog summary with source attribution, release tags, and community reactions.
Track this Dagster release note alongside related changelog updates, risky changes, and weekly digest signals from the developer community.
Verify the original release note
Every summary should remain traceable to the original changelog or release source.
Follow this in context
Turn this Dagster release note into a weekly digest for the tools you actually use.
Create digestMore Dagster changelog updates
Added an expand/collapse all toggle to the automation condition evaluation table in the UI
Asset health now reports a warning status (instead of degraded) when all failed partitions are pending automatic retry, with updated popover and alert messages.
Asset health now reports WARNING for pending retries and UI gains search improvements, copy key action, and SLURM tag icon