- Run status sensors can now monitor all runs across the Dagster instance (monitor_all_repositories=True) and the run key on RunRequest/partition is optional.
- Dagit UI improvements: delete runs directly from the run page, run timeline includes ad‑hoc asset materializations, backfill and asset observation tables have fixes and collapsible rows.
- Numerous bug fixes (multi‑asset sensor cursor, partition offset handling, k8s job executor env‑var args, duplicate asset keys, compute log links) and added docs for graph‑backed asset subsetting.
1.0.10 (core) / 0.16.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