dagster-io/dagster 1.10.7

1.10.7 (core) / 0.26.7 (libraries)

on GitHub

New

• Applying changes from sensor test results now also applies changes from dynamic partition requests.
• When merging assets from multiple code locations, autogenerated specs are now prioritized lower than customized external asset specs.
• [ui] Allowed using command-click to view a run from the toast message that appears when starting a materialization of an asset.
• [ui] Asset graph can now zoom out a lot more.
• [ui] Added a kind tag for dbt Cloud.
• [dagster-dlt] Added backfill policy to dlt_assets, defaulting to single-run. (Thanks @neuromantik33!)

Bugfixes

• Updated AutomationCondition.initial_evaluation condition to become true for all partitions of an asset whenever the PartitionsDefinition of that asset changes, rather than whenever the structure of the condition changes.
• Fixed a bug with several integrations that caused data fetched from external APIs not to be properly cached during code server initialization, leading to unnecessary API calls in run and step worker processes. This affected dagster-airbyte, dagster-dlift, dagster-dbt, dagster-fivetran, dagster-looker, dagster-powerbi, dagster-sigma, and dagster-tableau.
• [ui] Fixed an issue with the Run step selection input autocomplete where it would suggest key:"*substring*" instead of name:"*substring*".
• [ui] Fixed the "View run" link shown when launching runs.
• [ui] Fixed an issue where updating a catalog view caused an infinite loading state.
• Fixed an issue which could cause asset check evaluations emitted from the body of the op to not impact the check status of an asset in the UI.
• Fixed an issue that could cause an asset backfill created by re-executing another backfill from the point of failure to error on the first tick in rare cases.
• Fixed an issue that could cause automation condition evaluations to fail to render in the UI in rare cases.
• [ui] Fixed a regression in the "Cancel Backfill" option for job backfills that have finished queuing runs.
• [ui] Fixed overflow of long runs feed table on backfill page.
• [dagster-dbt] Replaced @validator with @field_validator in dagster_dbt/core/resource.py to prevent Pydantic deprecation warnings. (Thanks @tintamarre!)

Documentation

• Updated the "Asset versioning and caching" guide to reflect the current Dagster UI and "Unsynced" labels.
• Removed a few repeated lines in documentation on customizing automation conditions. (Thanks @zero-stroke!)
• Fixed example in TableRecord documentation to use the new input format.

Configuration

• [dagster-gcp] Updated Dataproc configuration to the latest version. If necessary, consider pinning your dagster-gcp version while you migrate config. Please see the full list of changed fields: https://gist.github.com/deepyaman/b4d562e04fe571e40037a344b7a9937d
• [dagster-aws][dagster-spark] Updated Spark configuration to the latest version (3.5.5). If necessary, consider pinning your dagster-aws and/or dagster-spark version while you migrate config. Please see the full list of changed fields: https://gist.github.com/deepyaman/f358f5a70fea28d5f164aca8da3dee04

Dagster Plus

• [ui] Fixed filtering for multiple tags on list view pages, including Automations.
• [ui] Fixed an issue where the urls generated by catalog filtering would remove all filters if loaded directly.
• [ui] Added a warning on the sign-in page indicating that the sign-in and signup flows will be changing soon.
• [ui] Require confirmation when rolling back a code location to a previous version.

dg & Components (Preview)

• Virtual environment detection settings for projects have changed. Previously, the global settings use_dg_managed_environment and require_local_venv controlled the environment used when launching project subprocesses. This is now configured at the project level. The tool.dg.project.python_environment setting takes a value of either persistent_uv or active. persistent_uv will be used by default in new scaffolded projects and uses a uv-managed .venv in the project root. active is the default if no tool.dg.project.python_environment is set, and just uses the active python environment and opts out of dg management of the environment.
• A new base class, Resolvable, has been added. This can be used to simplify the process of defining a yaml schema for your components. Instead of manually defining a manual ResolvedFrom[...] and ResolvableModel, the framework will automatically derive the model schema for you based off of the annotations of your class.
• Python files with Pythonic Components (i.e. defined with @component) can now contain relative imports.
• The dg init command now accepts optional --workspace-name and --project-name options to allow scaffolding an initial workspace and project via CLI options instead of prompts.
• Added a new dagster_components.dagster.DefsFolderComponent that can be used at any level of your defs/ folder to apply asset attributes to the definitions at or below that level. This was previously named dagster_components.dagster.DefsModuleComponent.