dagster-io/dagster 1.11.11

1.11.11 (core) / 0.27.11 (libraries)

on GitHub

New

• anthropic, mcp, and claude-code-sdk dependencies of dagster-dg-cli are now under a separate ai extra, allowing dagster-dg-cli to be installed without these dependencies.
• Added AutomationCondition.all_new_updates_have_run_tags and AutomationCondition.any_new_update_has_run_tags, which allows automation conditions to be filtered to partitions that have been materialized since the last tick from runs with certain tags. This condition can be used to require or prevent certain run tags from triggering downstream declarative automation conditions. These conditions are similar to AutomationCondition.executed_with_tags, but look at all new runs since the most recent tick instead of just looking at the latest run.

Bugfixes

• Fixed a bug which would cause steps downstream of an asset with skippable=True and a blocking asset check to execute as long as the asset check output was produced, even if the asset output was skipped.
• When a backfill fails, it will now cancel all of its in-progress runs before terminating.
• Fixed an issue that would cause trailing whitespace to be added to env vars using dot notation ({{ env.FOO }}) when listing the env vars used by a component. (Thanks, @edgarrmondragon!)
• Fixed issue that would cause errors when using multi to single partition mappings with DbIOManagers.
• [ui] Fixed issue with the "Report materialization" dialog for non-partitioned assets.
• [ui] Typing large YAML documents in the launchpad when default config is present is now more performant.
• [ui] Fixed an issue where setting a FloatMetadataValue to float('inf') or float('-inf') would cause an error when loading that metadata over graphql.
• [ui] The "Clear" button in the dimension partition text input for multi-partitioned assets now clears invalid selections as expected.
• [dagster-dbt] Fixed an issue with the DbtCloudWorkspaceClient that would cause errors when calling trigger_job_run with no steps_override parameter.