1.9.0 (core) / 0.25.0 (libraries)

Major changes since 1.8.0 (core) / 0.24.0 (libraries)

Automation

• Declarative Automation, the system which enables setting per-asset AutomationConditions, is no longer experimental. We now recommend using this system in all cases where asset-centric orchestration is desired. A suite of built-in static constructors have been added for common usecases, such as AutomationCondition.on_missing() (which can fill in missing partitions of assets as soon as upstream data is available), and AutomationCondition.all_deps_blocking_checks_passed() (which can prevent materialization of assets until all upstream blocking checks have passed).
• You can now assign AutomationConditions to asset checks, via the automation_condition parameter on @asset_check or AssetCheckSpec.
• You can now assign AutomationConditions to observable source assets, via the automation_condition parameter on @observable_source_asset.
• [experimental] You can now define custom subclasses of AutomationCondition to execute arbitrary Python code in the context of a broader expression. This allows you to compose built-in conditions with custom business logic.
• The target arguments on schedules and sensors are now marked stable, allowing a stable way for schedules and sensors to target asset selections without needing to define a job.

Integrations

• Introduced a slate of integrations with business intelligence (BI) tools, enabling dashboards, views, and reports to be represented in the Dagster asset graph.
  • Looker
  • Power BI
  • Sigma
  • Tableau
• A rich set of metadata is now automatically collected by our suite of ELT integrations.
  • The dagster/table_name metadata tag, containing the fully-qualified name of the destination model, has been added for Airbyte, dlt, Fivetran and Sling assets.
  • The dagster/row_count metadata tag, containing the number of records loaded in the corresponding run, has been added for dlt and Sling assets.
  • The dagster/column_schema metadata tag, containing column schema information of the destination tables, has been added for Fivetran assets.
  • Column lineage information is now collected for Sling assets.
• dagster-pipes are replacing the now deprecated Step Launchers as the new recommended approach for executing remote Spark jobs. Three new Pipes clients for running Spark applications on Amazon Web Services have been added:
  • dagster_aws.pipes.PipesGlueClient
  • dagster_aws.pipes.PipesEMRServerlessClient
  • dagster_aws.pipes.PipesEMRClient

UI

• Several changes have been made to the information architecture to make it easier to find what you’re looking for:
  • Backfills have been moved from their own tab underneath the Overview page to entries within the table on the Runs page. This reflects the fact that backfills and runs are similar entities that share most properties. You can continue to use the legacy Runs page with the “Revert to legacy Runs page” user setting. (GitHub Discussion)
  • “Jobs” is now a page reachable from the top-level navigation pane. It replaces the Jobs tab within the Overview page.
  • “Automations” is now a page reachable from the top-level navigation pane. It replaces the schedule and sensor tabs within the Overview page.
• @asset and AssetSpec now have a kinds attribute that enables specifying labels that show up on asset nodes in the asset graph in the UI. This supersedes the compute_kind attribute.

Changes since 1.8.13 (core) / 0.24.13 (libraries)

New

• The tags parameter to @asset and AssetSpec is no longer marked as experimental.
• The @observable_source_asset decorator now supports an automation_condition argument.
• AutomationCondition and associated APIs are no longer marked as experimental.
• Added a new use_user_code_server parameter to AutomationConditionSensorDefinition. If set, the sensor will be evaluated in the user code server (as traditional sensors are), allowing custom AutomationCondition subclasses to be evaluated.
• Added a new column to the BulkActions table, a new column to the Runs table, and a new BackfillTags table to improve the performance of the Runs page. To take advantage of these performance improvements, run dagster instance migrate. This migration involves a schema migration to add the new columns and table, and a data migration to populate the new columns for historical backfills and runs.
• Performance improvements when loading definitions with multi-assets with many asset keys.
• [ui] The previously-experimental changes to the top nav are now enabled for all users.
• [ui] Added new code location pages which provide information regarding library versions, metadata, and definitions.
• [ui] The new version of the Runs page is now enabled by default. To use the legacy version of the Runs page, toggle the "Revert to legacy Runs page" user setting.
• [ui] Clicking an asset with failed partitions on the asset health overview now takes you to a list of the failed partitions.
• [ui] The Materialize button runs pre-flight checks more efficiently, resulting in faster run launch times.
• [dagster-pipes] Added support for multi-container log streaming (thanks, @MattyKuzyk!)
• [dagster-docker] container_kwargs.stop_timeout can now be set when using the DockerRunLauncher or docker_executor to configure the amount of time that Docker will wait when terminating a run for it to clean up before forcibly stopping it with a SIGKILL signal.
• [dagster-dbt] Performance improvements when loading definitions using build_dbt_asset_selection.

Bugfixes

• [ui] Fixed redirect behavior on full pageloads of the legacy auto-materialize overview page.
• [ui] Plots for assets that emit materialization and observation events at different rates no longer display a time period missing the more frequent event type.
• [ui] Fixed issue causing scrolling to misbehave on the concurrency settings page.
• [helm] The blockOpConcurrencyLimitedRuns section of queuedRunCoordinator now correctly templates the appropriate config.
• [dagster-pipes] Fixed issue where k8s ops would fail after 4 hours (thanks, @MattyKuzyk!)

Documentation

• [dagster-dbt] Added guide for using dbt defer with Dagster branch deployments.
• [docs] Step Launchers documentation has been removed and replaced with references to Dagster Pipes.
• [docs] Fixed code example in Dagster Essentials (thanks, @aleexharris!)

Breaking Changes

• dagster no longer supports Python 3.8, which hit EOL on 2024-10-07.
• dagster now requires pydantic>=2.
• By default, AutomationConditionSensorDefinitions will now emit backfills to handle cases where more than one partition of an asset is requested on a given tick. This allows that asset's BackfillPolicy to be respected. This feature can be disabled by setting allow_backfills to False.
• Passing a custom PartitionsDefinition subclass into a Definitions object now issues an error instead of a deprecation warning.
• AssetExecutionContext is no longer a subclass of OpExecutionContext. At this release, AssetExecutionContext and OpExecutionContext implement the same methods, but in the future, the methods implemented by each class may diverge. If you have written helper functions with OpExecutionContext type annotations, they may need to be updated to include AssetExecutionContext depending on your usage. Explicit calls to isinstance(context, OpExecutionContext) will now fail if context is an AssetExecutionContext.
• The asset_selection parameter on AutomationConditionSensorDefinition has been renamed to target, to align with existing sensor APIs.
• The experimental freshness_policy_sensor has been removed, as it relies on the long-deprecated FreshnessPolicy API.
• The deprecated external_assets_from_specs and external_asset_from_spec methods have been removed. Users should use AssetsDefinition(specs=[...]), or pass specs directly into the Definitions object instead.
• AssetKey objects can no longer be iterated over or indexed in to. This behavior was never an intended access pattern and in all observed cases was a mistake.
• The dagster/relation_identifier metadata key has been renamed to dagster/table_name.
• [dagster-ge] dagster-ge now only supports great_expectations>=0.17.15. The ge_validation_op_factory API has been replaced with the API previously called ge_validation_op_factory_v3.
• [dagster-aws] Removed deprecated parameters from dagster_aws.pipes.PipesGlueClient.run.
• [dagster-embedded-elt] Removed deprecated parameter dlt_dagster_translator from @dlt_assets. The dagster_dlt_translator parameter should be used instead.
• [dagster-polars] Dropped support for saving storage-level arbitrary metadata via IOManagers.

Deprecations

• The DataBricksPysparkStepLauncher, EmrPySparkStepLauncher, and any custom subclass of StepLauncher have been marked as deprecated, but will not be removed from the codebase until Dagster 2.0 is released, meaning they will continue to function as they currently do for the foreseeable future. Their functionality has been superseded by the interfaces provided by dagster-pipes, and so future development work will be focused there.
• The experimental multi_asset_sensor has been marked as deprecated, as its main use cases have been superseded by the AutomationCondition APIs. However, it will not be removed until version 2.0.0.

1.8.13 (core) / 0.24.13 (libraries)

New

• Performance improvements when loading code locations using multi-assets with many asset keys.
• AutomationCondition.in_progress() now will be true if an asset partition is part of an in-progress backfill that has not yet executed it. The prior behavior, which only considered runs, is encapsulated in AutomationCondition.execution_in_progress().
• [ui] Added tag filter to the jobs page.
• [ui] Preserve user login state for a longer period of time.
• [dagster-dbt] Performance improvements when loading definitions using build_dbt_asset_selection.
• [dagster-docker] container_kwargs.stop_timeout can now be set when using the DockerRunLauncher or docker_executor to configure the amount of time that Docker will wait when terminating a run for it to clean up before forcibly stopping it with a SIGKILL signal.
• [dagster-sigma] The Sigma integration now fetches initial API responses in parallel, speeding up initial load.
• [dagster-looker] Attempt to naively render liquid templates for derived table sql.
• [dagster-looker] Added support for views and explores that rely on refinements or extends.
• [dagster-looker] When fetching explores and dashboards from the Looker API, retrieve in parallel.

Bugfixes

• Fixed an issue with AutomationCondition.eager() that could cause it to attempt to launch a second attempt of an asset in cases where it was skipped or failed during a run where one of its parents successfully materialized.
• Fixed an issue which would cause AutomationConditionSensorDefinitions to not be evaluated if the use_user_code_server value was toggled after the initial evaluation.
• Fixed an issue where configuration values for aliased pydantic fields would be dropped.
• [ui] Fix an issue in the code locations page where invalid query parameters could crash the page.
• [ui] Fix navigation between deployments when query parameters are present in the URL.
• [helm] the blockOpConcurrencyLimitedRuns section of queuedRunCoordinator now correctly templates the appropriate config.
• [dagster-sigma] Fixed pulling incomplete data for very large workspaces.

1.8.12 (core) / 0.24.12 (libraries)

New

• The AutomationCondition.eager(), AutomationCondition.missing(), and AutomationCondition.on_cron conditions are now compatible with asset checks.
• Added AssetSelection.materializable(), which returns only assets that are materializable in an existing selection.
• Added a new AutomationCondition.all_deps_blocking_checks_passed condition, which can be used to prevent materialization when any upstream blocking checks have failed.
• Added a code_version parameter to the @graph_asset decorator.
• If a LaunchPartitionBackfill mutation is submitted to GQL with invalid partition keys, it will now return an early PartitionKeysNotFoundError.
• AssetSelection.checks_for_assets now accepts AssetKeys and string asset keys, in addition to AssetsDefinitions.
• [ui] Added a search bar to partitions tab on the asset details page.
• [ui] Restored docked left nav behavior for wide viewports.
• [dagster-aws] get_objects now has a since_last_modified that enables only fetching objects modified after a given timestamp.
• [dagster-aws] New AWS EMR Dagster Pipes client (dagster_aws.pipes.PipesEMRCLient ) for running and monitoring AWS EMR jobs from Dagster.
• [dagster-looker] Pinned the looker-sdk dependency below 24.18.0 to avoid this issue: looker-open-source/sdk-codegen#1518.

Bugfixes

• Fixed an issue which could cause incorrect evaluation results when using self-dependent partition mappings with AutomationConditions that operate over dependencies.
• [ui] Fixed an issue where the breadcumb on asset pages would flicker nonstop.
• [dagster-embedded-elt] Fixed extraction of metadata for dlt assets whose source and destination identifiers differ.
• [dagster-databricks] Fixed a permissioning gap that existed with the DatabricksPySparkStepLauncher, so that permissions are now set correctly for non-admin users.
• [dagster-dbt] Fixed an issue where column metadata generated with fetch_column_metadata did not work properly for models imported through dbt dependencies.

Documentation

• [dagster-k8s] DagsterK8sPipesClient.run now shows up in API docs.

Dagster Plus

• [ui] Fixed a bug in the catalog UI where owners filters were not applied correctly.
• [ui] Fixed width of the column lineage dropdown selector on the asset page.
• [ui] Column lineage now correctly renders when set on asset definition metadata
• [ui] Fixed Settings link on the list of deployments, for users in the legacy navigation flag.

1.8.11 (core) / 0.24.11 (libraries)

New

• [experimental] AutomationCondition.eager() will now only launch runs for missing partitions which become missing after the condition has been added to the asset. This avoids situations in which the eager policy kicks off a large amount of work when added to an asset with many missing historical static/dynamic partitions.
• [experimental] Added a new AutomationCondition.asset_matches() condition, which can apply a condition against an arbitrary asset in the graph.
• [experimental] Added the ability to specify multiple kinds for an asset with the kinds parameter.
• [dagster-github] Added create_pull_request method on GithubClient that enables creating a pull request.
• [dagster-github] Added create_ref method on GithubClient that enables creating a new branch.
• [dagster-embedded-elt] dlt assets now generate column metadata for child tables.
• [dagster-embedded-elt] dlt assets can now fetch row count metadata with dlt.run(...).fetch_row_count() for both partitioned and non-partitioned assets. Thanks @kristianandre!
• [dagster-airbyte] relation identifier metadata is now attached to Airbyte assets.
• [dagster-embedded-elt] relation identifier metadata is now attached to sling assets.
• [dagster-embedded-elt] relation identifier metadata is now attached to dlt assets.

Bugfixes

• PartitionedConfig objects can now return a RunConfig without causing a crash.
• Corrected the AssetIn.__new__ typing for the dagster_type argument.
• [dagster-embedded-elt] dlt assets now generate correct column metadata after the first materialization.
• [dagster-embedded-elt] Sling's fetch_row_count() method now works for databases returning uppercase column names. Thanks @kristianandre!
• [dagster-gcp] Ensure blob download is flushed to temporary file for GCSFileManager.read operations. Thanks @ollie-bell!

Dagster Plus

• Fixed a bug in the catalog UI where owners filters were not applied correctly.

1.8.10 (core) / 0.24.10 (libraries)

New

• JobDefinition, @job, and define_asset_job now take a run_tags parameter. If run_tags are defined, they will be attached to all runs of the job, and tags will not be. If run_tags is not set, then tags are attached to all runs of the job (status quo behavior). This change enables the separation of definition-level and run-level tags on jobs.
• Then env var DAGSTER_COMPUTE_LOG_TAIL_WAIT_AFTER_FINISH can now be used to pause before capturing logs (thanks @HynekBlaha!)
• The kinds parameter is now available on AssetSpec.
• OutputContext now exposes the AssetSpec of the asset that is being stored as an output (thanks, @marijncv!)
• [experimental] Backfills are incorporated into the Runs page to improve observability and provide a more simplified UI. See the GitHub discussion for more details.
• [ui] The updated navigation is now enabled for all users. You can revert to the legacy navigation via a feature flag. See GitHub discussion for more.
• [ui] Improved performance for loading partition statuses of an asset job.
• [dagster-docker] Run containers launched by the DockerRunLauncher now include dagster/job_name and dagster/run_id labels.
• [dagster-aws] The ECS launcher now automatically retries transient ECS RunTask failures (like capacity placement failures).

Bugfixes

• Changed the log volume for global concurrency blocked runs in the run coordinator to be less spammy.
• [ui] Asset checks are now visible in the run page header when launched from a schedule.
• [ui] Fixed asset group outlines not rendering properly in Safari.
• [ui] Reporting a materialization event now removes the asset from the asset health "Execution failures" list and returns the asset to a green / success state.
• [ui] When setting an AutomationCondition on an asset, the label of this condition will now be shown in the sidebar on the Asset Details page.
• [ui] Previously, filtering runs by Created date would include runs that had been updated after the lower bound of the requested time range. This has been updated so that only runs created after the lower bound will be included.
• [ui] When using the new experimental navigation flag, added a fix for the automations page for code locations that have schedules but no sensors.
• [ui] Fixed tag wrapping on asset column schema table.
• [ui] Restored object counts on the code location list view.
• [ui] Padding when displaying warnings on unsupported run coordinators has been corrected (thanks @hainenber!)
• [dagster-k8s] Fixed an issue where run termination sometimes did not terminate all step processes when using the k8s_job_executor, if the termination was initiated while it was in the middle of launching a step pod.

Documentation

• Corrections on the Dagster instance concept page (thanks @mheguy!)
• Corrections on the code locations concept page (thanks @tiberiuana!)
• Repeated words removed (thanks @tianzedavid!)
• [dagster-deltalake] Corrections and improvements (thanks @avriiil!)
• [dagster-aws] Added docs for PipesEMRServerlessClient.
• [dagster-cli] A guide on how to validate Dagster definitions using dagster definitions validate have been added.
• [dagster-databricks] Added docs for using Databricks Pipes with existing clusters.
• [dagster-dbt] Corrected sample sql code (thanks @b-per!)

1.8.9 (core) / 0.24.9 (libraries)

New

• AssetSpec now has a with_io_manager_key method that returns an AssetSpec with the appropriate metadata entry to dictate the key for the IO manager used to load it. The deprecation warning for SourceAsset now references this method.
• Added a max_runtime_seconds configuration option to run monitoring, allowing you to specify that any run in your Dagster deployment should terminate if it exceeds a certain runtime. Prevoiusly, jobs had to be individually tagged with a dagster/max_runtime tag in order to take advantage of this feature. Jobs and runs can still be tagged in order to override this value for an individual run.
• It is now possible to set both tags and a custom execution_fn on a ScheduleDefinition. Schedule tags are intended to annotate the definition and can be used to search and filter in the UI. They will not be attached to run requests emitted from the schedule if a custom execution_fn is provided. If no custom execution_fn is provided, then for back-compatibility the tags will also be automatically attached to run requests emitted from the schedule.
• SensorDefinition and all of its variants/decorators now accept a tags parameter. The tags annotate the definition and can be used to search and filter in the UI.
• Added the dagster definitions validate command to Dagster CLI. This command validates if Dagster definitions are loadable.
• [dagster-databricks] Databricks Pipes now allow running tasks in existing clusters.

Bugfixes

• Fixed an issue where calling build_op_context in a unit test would sometimes raise a TypeError: signal handler must be signal.SIG_IGN, signal.SIG_DFL, or a callable object Exception on process shutdown.
• [dagster-webserver] Fix an issue where the incorrect sensor/schedule state would appear when using DefaultScheduleStatus.STOPPED / DefaultSensorStatus.STOPPED after performing a reset.

Documentation

• [dagster-pipes] Fixed inconsistencies in the k8s pipes example.
• [dagster-pandas-pyspark] Fixed example in the Spark/Pandas SDA guide.

Dagster Plus

• Fixed an issue where users with Launcher permissions for a particular code location were not able to cancel backfills targeting only assets in that code location.
• Fixed an issue preventing long-running alerts from being sent when there was a quick subsequent run.

1.8.8 (core) / 0.24.8 (libraries)

New

• Added --partition-range option to dagster asset materialize CLI. This option only works for assets with single-run Backfill Policies.
• Added a new .without() method to AutomationCondition.eager(), AutomationCondition.on_cron(), and AutomationCondition.on_missing() which allows sub-conditions to be removed, e.g. AutomationCondition.eager().without(AutomationCondition.in_latest_time_window()).
• Added AutomationCondition.on_missing(), which materializes an asset partition as soon as all of its parent partitions are filled in.
• pyproject.toml can now load multiple Python modules as individual Code Locations. Thanks, @bdart!
• [ui] If a code location has errors, a button will be shown to view the error on any page in the UI.
• [dagster-adls2] The ADLS2PickleIOManager now accepts lease_duration configuration. Thanks, @0xfabioo!
• [dagster-embedded-elt] Added an option to fetch row count metadata after running a Sling sync by calling sling.replicate(...).fetch_row_count().
• [dagster-fivetran] The dagster-fivetran integration will now automatically pull and attach column schema metadata after each sync.

Bugfixes

• Fixed an issue which could cause errors when using AutomationCondition.any_downstream_condition() with downstream AutoMaterializePolicy objects.
• Fixed an issue where process_config_and_initialize did not properly handle processing nested resource config.
• [ui] Fixed an issue that would cause some AutomationCondition evaluations to be labeled DepConditionWrapperCondition instead of the key that they were evaluated against.
• [ui] Fix an issue where the incorrect sensor/schedule state would appear when using DefaultScheduleStatus.STOPPED / DefaultSensorStatus.STOPPED after performing a reset.
• [dagster-webserver] Fixed an issue with code locations appearing in fluctuating incorrect state in deployments with multiple webserver processes.
• [dagster-embedded-elt] Fixed an issue where Sling column lineage did not correctly resolve int the Dagster UI.
• [dagster-k8s] The wait_for_pod check now waits until all pods are available, rather than erroneously returning after the first pod becomes available. Thanks @easontm!

Dagster Plus

• Backfill daemon logs are now available in the "Coordinator Logs" tab in a backfill details page.
• Users without proper code location permissions can no longer edit sensor cursors.

1.8.7 (core) / 0.24.7 (libraries)

New

• The AssetSpec constructor now raises an error if an invalid group name is provided, instead of an error being raised when constructing the Definitions object.
• dagster/relation_identifier metadata is now automatically attached to assets which are stored using a DbIOManager.
• [ui] Streamlined the code location list view.
• [ui] The “group by” selection on the Timeline Overview page is now part of the query parameters, meaning it will be retained when linked to directly or when navigating between pages.
• [dagster-dbt] When instantiating DbtCliResource, the project_dir argument will now override the DBT_PROJECT_DIR environment variable if it exists in the local environment (thanks, @marijncv!).
• [dagster-embedded-elt] dlt assets now generate rows_loaded metadata (thanks, @kristianandre!).
• Added support for pydantic version 1.9.0.

Bugfixes

• Fixed a bug where setting asset_selection=[] on RunRequest objects yielded from sensors using asset_selection would select all assets instead of none.
• Fixed bug where the tick status filter for batch-fetched graphql sensors was not being respected.
• [examples] Fixed missing assets in assets_dbt_python example.
• [dagster-airbyte] Updated the op names generated for Airbyte assets to include the full connection ID, avoiding name collisions.
• [dagster-dbt] Fixed issue causing dagster-dbt to be unable to load dbt projects where the adapter did not have a database field set (thanks, @dargmuesli!)
• [dagster-dbt] Removed a warning about not being able to load the dbt.adapters.duckdb module when loading dbt assets without that package installed.

Documentation

• Fixed typo on the automation concepts page (thanks, @oedokumaci!)

Dagster Plus

• You may now wipe specific asset partitions directly from the execution context in user code by calling DagsterInstance.wipe_asset_partitions.
• Dagster+ users with a "Viewer" role can now create private catalog views.
• Fixed an issue where the default IOManager used by Dagster+ Serverless did not respect setting allow_missing_partitions as metadata on a downstream asset.

1.8.6 (core) / 0.24.6 (libraries)

Bugfixes

• Fixed an issue where runs in Dagster+ Serverless that materialized partitioned assets would sometimes fail with an object has no attribute '_base_path' error.
• [dagster-graphql] Fixed an issue where the statuses filter argument to the sensorsOrError GraphQL field was sometimes ignored when querying GraphQL for multiple sensors at the same time.

1.8.5 (core) / 0.24.5 (libraries)

New

• Updated multi-asset sensor definition to be less likely to timeout queries against the asset history storage.
• Consolidated the CapturedLogManager and ComputeLogManager APIs into a single base class.
• [ui] Added an option under user settings to clear client side indexeddb caches as an escape hatch for caching related bugs.
• [dagster-aws, dagster-pipes] Added a new PipesECSClient to allow Dagster to interface with ECS tasks.
• [dagster-dbt] Increased the default timeout when terminating a run that is running a dbt subprocess to wait 25 seconds for the subprocess to cleanly terminate. Previously, it would only wait 2 seconds.
• [dagster-sdf] Increased the default timeout when terminating a run that is running an sdf subprocess to wait 25 seconds for the subprocess to cleanly terminate. Previously, it would only wait 2 seconds.
• [dagster-sdf] Added support for caching and asset selection (Thanks, akbog!)
• [dagster-dlt] Added support for AutomationCondition using DagsterDltTranslator.get_automation_condition() (Thanks, aksestok!)
• [dagster-k8s] Added support for setting dagsterDaemon.runRetries.retryOnAssetOrOpFailure to False in the Dagster Helm chart to prevent op retries and run retries from simultaneously firing on the same failure.
• [dagster-wandb] Removed usage of deprecated recursive parameter (Thanks, chrishiste!)

Bugfixes

• [ui] Fixed a bug where in-progress runs from a backfill could not be terminated from the backfill UI.
• [ui] Fixed a bug that caused an "Asset must be part of at least one job" error when clicking on an external asset in the asset graph UI
• Fixed an issue where viewing run logs with the latest 5.0 release of the watchdog package raised an exception.
• [ui] Fixed issue causing the “filter to group” action in the lineage graph to have no effect.
• [ui] Fixed case sensitivity when searching for partitions in the launchpad.
• [ui] Fixed a bug which would redirect to the events tab for an asset if you loaded the partitions tab directly.
• [ui] Fixed issue causing runs to get skipped when paging through the runs list (Thanks, @HynekBlaha!)
• [ui] Fixed a bug where the asset catalog list view for a particular group would show all assets.
• [dagster-dbt] fix bug where empty newlines in raw dbt logs were not being handled correctly.
• [dagster-k8s, dagster-celery-k8s] Correctly set dagster/image label when image is provided from user_defined_k8s_config. (Thanks, @HynekBlaha!)
• [dagster-duckdb] Fixed an issue for DuckDB versions older than 1.0.0 where an unsupported configuration option, custom_user_agent, was provided by default
• [dagster-k8s] Fixed an issue where Kubernetes Pipes failed to create a pod if the op name contained capital or non-alphanumeric containers.
• [dagster-embedded-elt] Fixed an issue where dbt assets downstream of Sling were skipped

Deprecations

• [dagser-aws]: Direct AWS API arguments in PipesGlueClient.run have been deprecated and will be removed in 1.9.0. The new params argument should be used instead.

Dagster Plus

• Fixed a bug that caused an error when loading the launchpad for a partition, when using Dagster+ with an agent with version below 1.8.2.
• Fixed an issue where terminating a Dagster+ Serverless run wouldn’t forward the termination signal to the job to allow it to cleanly terminate.