1.6.7 (core) / 0.22.7 (libraries)

New

• Added a new run_retries.retry_on_op_or_asset_failures setting that can be set to false to make run retries only occur when there is an unexpected failure that crashes the run, allowing run-level retries to co-exist more naturally with op or asset retries. See the docs for more information.
• dagster dev now sets the environment variable DAGSTER_IS_DEV_CLI allowing subprocesses to know that they were launched in a development context.
• [ui] The Asset Checks page has been updated to show more information on the page itself rather than in a dialog.

Bugfixes

• [ui] Fixed an issue where the UI disallowed creating a dynamic partition if its name contained the “|” pipe character.
• AssetSpec previously dropped the metadata and code_version fields, resulting in them not being attached to the corresponding asset. This has been fixed.

Experimental

• The new @multi_observable_source_asset decorator enables defining a set of assets that can be observed together with the same function.
• [dagster-embedded-elt] New Asset Decorator @sling_assets and Resource SlingConnectionResource have been added for the [dagster-embedded-elt.sling](http://dagster-embedded-elt.sling) package. Deprecated build_sling_asset, SlingSourceConnection and SlingTargetConnection.
• Added support for op-concurrency aware run dequeuing for the QueuedRunCoordinator.

Documentation

• Fixed reference documentation for isolated agents in ECS.
• Corrected an example in the Airbyte Cloud documentation.
• Added API links to OSS Helm deployment guide.
• Fixed in-line pragmas showing up in the documentation.

Dagster Cloud

• Alerts now support Microsoft Teams.
• [ECS] Fixed an issue where code locations could be left undeleted.
• [ECS] ECS agents now support setting multiple replicas per code server.
• [Insights] You can now toggle the visibility of a row in the chart by clicking on the dot for the row in the table.
• [Users] Added a new column “Licensed role” that shows the user's most permissive role.

1.6.6 (core) / 0.22.6 (libraries)

New

• Dagster officially supports Python 3.12.
• dagster-polars has been added as an integration. Thanks @danielgafni!
• [dagster-dbt] @dbt_assets now supports loading projects with semantic models.
• [dagster-dbt] @dbt_assets now supports loading projects with model versions.
• [dagster-dbt] get_asset_key_for_model now supports retrieving asset keys for seeds and snapshots. Thanks @aksestok!
• [dagster-duckdb] The Dagster DuckDB integration supports DuckDB version 0.10.0.
• [UPath I/O manager] If a non-partitioned asset is updated to have partitions, the file containing the non-partitioned asset data will be deleted when the partitioned asset is materialized, rather than raising an error.

Bugfixes

• Fixed an issue where creating a backfill of assets with dynamic partitions and a backfill policy would sometimes fail with an exception.
• Fixed an issue with the type annotations on the @asset decorator causing a false positive in Pyright strict mode. Thanks @tylershunt!
• [ui] On the asset graph, nodes are slightly wider allowing more text to be displayed, and group names are no longer truncated.
• [ui] Fixed an issue where the groups in the asset graph would not update after an asset was switched between groups.
• [dagster-k8s] Fixed an issue where setting the security_context field on the k8s_job_executor didn't correctly set the security context on the launched step pods. Thanks @krgn!

Experimental

• Observable source assets can now yield ObserveResults with no data_version.
• You can now include FreshnessPolicys on observable source assets. These assets will be considered “Overdue” when the latest value for the “dagster/data_time” metadata value is older than what’s allowed by the freshness policy.
• [ui] In Dagster Cloud, a new feature flag allows you to enable an overhauled asset overview page with a high-level stakeholder view of the asset’s health, properties, and column schema.

Documentation

• Updated docs to reflect newly-added support for Python 3.12.

Dagster Cloud

• [kubernetes] Fixed an issue where the Kubernetes agent would sometimes leave dangling kubernetes services if the agent was interrupted during the middle of being terminated.

1.6.5 (core) / 0.22.5 (libraries)

New

• Within a backfill or within auto-materialize, when submitting runs for partitions of the same assets, runs are now submitted in lexicographical order of partition key, instead of in an unpredictable order.
• [dagster-k8s] Include k8s pod debug info in run worker failure messages.
• [dagster-dbt] Events emitted by DbtCliResource now include metadata from the dbt adapter response. This includes fields like rows_affected, query_id from the Snowflake adapter, or bytes_processed from the BigQuery adapter.

Bugfixes

• A previous change prevented asset backfills from grouping multiple assets into the same run when using BackfillPolicies under certain conditions. While the backfills would still execute in the proper order, this could lead to more individual runs than necessary. This has been fixed.
• [dagster-k8s] Fixed an issue introduced in the 1.6.4 release where upgrading the Helm chart without upgrading the Dagster version used by user code caused failures in jobs using the k8s_job_executor.
• [instigator-tick-logs] Fixed an issue where invoking context.log.exception in a sensor or schedule did not properly capture exception information.
• [asset-checks] Fixed an issue where additional dependencies for dbt tests modeled as Dagster asset checks were not properly being deduplicated.
• [dagster-dbt] Fixed an issue where dbt model, seed, or snapshot names with periods were not supported.

Experimental

• @observable_source_asset-decorated functions can now return an ObserveResult. This allows including metadata on the observation, in addition to a data version. This is currently only supported for non-partitioned assets.
• [auto-materialize] A new AutoMaterializeRule.skip_on_not_all_parents_updated_since_cron class allows you to construct AutoMaterializePolicys which wait for all parents to be updated after the latest tick of a given cron schedule.
• [Global op/asset concurrency] Ops and assets now take run priority into account when claiming global op/asset concurrency slots.

Documentation

• Fixed an error in our asset checks docs. Thanks @vaharoni!
• Fixed an error in our Dagster Pipes Kubernetes docs. Thanks @cameronmartin!
• Fixed an issue on the Hello Dagster! guide that prevented it from loading.
• Add specific capabilities of the Airflow integration to the Airflow integration page.
• Re-arranged sections in the I/O manager concept page to make info about using I/O versus resources more prominent.

1.6.4 (core) / 0.22.4 (libraries)

New

• build_schedule_from_partitioned_job now supports creating a schedule from a static-partitioned job (Thanks @craustin!)
• [dagster-pipes] PipesK8sClient will now autodetect the namespace when using in-cluster config. (Thanks @aignas!)
• [dagster-pipes] PipesK8sClient can now inject the context in to multiple containers. (Thanks @aignas!)
• [dagster-snowflake] The Snowflake Pandas I/O manager now uses the write_pandas method to load Pandas DataFrames in Snowflake. To support this change, the database connector was switched from SqlDbConnection to SnowflakeConnection .
• [ui] On the overview sensors page you can now filter sensors by type.
• [dagster-deltalake-polars] Added LazyFrame support (Thanks @ion-elgreco!)
• [dagster-dbt] When using @dbt_assets and multiple dbt resources produce the same AssetKey, we now display an exception message that highlights the file paths of the misconfigured dbt resources in your dbt project.
• [dagster-k8s] The debug info reported upon failure has been improved to include additional information from the Job. (Thanks @jblawatt!)
• [dagster-k8s] Changed the Dagster Helm chart to apply automountServiceAccountToken: false to the default service account used by the Helm chart, in order to better comply with security policies. (Thanks @MattyKuzyk!)

Bugfixes

• A unnecessary thread lock has been removed from the sensor daemon. This should improve sensor throughput for users with many sensors who have enabled threading.
• Retry from failure behavior has been improved for cases where dynamic steps were interrupted.
• Previously, when backfilling a set of assets which shared a BackfillPolicy and PartitionsDefinition, but had a non-default partition mapping between them, a run for the downstream asset could be launched at the same time as a separate run for the upstream asset, resulting in inconsistent partition ordering. Now, the downstream asset will only execute after the parents complete. (Thanks @ruizh22!)
• Previously, asset backfills would raise an exception if the code server became unreachable mid-iteration. Now, the backfill will pause until the next evaluation.
• Fixed a bug that was causing ranged backfills over dynamically partitioned assets to fail.
• [dagster-pipes] PipesK8sClient has improved handling for init containers and additional containers. (Thanks @aignas!)
• Fixed the last_sensor_start_time property of the SensorEvaluationContext, which would get cleared on ticks after the first tick after the sensor starts.
• [dagster-mysql] Fixed the optional dagster instance migrate --bigint-migration, which caused some operational errors on mysql storages.

Deprecations

• The following methods on AssetExecutionContext have been marked deprecated, with their suggested replacements in parenthesis:
  • context.op_config (context.op_execution_context.op_config)
  • context.node_handle (context.op_execution_context.node_handle)
  • context.op_handle (context.op_execution_context.op_handle)
  • context.op (context.op_execution_context.op)
  • context.get_mapping_key (context.op_execution_context.get_mapping_key)
  • context.selected_output_names (context.op_execution_context.selected_output_names)
  • context.dagster_run (context.run)
  • context.run_id (context.run.run_id)
  • context.run_config (context.run.run_config)
  • context.run_tags (context.run.tags)
  • context.has_tag (key in context.run.tags)
  • context.get_tag (context.run.tags.get(key))
  • context.get_op_execution_context (context.op_execution_context)
  • context.asset_partition_key_for_output (context.partition_key)
  • context.asset_partition_keys_for_output (context.partition_keys)
  • context.asset_partitions_time_window_for_output (context.partition_time_window)
  • context.asset_partition_key_range_for_output (context.partition_key_range)

Experimental

• [asset checks] @asset_check now has a blocking parameter. When this is enabled, if the check fails with severity ERROR then any downstream assets in the same run won’t execute.

Documentation

• The Branch Deployment docs have been updated to reflect support for backfills
• Added Dagster’s maximum supported Python version (3.11) to Dagster University and relevant docs
• Added documentation for recommended partition limits (a maximum of 25K per asset).
• References to the Enterprise plan have been renamed to Pro, to reflect recent plan name changes
• Added syntax example for setting environment variables in PowerShell to our dbt with Dagster tutorial
• [Dagster University] Dagster Essentials to Dagster v1.6, and introduced the usage of MaterializeResult
• [Dagster University] Fixed a typo in the Dagster University section on adding partitions to an asset (Thanks Brandon Peebles!)
• [Dagster University] Corrected lesson where sensors are covered (Thanks onefloid!)

Dagster Cloud

• Agent tokens can now be locked down to particular deployments. Agents will not be able to run any jobs scheduled for deployments that they are not permitted to access. By default, agent tokens have access to all deployments in an organization. Use the Edit button next to an agent token on the Tokens tab in Org Settings to configure permissions for a particular token. You must be an Organization Admin to edit agent token permissions.

1.6.3 (core) / 0.22.3 (libraries)

New

• Added support for the 3.0 release of the pendulum library, for Python versions 3.9 and higher.
• Performance improvements when starting run worker processes or step worker processes for runs in code locations with a large number of jobs.
• AllPartitionMapping now supports mapping to downstream partitions, enabling asset backfills with these dependencies. Thanks @craustin!
• [asset checks][experimental] @asset_check has new fields additional_deps and additional_ins to allow dependencies on assets other than the asset being checked.
• [ui] Asset graph group nodes now show status counts.
  • [dagster-snowflake] The Snowflake I/O Manager now has more specific error handling when a table doesn’t exist.
• [ui] [experimental] A new experimental UI for the auto-materialize history of a specific asset has been added. This view can be enabled under your user settings by setting “Use new asset auto-materialize history page”.
• [ui] Command clicking on an asset group will now select or deselect all assets in that group.
• [dagster-k8s] Added the ability to customize resource limits for initContainers used by Dagster system components in the Dagster Helm chart. Thanks @MattyKuzyk!
• [dagster-k8s] Added the ability to specify additional containers and initContainers in code locations in the Helm chart. Thanks @craustin!
• [dagster-k8s] Explicitly listed the set of RBAC permissions used by the agent Helm chart role instead of using a wildcard. Thanks @easontm!
• [dagster-dbt] Support for dbt-core==1.4.* is now removed because the version has reached end-of-life.

Bugfixes

• Previously, calling get_partition_keys_not_in_subset on a BaseTimeWindowPartitionsSubset that targeted a partitions definition with no partitions (e.g. a future start date) would raise an error. Now, it returns an empty list.
• Fixed issue which could cause invalid runs to be launched if a code location was updated during the course of an AMP evaluation.
• Previously, some asset backfills raised an error when targeting multi-assets with internal asset dependencies. This has been fixed.
• Previously, using the LocalComputeLogManager on Windows could result in errors relating to invalid paths. This has been resolved. Thanks @hainenber!
• An outdated path in the contribution guide has been updated. Thanks @hainenber!
• [ui] Previously an error was sometimes raised when attempting to create a dynamic partition within a multi-partitioned asset via the UI. This has been fixed.
• [ui] The “Upstream materializations are missing” warning when launching a run has been expanded to warn about failed upstream materializations as well.
• [ui] The community welcome modal now renders properly in dark mode and some elements of Asset and Op graphs have higher contrast in both themes.
• [ui] Fixed dark mode colors for datepicker, error message, and op definition elements.
• [ui] Pressing the arrow keys to navigate op/asset graphs while the layout is loading no longer causes errors.
• [ui] Exporting asset and op graphs to SVG no longer fails when chrome extensions inject additional stylesheets into Dagster’s UI.
• [ui] Dagster now defaults to UTC when the user’s default timezone cannot be identified, rather than crashing with a date formatting error.
• [ui] Fixed an issue in the asset graph sidebar that caused groups to only list their first asset.
• [ui] Fixed an issue where sensors runs would undercount the number of dynamic partition requests added or deleted if there were multiple requests for additions/deletions.
• [docs] Fixed a typo in the “Using Dagster with Delta Lake” guide. Thanks @avriiil!
• [asset checks] Fixed an issue which could cause errors when using asset checks with step launchers.
• [dagster-webserver] A bug preventing WebSocket connections from establishing on python 3.11+ has been fixed.
• [dagster-databricks] DatabricksJobRunner now ensures the correctdatabricks-sdk is installed. Thanks @zyd14!
• [dagster-dbt] On run termination, an interrupt signal is now correctly forwarded to any in-progress dbt subprocesses.
• [dagster-dbt] Descriptions for dbt tests ingested as asset checks can now be populated using the config.meta.description. Thanks @CapitanHeMo!
• [dagster-dbt] Previously, the error message displayed when no dbt profiles information was found would display an incorrect path. This has been fixed. Thanks @zoltanctoth!
• [dagster-k8s] PipesK8sClient can now correctly handle load_incluster_config . Thanks @aignas!

Documentation

• Added a new category to Concepts: Automation. This page provides a high-level overview of the various ways Dagster allows you run data pipelines without manual intervention.
• Moved several concept pages under Concepts > Automation: Schedules, Sensors, Asset Sensors, and Auto-materialize Policies.

Dagster Cloud

• Fixed an issue where configuring the agent_queue key in a dagster_cloud.yaml file incorrectly failed to validate when using the dagster-cloud ci init or dagster-cloud ci check commands during CI/CD.

1.6.2 (core) / 0.22.2 (libraries)

New

• The warning for unloadable sensors and schedules in the Dagster UI has now been removed.
• When viewing an individual sensor or schedule, we now provide a button to reset the status of the sensor or schedule back to its default status as defined in code.

Experimental

• [asset-checks] dbt asset checks now respect warn_if/ error_if severities

Dagster Cloud

• Fixed a bug introduced in 1.6.0 where run status sensors did not cursor correctly when deployed on Dagster Cloud.
• Schedule and sensor mutations are now tracked in the audit log.

1.6.1 (core) / 0.22.1 (libraries)

New

• Added experimental functionality which hides user code errors from the Dagster UI. You may enable this functionality by setting the DAGSTER_REDACT_USER_CODE_ERRORS environment variable to 1.
• [dagster-dbt] @dbt_assets now accepts a required_resource_keys argument.

Bugfixes

• Fixed a bug where a run that targets no steps is launched by an asset backfill when code updates are pushed after backfill launch time.
• Previously a graphQL error would be thrown on the asset backfill page if certain unpartitioned assets were changed to a partitioned assets. This has been fixed.
• [ui] Show run log timestamps in the user’s preferred hour cycle (12/24h) format.
• [ui] The “Export to SVG” option now works as expected in the improved asset graph UI.
• [ui] On the asset graph, hovering over a collapsed group or the title bar of an expanded group highlights all edges in/out of the group.
• Fixed occasional CI/CD errors when building documentation on a feature branch

Community Contributions

• fix: add missing volumes and volumeMounts in job-instance-migrate.yaml. Thanks @nhuray!

Documentation

• Fixed typos in the docs.

Dagster Cloud

• [ui] Fix dark theme colors for billing components.
• [ui] Show the number of users for each grant type (admin, editor, etc.) on the Users page.

1.6.0 (core) / 0.22.0 (libraries)

Major Changes since 1.5.0 (core) / 0.21.0 (libraries)

Core

• Asset lineage graph UI revamp, to make it easier to visualize and navigate large graphs
  • Lineage now flows left-to-right instead of top-to-bottom.
  • You can expand and collapse asset groups in the graph.
  • A new left-hand sidebar provides a list of assets, organized by asset group and code location.
  • You can right-click on assets or groups to filter or materialize them.
  • You can filter by compute kind.
• Dark mode for the Dagster UI – By default, Dagster will match your system’s light or dark theme but you can adjust this in the user settings in the top right of the UI.
• Report asset materializations from the UI – I.e. you record an asset materialization event without executing the code to materialize the asset. This is useful in cases where you overwrote data outside of Dagster, and you want Dagster to know about it and represent it in the UI. It’s also useful when you have a preexisting partitioned asset and start managing it with Dagster: you want Dagster to show the historical partitions as materialized instead of missing.
• MaterializeResult, AssetSpec, and AssetDep now marked stable – These APIs, introduced in Dagster 1.5, were previously marked experimental. They offer a more straightforward way of defining assets when you don’t want to use I/O managers.
• Backfill previews – When launching a backfill that covers assets with different partitions, can you now click “Preview” to see that partitions for each asset that will be covered by the backfill.
• Viewing logs for a sensor or schedule tick is no longer considered experimental – previously, accessing this functionality required turning on a feature flag in user settings.
• Runs triggered by a sensor or schedule link to the tick that triggered them.

dagster-pipes

• AWS Lambda Pipes client –PipesLambdaClient [guide].
• Report arbitrary messages between pipes processes and the orchestrating process – with report_custom_message and get_custom_messages.
• Termination forwarding – ensures that external processes are terminated when an orchestration process is.

Since 1.5.14 (core) / 0.21.14 (libraries)

New

• Default op/asset concurrency limits are now configurable at the deployment level, using the concurrency > default_op_concurrency_limit configuration in your dagster.yaml (OSS) or Deployment Settings page (Dagster Cloud). In OSS, this feature first requires a storage migration (e.g. dagster instance migrate).
• Zero-value op/asset concurrency limits are now supported. In OSS, this feature first requires a storage migration (e.g. dagster instance migrate).
• When a Nothing-typed output is returned from an asset or op, the handle_output function of the I/O manager will no longer be called. Users of most Dagster-maintained I/O managers will see no behavioral changes, but users of the In-Memory I/O manager, or custom I/O managers that store Nothing-typed outputs should reference the migration guide for more information.
• [ui] The updated asset graph is no longer behind an experimental flag. The new version features a searchable left sidebar, a horizontal DAG layout, context menus and collapsible groups!

Bugfixes

• Previously, if a code location was re-deployed with modified assets during an iteration of the asset daemon, empty auto-materialize runs could be produced. This has been fixed.
• The CLI command dagster asset materialize will now return a non-zero exit code upon failure.
• [ui] The Dagster UI now shows resource descriptions as markdown instead of plain text.
• [ui] Viewing stdout/stderr logs for steps emitting hundreds of thousands of messages is much more performant and does not render the Run page unusable.
• [ui] Fixed an issue where sensors with intervals that were less than 30 seconds were shown with an interval of “~30s” in the UI. The correct interval is now shown.
• [dagster-graphql] Fixed an issue where the GraphQL Python client raised an unclear error if the request failed due to a permissions error.

Breaking Changes

• A slight change has been made to run status sensors cursor values for Dagster instance using the default SQLite storage implementation. If you are using the default SQLite storage and you are upgrading directly from a version of dagster<1.5.1, you may see the first tick of your run status sensor skip runs that completed but were not yet registered by the sensor during your upgrade. This should not be common, but to avoid any chance of that, you may consider an interim upgrade to dagster>=1.5.1,<1.6.0 first.

Community Contributions

• Fixed a typo in the docs. Thanks @tomscholz!
• [dagster-pyspark] Added additional file exclude rules to the zip files created by Dagster Pyspark step launchers. Thanks @maxfirman!

Documentation

• Added a high-level overview page for Logging.

Dagster Cloud

• Added the ability to annotate code locations with custom agent queues, allowing you to route requests for code locations in a single deployment to different agents. For example, you can route requests for one code location to an agent running in an on-premise data center but requests for all other code locations to another agent running in the cloud. For more information, see the docs.

1.5.14 / 0.21.14 (libraries)

New

• Viewing logs for a sensor or schedule tick is now a generally available feature.
  • The feature flag to view sensor or schedule tick logs has been removed, as the feature is now enabled by default.
  • Logs can now be viewed even when the sensor or schedule tick fails.
  • The logs are now viewable in the sensor or schedule tick modal.
• graph_multi_assets can now accept inputs as kwargs.
• [ui] The tick timeline for schedules and sensors now defaults to showing all ticks, instead of excluding skipped ticks. The previous behavior can be enabled by unchecking the “Skipped” checkbox below the timeline view.
• [ui] The updated asset graph is no longer behind an experimental flag. The new version features a searchable left sidebar, a horizontal DAG layout, context menus and collapsible groups!

Bugfixes

• [ui] Fix layout and scrolling issues that arise when a global banner alert is displayed in the app.
• [ui] Use a larger version of the run config dialog in the Runs list in order to maximize the amount of visible config yaml.
• [ui] When a software-defined asset is removed from a code location, it will now also be removed from global search.
• [ui] When selecting assets in the catalog, you can now opt to materialize only “changed and missing” items in your selection.
• [ui] The “Open in Launchpad” option on asset run pages has been updated to link to the graph of assets or asset job instead of an unusable launchpad page.
• [ui] Partition status dots of multi-dimensional assets no longer wrap on the Asset > Partitions page.
• [asset checks] Fixed a bug that caused the resource_defs parameter of @asset_check to not be respected
• [ui] Fixed an issue where schedules or sensors with the same name in two different code locations sometimes showed each others runs in the list of runs for that schedule or sensor.
• [pipes] Fixed an issue with the PipesFileMessageReader that could cause a crash on Windows.
• Previously, calling context.log in different threads within a single op could result in some of those log messages being dropped. This has been fixed (thanks @quantum-byte!)
• [dagster-dbt] On Dagster run termination, the dbt subprocess now exits gracefully to terminate any inflight queries that are materializing models.

Breaking Changes

• The file_manager property on OpExecutionContext and AssetExecutionContext has been removed. This is an ancient property that was deprecated prior to Dagster 1.0, and since then had been raising a NotImplementedError whenever invoked.

Community Contributions

• Added the Hashicorp Nomad integration to the documentation’s list of community integrations. Thanks, @ThomAub!
• [dagster-deltalake] Fixed an error when passing non-string valued options and extended the supported data types by the arrow type handler to support pyarrow datasets which allows for lazily loading delta tables. Thanks @roeap!

Experimental

• [dagster-pipes] The subprocess and databricks clients now forward termination to the external process if the orchestration process is terminated. A forward_termination argument is available for opting out.

Documentation

• Fixed an error in the asset checks factory code example.

Dagster Cloud

• The UI now correctly displays failed partitions after a single-run backfill occurs. Previously, if a single-run backfill failed, the corresponding partitions would not display as failed.
• Several performance improvements when submitting Snowflake metrics to Dagster Cloud Insights.
• Fixed an error which would occur when submitting Snowflake metrics for a removed or renamed asset to Dagster Cloud Insights.

1.5.13 / 0.21.13 (libraries)

New

• The SensorEvaluationContext object has two new properties: last_sensor_start_time and is_first_tick_since_sensor_start. This enables sensor evaluation functions to vary behavior on the first tick vs subsequent ticks after the sensor has started.
• The asset_selection argument to @sensor and SensorDefinition now accepts sequence of AssetsDefinitions, a sequences of strings, or a sequence of AssetKeys, in addition to AssetSelections.
• [dagster-dbt] Support for dbt-core==1.3.* has been removed.
• [ui] In code locations view, link to git repo when it’s a valid URL.
• [ui] To improve consistency and legibility, when displaying elapsed time, most places in the app will now no longer show milliseconds.
• [ui] Runs that were launched by schedules or sensors now show information about the relevant schedule or sensor in the header, with a link to view other runs associated with the same tick.
• [dagster-gcp] Added a show_url_only parameter to GCSComputeLogManager that allows you to configure the compute log manager so that it displays a link to the GCS console rather than loading the logs from GCS, which can be useful if giving Dagster access to GCS credentials is undesirable.

Bugfixes

• Fixed behavior of loading partitioned parent assets when using the BranchingIOManager
• [ui] Fixed an unwanted scrollbar that sometimes appears on the code location list.

Community Contributions

• Fixed a bug where dagster would error on FIPS-enabled systems by explicitly marking callsites of hashlib.md5 as not used for security purposes (Thanks @jlloyd-widen!)
• [dagster-k8s] Changed execute_k8s_job to be aware of run-termination and op failure by deleting the executing k8s job (Thanks @Taadas!).
• [dagstermill] Fixed dagstermill integration with the Dagster web UI to allow locally-scoped static resources (required to show certain frontend-components like plotly graphs) when viewing dagstermill notebooks (Thanks @aebrahim!).
• [dagster-dbt] Fixed type annotation typo in the DbtCliResource API docs (Thanks @akan72!)

Experimental

• [pipes] Methods have been added to facilitate passing non-Dagster data back from the external process (report_custom_message ) to the orchestration process (get_custom_messages).
• [ui] Added a “System settings” option for UI theming, which will use your OS preference to set light or dark mode.

Documentation

• [graphql] - Removed experimental marker that was missed when the GraphQL client was fully released
• [assets] - Add an example for using retries with assets to the SDA concept page
• [general] - Fixed some typos and formatting issues