1.10.0 (core) / 0.26.0 (libraries)

New

• Added a new AutomationCondition.data_version_changed() condition.
• [dagster-msteams] Added support for sending messages to PowerAutomate flows using AdaptiveCard formatting.
• dagster definitions validate is now less verbose, primarily highlighting load errors.
• [ui] Made defunct code locations removable when editing environment variables.
• [ui] Added a warning icon to the Agents item in Deployment settings, indicating when there are no active agents.
• [dagster-tableau] Changed logic to show embedded data sources in case published data sources are not present. Also, pulled more metadata from Tableau. (Thanks @VenkyRules!)
• Added new decorators to reflect our new API lifecycle: @preview, @beta and @superseded. Also added new annotations and warnings to match these new decorators.

Bugfixes

• [ui] Fixed persistence of the group-by setting in the run timeline view.
• [ui] Fixed timestamped links to asset pages from asset check evaluations in run logs.
• [ui] Fixed excessive rendering and querying on the Concurrency configuration page.
• Fixed the step stats calculations for steps that fail and request a retry before the step starts. This happened if a failure occurred in the step worker before the compute function began execution. This should help with sporadic hanging of step retries.
• Fixed an issue where the Concurrency UI was broken for keys with slashes.
• Fixed an issue with emitting AssetResult with ops or multi-assets that are triggered multiple times in the same run.
• [dagster-dbt] Fixed a bug introduced in dagster-dbt 0.25.7 that would cause execution to fail when using the @dbt_assets decorator with an io_manager_key specified.
• [dagster-dbt] Refactored UnitTestDefinition instantiation to address failure to initialize dbt models with unit tests. (Thanks @kang8!)
• Fixed issue where dagster instance migrate was failing for instances with tables having non-empty concurrency limits.
• Fixed an issue where Declarative Automation sensors in code locations that included source assets referencing assets with automation conditions in other code locations would sometimes cause duplicate runs to be created.
• Turned on run blocking for concurrency keys/pools by default. For op granularity, runs are dequeued if there exists at least one op that can execute once the run has started. For run granularity, runs are dequeued if all pools have available slots.
• [dagster-dbt] Added pool support.
• [dagster-dlt] Added pool support.
• [dagster-sling] Added pool support.

Documentation

• Corrected docs on managing concurrency.
• Fixed a Markdown link to "assets metadata." (Thanks @rchrand!)
• Fixed a pip install command for Zsh. (Thanks @aimeecodes!)

Breaking Changes

• The include_sources param on all AssetSelection APIs has been renamed to include_external_assets.

• Disallowed invalid characters (i.e. anything other than letters, numbers, dashes, and underscores) in pool names.

• Changed the default run coordinator to be the queued run coordinator. This requires the Dagster daemon to be running for runs to be launched. To restore the previous behavior, you can add the following configuration block to your dagster.yaml:

  run_coordinator:
    module: dagster.core.run_coordinator.sync_in_memory_run_coordinator
    class: SyncInMemoryRunCoordinator
  

Deprecations

• [dagster-sdf] Moved the dagster-sdf library to the community-supported repo.
• [dagster-blueprints] Removed the dagster-blueprints package. We are actively developing a project, currently named Components, that has similar goals to Blueprints of increasing the accessibility of Dagster.
• Removed the @experimental decorator in favor of the @preview and @beta decorators. Also removed annotations and warnings related to the @experimental decorator.

Dagster Plus

• Shipped a range of improvements to alerts in Dagster+, including more granular targeting, streamlined UIs, and more helpful content. Stay tuned for some final changes and a full announcement in the coming weeks!