{"id":"src_h0iY0kuHrhhAemKajfS-1","slug":"dagster","name":"Dagster","type":"github","url":"https://github.com/dagster-io/dagster","orgId":"org_HHYZeLetYDhaPwocGH-oQ","productId":null,"productSlug":null,"org":{"id":"org_HHYZeLetYDhaPwocGH-oQ","slug":"dagster","name":"Dagster"},"isPrimary":false,"isHidden":false,"discovery":"curated","metadata":"{\"evaluatedMethod\":\"github\",\"evaluatedAt\":\"2026-04-11T14:04:26.103Z\",\"changelogUrl\":\"https://github.com/dagster-io/dagster/blob/HEAD/CHANGES.md\",\"changelogDetectedAt\":\"2026-04-11T14:07:22.657Z\",\"wellKnownSweptAt\":\"2026-06-24T06:00:01.224Z\"}","notice":null,"kind":"platform","stars":15737,"starsFetchedAt":"2026-06-24T03:01:11.069Z","releaseCount":110,"releasesLast30Days":4,"avgReleasesPerWeek":1,"latestVersion":"1.13.10","latestDate":"2026-06-18T19:23:58.000Z","changelogUrl":"https://github.com/dagster-io/dagster/blob/HEAD/CHANGES.md","hasChangelogFile":true,"lastFetchedAt":"2026-06-24T03:01:11.069Z","lastPolledAt":"2026-06-24T03:01:09.665Z","trackingSince":"2024-05-23T21:58:12.000Z","releases":[{"id":"rel_vZMWqmbJK5HPm_8VzBpH7","version":"1.13.10","type":"feature","title":"1.13.10 (core) / 0.29.10 (libraries)","summary":"### Bugfixes\n\n- Fixed a bug where `DagsterInstance.get_latest_materialization_event` (and `get_asset_records`) could return a stale pre-wipe materiali...","titleGenerated":null,"titleShort":null,"content":"### Bugfixes\n\n- Fixed a bug where `DagsterInstance.get_latest_materialization_event` (and `get_asset_records`) could return a stale pre-wipe materialization for a wiped asset once a new run targeting the asset started or an observation was reported. In Dagster+, fixed the analogous bug where wiping partitions could leave the wiped partition's materialization as the asset's latest materialization.\n- Fixed an issue where an asset backfill could get stuck — emitting no further runs but never completing — when an asset whose partitions definition includes certain dates depended on an asset whose partitions definition excludes them.\n- Fixed a performance issue where assets partitioned by a cron schedule using an explicit minute list (e.g. `0,30 * * * *`) computed partition counts much more slowly than the equivalent `*/30` schedule.\n- Improved the performance of loading the backfills for a partition set on deployments with a large number of backfills, which previously fetched and deserialized every backfill in the deployment on each request.\n- [ui] Fixed a performance regression that caused views with truncated text, such as the asset catalog, to render slowly.\n- [dagster-cloud] Fixed an issue where importing `dagster_cloud.serverless` could fail with a missing `boto3` dependency on serverless deployments that did not install the `[serverless]` extra.","publishedAt":"2026-06-18T19:23:58.000Z","fetchedAt":"2026-06-18T22:01:56.838Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.13.10","media":[],"coverageCount":0},{"id":"rel_fjEdKwY7YjQUI9zmxPVJQ","version":"1.13.9","type":"feature","title":"1.13.9 (core) / 0.29.9 (libraries)","summary":"### New\n\n- Asset group names may now contain `/` separators to define hierarchical groups (e.g. `marketing/ads`). Hierarchical groups can be selected ...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- Asset group names may now contain `/` separators to define hierarchical groups (e.g. `marketing/ads`). Hierarchical groups can be selected with wildcards in asset selections (e.g. `group:\"marketing/*\"`) and are rendered as nested groups in the asset graph.\n- Added an `is:` filter to the asset selection syntax and search filters to select assets by type (e.g. `is:external`, `is:materializable`).\n- [dg] `DG_PROJECT_PYTHON_EXECUTABLE` in a project's `.env` is now parsed via `python-dotenv`, so `export KEY=value`, quoted values, and trailing comments are honored.\n- [ui] When filtering assets in the lineage view with the selection input, a \"Save selection\" button now allows creating a saved selection directly from the input value.\n- [ui] Redesigned the recent updates timeline on asset pages.\n- [dagster-cloud] Uploads through S3 presigned URLs (code location snapshots, serverless I/O manager objects, compute logs, and PEX files) now retry on transient HTTP 500 errors from S3.\n- [dagster-dlt] `DltLoadCollectionComponent` now supports `partitions_def` and `backfill_policy`. (Thanks, [@Benjamin0313](https://github.com/Benjamin0313)!)\n- [helm] User code deployments now support running multiple replicas via `replicaCount`. All replicas of a deployment share a consistent gRPC server ID, so multi-replica deployments do not trigger spurious code location reloads. (Thanks, [@HynekBlaha](https://github.com/HynekBlaha)!)\n\n### Bugfixes\n\n- Fixed an issue where date-like strings (e.g. `\"2021-10-30\"`) in YAML config files were converted to datetime objects instead of being passed through as strings.\n- Fixed an issue where run failure sensors did not receive error information when a run failed due to a step failure. The originating step error is now available on the sensor context.\n- Fixed an issue where schedules using cron strings constrained to specific hours or days (e.g. `*/15 9-16 * * 1-5`) were incorrectly treated as ticking uniformly throughout the day, which could produce overcounted partition counts and oversized backfills.\n- Fixed a deadlock that could occur when shutting down event log watchers on Postgres or MySQL storage while a watch callback was concurrently unsubscribing.\n- `TemplatedSqlComponent` now generates a unique default op name based on its template, preventing op name collisions when multiple components omit an explicit execution name.\n- [ui] Fixed an issue where clicking \"View runs\" in the backfill step status dialog did not open the runs dialog.\n- [ui] On the asset partitions page, the focused partition now resets when it falls outside the selected partition range, instead of continuing to display a partition that is no longer in the range.\n\n### Documentation\n\n- [dagster-dbt] Added a \"Blue/green deployments\" section to the dbt patterns and best practices guide, covering the clone-then-swap pattern.","publishedAt":"2026-06-11T19:16:52.000Z","fetchedAt":"2026-06-11T20:02:04.068Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.13.9","media":[],"coverageCount":0},{"id":"rel_W0uopBV6yHDVNhfyVHm0_","version":"1.13.8","type":"feature","title":"1.13.8 (core) / 0.29.8 (libraries)","summary":"### New\n\n- Special characters are now allowed in team `owners` for jobs, schedules, and sensors. (Thanks, [@dragos-pop](https://github.com/dragos-pop)...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- Special characters are now allowed in team `owners` for jobs, schedules, and sensors. (Thanks, [@dragos-pop](https://github.com/dragos-pop)!)\n- Added `kinds` tags and icons for Microsoft Fabric and OneLake. (Thanks, [@MartyP233](https://github.com/MartyP233)!)\n- The BigQuery, Snowflake, and DuckDB I/O managers now skip the table write when an asset returns an empty DataFrame, logging a warning instead. This prevents incorrect type inference and degenerate tables for empty partitions.\n- [ui] The per-code-location \"Docs\" tab is now \"Components\", with its content available under a \"Library\" subtab. Existing `/docs` links continue to work via redirect.\n- [dagster-aws] The EMR PySpark step launcher now honors a configured S3 job package path.\n- [dagster-cloud] `code_server.*` metrics now carry a `server_instance_id` tag identifying the underlying gRPC server process. For multi-replica code locations, the tag identifies whichever replica answered the most recent metrics ping.\n\n### Bugfixes\n\n- `InstigationLogger` now stringifies log record attributes that are not JSON-serializable instead of failing to emit the log. (Thanks, [@jonaslb](https://github.com/jonaslb)!)\n- Fixed a SQL injection vulnerability in `dagster-clickhouse`, `dagster-clickhouse-pandas`, and `dagster-clickhouse-polars` when using dynamic partition keys. ClickHouse partition queries now bind partition key values as driver parameters instead of interpolating them into SQL strings.\n- Fixed an issue where tag values in component YAML files were not coerced correctly.\n- [dg] `dg labs ai dispatch` no longer writes a `plan.md` artifact into version control.\n- [dg] Fixed an error that occurred when using `TypedDict`-typed fields in component configuration.\n- [ui] Fixed partition step status labels and squares that rendered incorrectly after the CSS Modules migration.\n- [ui] Fixed backfill progress not reaching 100% until all runs had completed.\n- [dagster-databricks] Fixed Databricks workspace job list pagination and added retries for rate-limit responses.\n- [dagster-dbt] Fixed `DbtProject.prepare()` to always run `dbt deps` when dependency files are present.\n- [dagster-dbt] Fixed YAML-based translation in `DbtProjectComponent` subclasses to also translate dependency keys.\n- [dagster-dbt] Fixed an issue where dbt unit tests could be ignored unexpectedly.\n- [dagster-dbt] Fixed incorrect asset key translation when generating column lineage with `DbtProjectComponent`.\n- [dagster-dbt] Fixed unbounded recursive copying of the `.local_defs_state()` directory when a dbt project was located at the repository root.\n- [dagster-cloud-cli] Fixed `dg plus deploy` failing with `No module named pip` in `uv`-managed environments.\n- [dagster-cloud-cli] Removed an overly strict dependency-file check from the Docker deploy path.\n\n### Documentation\n\n- Added an integration reference for `dagster-elasticsearch`.\n- Added documentation for the OpenLineage integration.\n- Added documentation for `dagster-hf-datasets`.\n- Added an example covering deployment strategies.","publishedAt":"2026-06-04T18:11:04.000Z","fetchedAt":"2026-06-04T23:01:33.997Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.13.8","media":[],"coverageCount":0},{"id":"rel_psdlA_9MgbuZeUI0M2eLM","version":"1.13.7","type":"feature","title":"1.13.7 (core) / 0.29.7 (libraries)","summary":"### New\n\n- Added an `owners` parameter to `build_schedule_from_partitioned_job` to set owners on the resulting schedule. (Thanks, [@dragos-pop](https:...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- Added an `owners` parameter to `build_schedule_from_partitioned_job` to set owners on the resulting schedule. (Thanks, [@dragos-pop](https://github.com/dragos-pop)!)\n- [dagster-airlift] Added support for Python 3.12, 3.13, and 3.14.\n- [dagster-fivetran] The Fivetran component now supports a `fetch_column_metadata` option to fetch column-level metadata for synced tables.\n- [dagster-k8s] When `includeConfigInLaunchedRuns.enabled` is set in the Helm chart, run pods now inherit `nodeSelector`, `tolerations`, and `podSecurityContext` from user deployment configuration.\n\n### Bugfixes\n\n- Fixed a SQL injection vulnerability in `dagster-clickhouse`, `dagster-clickhouse-pandas`, and `dagster-clickhouse-polars` when using dynamic partition keys. ClickHouse partition queries now use driver parameter binding instead of interpolating partition key values into SQL strings.\n- Fixed a race condition where readers polling for a run to reach `FAILURE` could observe the failed status before the `dagster/failure_reason` tag was written.\n- Fixed a regression where a blocking asset check that did not emit a result (e.g. a dbt test that dbt declined to run under `indirect_selection: cautious` or `buildable`) could silently cause downstream assets to be skipped. Missing blocking check results now allow downstream assets to proceed and log a warning; failed blocking checks continue to fail the step and the run as before.\n- Improved deduplication in `AutomationCondition.any_downstream_conditions()` to prevent recursive blowups in condition size when combined with other automation conditions.\n- [ui] Fixed extra scrollbars appearing in the asset overview and asset sidebar.\n- [dagster-k8s] Fixed an `AttributeError` when using `kubernetes` client v36+, which uses PEP 585 dict syntax (e.g. `dict[str, str]`) in its OpenAPI type annotations. (Thanks, [@vanika02](https://github.com/vanika02)!)","publishedAt":"2026-05-28T17:18:25.000Z","fetchedAt":"2026-05-28T21:02:12.591Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.13.7","media":[],"coverageCount":0},{"id":"rel_F-B6YNC2ermz5fVIk13Gc","version":"1.13.6","type":"feature","title":"1.13.6 (core) / 0.29.6 (libraries)","summary":"### New\n\n- Schedule, sensor, and asset daemon ticks now dispatch instigators round-robin across code locations, preventing a single code location with...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- Schedule, sensor, and asset daemon ticks now dispatch instigators round-robin across code locations, preventing a single code location with many instigators from delaying launches in other code locations.\n- Added `dg api run launch` command for launching runs from the CLI against the Dagster+ API.\n- Improved declarative automation performance for assets sharing the same cron schedule.\n- [ui] The asset catalog now shows a toggle to hide duplicate connections-defined assets when an SDA and a connection target the same table, and the asset sidebar links to matched assets.\n- [dagster-dbt] Added a configurable job pool to `DbtCloudComponent` and `DbtCloudWorkspace` to work around dbt Cloud's one-concurrent-run-per-job limit.\n\n### Bugfixes\n\n- Fixed an issue where asset keys and partitions containing leading \"/\" characters or \"..\" characters would sometimes cause IOManagers to read and write outside of the supplied `base_path`.\n- Fixed a regression where a blocking asset check that did not emit a result (e.g. a dbt test skipped under `indirect_selection: cautious` or `buildable`) would silently cause downstream assets to be skipped. Missing check results now allow downstream assets to proceed; failed checks still fail the step.\n- Softened the `job_snapshot_id` mismatch invariant in execution plan persistence from a crash to a warning, preventing run launch failures when client and server compute slightly different snapshot IDs.\n- Pinned `antlr4-python3-runtime` to `<4.14` to prevent potential breakage from future ANTLR minor version bumps.\n- [ui] Fixed minor flex alignment issues for tags and metadata buttons on asset catalog detail pages.\n- [dagster-k8s] Added support for the PEP 585 `dict[str, str]` syntax used by the `kubernetes` client v36+ when snake-casing model dictionaries, fixing an `AttributeError: module 'kubernetes.client.models' has no attribute 'dict[str, str]'` raised on `kubernetes>=36`. (Thanks, [@vanika02](https://github.com/vanika02)!)\n\n### Documentation\n\n- Added documentation for defining asset dependencies across code locations.\n- Added `dg utils` CLI reference documentation.\n- Added missing `DAGSTER_POSTGRES_HOST` environment variable to the Docker deployment documentation.\n- Expanded Databricks integration documentation with Databricks Connect, serverless compute (Pipes), and UC Volumes patterns.\n- [dagster-dbt] Documented the `FROM_ASSET_FAILURE` retry strategy for dbt asset jobs.","publishedAt":"2026-05-22T18:17:05.000Z","fetchedAt":"2026-05-22T20:01:58.026Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.13.6","media":[],"coverageCount":0},{"id":"rel_kaOvNkOew69exELV6pCP5","version":"1.13.5","type":"feature","title":"1.13.5 (core) / 0.29.5 (libraries)","summary":"### New\n\n- Added kinds tags for Alteryx, Boomi, and SAP.\n- Raised the SQLite `busy_timeout` default from 5s to 30s on `SqliteEventLogStorage` and `Con...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- Added kinds tags for Alteryx, Boomi, and SAP.\n- Raised the SQLite `busy_timeout` default from 5s to 30s on `SqliteEventLogStorage` and `ConsolidatedSqliteEventLogStorage` to better tolerate slow or network-backed `$DAGSTER_HOME` filesystems.\n- [ui] Removed the \"Scheduled\" tab from the runs feed.\n- [ui] The sensor tick timeline now shows more ticks on the newest page, matching the list of ticks shown in the table below.\n- [dagster-k8s] Added a `delete_pod_on_completion` flag to `PipesK8sClient.run`, allowing callers to opt out of the automatic pod deletion at the end of a Pipes run.\n- [dagstermill] Dropped support for papermill 1.x. `dagstermill` now requires `papermill>=2.0.0`.\n\n### Bugfixes\n\n- Job backfills now retry on transient daemon errors such as code-server unreachable, matching the existing behavior for asset backfills. The `DAGSTER_MAX_ASSET_BACKFILL_RETRIES` environment variable has been renamed to `DAGSTER_MAX_BACKFILL_RETRIES`, with a fallback to the old name for backwards compatibility.\n- Fixed a bug where asset checks could be dropped from a `JobDefinition` when selected as part of a subset selection.\n- Fixed a bug where, in a partitioned-asset backfill running multiple partitions concurrently, an inline `AssetCheckResult` could record a `target_materialization` pointing to a different partition's materialization.\n- Fixed a regression introduced in 1.12.10 where `OutputContext.asset_partition_key_range` and `InputContext.asset_partition_key_range` could raise `CheckError: The instance is not available to load partitions` for assets using a `MultiPartitionsDefinition` that includes a `DynamicPartitionsDefinition`.\n- Improved the error message shown when the instance is not available to load dynamic partitions, recommending the use of `partition_loading_context`.\n- [ui] Fixed an issue where viewing the Lineage tab for an asset could cause the page header to disappear.\n- [dagster-dbt] Fixed a bug where, when a dbt asset selection grew large enough to switch from inline `--select`/`--exclude` to a temporary `selectors.yml`, runtime `--exclude` arguments were silently dropped.\n- [dagster-dbt] Fixed runtime selection arguments not being properly applied when used with `@dbt_assets` ops.\n- [dagstermill] Increased the default Jupyter kernel-startup timeout for `dagstermill` notebook ops from 60s to 120s.","publishedAt":"2026-05-15T16:40:58.000Z","fetchedAt":"2026-05-15T21:00:43.633Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.13.5","media":[],"coverageCount":0},{"id":"rel_u5TfxC2uhDyiXlZ36aulh","version":"1.13.4","type":"feature","title":"1.13.4 (core) / 0.29.4 (libraries)","summary":"### New\n\n- `typing.Mapping` and `typing.Sequence` annotations are now supported on op and asset inputs.\n- Added a `path_prefix` parameter to `DagsterG...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- `typing.Mapping` and `typing.Sequence` annotations are now supported on op and asset inputs.\n- Added a `path_prefix` parameter to `DagsterGraphQLClient` to support connecting to webserver deployments behind a non-root path prefix.\n- Added a `storage_kind` field to `TableMetadataSet` to denote the storage system that backs a table (e.g., `snowflake`, `databricks`, `bigquery`).\n- `define_asset_job` now validates owner strings at definition time, producing clearer error messages for invalid owners.\n- [ui] The `schedule:` and `sensor:` selector syntax now matches assets in jobs targeted by the schedule or sensor, in addition to assets directly in the asset selection.\n- [dagster-azure] Added a configurable `endpoint_suffix` parameter to ADLS2 and Blob Storage utilities, resources, components, and compute log manager (also exposed as `endpointSuffix` in the Helm chart for `AzureBlobComputeLogManager`), enabling Azure Government Cloud, Azure China, and other sovereign cloud endpoints.\n- [dagster-dbt] Added a `translation` parameter to `DbtCloudComponent` for customizing how dbt models are translated into Dagster assets.\n- [dagster-soda] Added a new `dagster-soda` library (preview) containing the `SodaScanComponent` for executing Soda Core data quality checks.\n\n### Bugfixes\n\n- Fixed a bug where asset checks could be dropped from a job during subset selection.\n- Asset checks can now be defined on assets whose names contain dots.\n- [dg] Fixed a bug where `dg plus deploy` did not read the local config stored by `dg plus login`.\n- [ui] Fixed the \"Flatten graphs\" toggle in the graph query input on the Launchpad.\n- [ui] Restored CommonMark-compliant Markdown line break rendering in Markdown descriptions and docs blocks. (Thanks, [@vidiyala99](https://github.com/vidiyala99)!)\n- [dagster-airbyte] Fixed an issue where Airbyte job timestamp parsing could fail with newer Airbyte API versions due to stricter ISO format handling.\n- [dagster-aws] `InsufficientFreeAddressesInSubnet` and \"Task provisioning failed\" are now treated as transient ECS stop reasons, so affected runs are retried instead of marked as a permanent failure.\n- [dagster-dbt] Fixed a bug where path-based dbt selectors did not match assets correctly because absolute paths were not calculated relative to the project root.\n- [dagster-dbt] Fixed an issue where conflicting source metadata could spuriously raise an error.\n\n### Documentation\n\n- Added documentation for multi-region failover in Dagster+.\n- Renamed the DuckDB integration documentation to MotherDuck.\n- Rebranded the in-app Compass assistant as Dagster+ AI in documentation.","publishedAt":"2026-05-14T15:31:55.000Z","fetchedAt":"2026-05-14T20:00:53.782Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.13.4","media":[],"coverageCount":0},{"id":"rel_dQ0kJEUko581Za56gvJ8b","version":"1.13.3","type":"feature","title":"1.13.3 (core) / 0.29.3 (libraries)","summary":"### New\n\n- Added an `owners` parameter to `define_asset_job`, mirroring the field on regular jobs.\n- Improved error messages when required config is m...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- Added an `owners` parameter to `define_asset_job`, mirroring the field on regular jobs.\n- Improved error messages when required config is missing in Dagster jobs, with clearer guidance on which fields are missing and example config to provide.\n- `LOGS_CAPTURED` event messages no longer say \"Started capturing logs\", since compute log managers typically upload logs on completion rather than streaming in real time.\n- [ui] Added client-side validation for the deployment settings YAML editor that warns when unknown keys are detected.\n- [ui] Op tags are now shown on the asset details page in a separate \"Op tags\" row, alongside the asset's own tags.\n- [ui] Redesigned the sensor dry run dialog with a stacked cursor layout, copy buttons for cursor values, and an inline run config preview.\n- [dagster-clickhouse] Added new `dagster-clickhouse`, `dagster-clickhouse-pandas`, and `dagster-clickhouse-polars` libraries with native ClickHouse resources, IO managers, and `dg` components.\n- [dagster-cloud] The `EcsUserCodeLauncher` now accepts a `repository_credentials` config option, allowing ECR credentials to be configured at the agent or deployment level instead of only per code location.\n- [dagster-postgres] Added workload identity federation (WIF) authentication for PostgreSQL via a new `auth_provider` config option (`azure_wif`, `gcp_wif`, or `aws_wif`), with optional extras `dagster-postgres[azure]`, `dagster-postgres[gcp]`, and `dagster-postgres[aws]`. The Helm chart supports WIF via `global.postgresqlAuthWifEnabled`. (Thanks, [@JohnMav](https://github.com/JohnMav)!)\n\n### Bugfixes\n\n- Fixed an error when starting a schedule whose name was previously used for a sensor (or vice versa).\n- Fixed a race condition in Pipes that could cause dynamically-added log readers to be missed.\n- [dg] Fixed bugs in the GitLab hybrid scaffolder used by `dg plus deploy configure`.\n- [ui] Fixed the open/close behavior of the partition selector in the materialization dialog.\n- [ui] Fixed false-positive syntax errors in asset selection inputs while the autocomplete dropdown was open.\n- [ui] Fixed `key:value` autocompletion in search inputs not advancing into value-suggestion context when accepting a key with the Enter key.\n- [ui] Fixed the asset catalog \"Group by Owner\" and \"Group by Tags\" views not showing assets with empty owner or tag arrays under a \"None\" section.\n- [ui] Fixed asset selection summary tiles with long titles visually overlapping with adjacent UI.\n- [ui] Fixed monospace text in several places that had reverted to the default font.\n- [dagster-airbyte] Fixed errors parsing timestamps from newer versions of the Airbyte API.\n- [dagster-cloud] Fixed an issue where the `--defs-state-info` argument was applied to the multipex server command but not to the gRPC server command in serverless deployments.\n- [dagster-dbt] Fixed an issue where dbt assets configured with `enable_duplicate_source_asset_keys` could emit duplicate dependency entries and ambiguous source metadata when multiple dbt sources resolved to the same asset key.\n- [dagster-k8s] Added a workaround for an upstream issue in the Kubernetes Python client where setting the `NO_PROXY` or `no_proxy` environment variable did not affect the configuration of Kubernetes API calls.\n- [dagster-snowflake] Replaced deprecated Pydantic `validator` usage with `field_validator` to eliminate Pydantic deprecation warnings.\n\n### Documentation\n\n- Added documentation for writing unit tests for declarative automation conditions.\n- Added documentation for branch deployment RBAC.\n- Added a dedicated documentation page for branch deployment concurrency settings.\n- Documented the new asset-event webhook tokens.\n- Clarified asset metric monitor behavior in the alerts documentation.\n- Added required API scopes to the Databricks connection documentation.\n- Updated the Databricks connection documentation with an OAuth flow for service principals.\n- [dg] Documented the `dg` CLI configuration option for setting a custom virtual environment path.","publishedAt":"2026-04-30T20:46:18.000Z","fetchedAt":"2026-04-30T23:01:08.755Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.13.3","media":[],"coverageCount":0},{"id":"rel_b0DvbCPYGniQxb2c5LqZ9","version":"1.13.2","type":"feature","title":"1.13.2 (core) / 0.29.2 (libraries)","summary":"### New\n\n- [ui] Users can now hold Cmd or Ctrl while clicking launch, materialize, re-execute, or retry buttons to open the resulting run in a new\n  b...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- [ui] Users can now hold Cmd or Ctrl while clicking launch, materialize, re-execute, or retry buttons to open the resulting run in a new\n  browser tab instead of navigating away from the current page.\n- [ui] Added an Azure DevOps kind tag icon for assets tagged with the `azuredevops` kind.\n- [dg] The `dg utils integrations` sub-command has been removed.\n- [dagster-databricks] `DatabricksClientResource` now accepts a `credentials_strategy` argument, enabling federated and custom authentication flows via the Databricks SDK's `CredentialsStrategy` protocol. (Thanks, [@hbellur0526](https://github.com/hbellur0526)!)\n\n### Bugfixes\n\n- Fixed an issue where the asset daemon could fail when encountering foreign sensor cursors in automation condition sensor state.\n- Fixed an issue where run retries were sometimes not executed by the event log consumer daemon.\n- Fixed an issue where an invalid multi-partition key format could cause errors when computing partition statuses.\n- [dg] Fixed an issue where the `--api-token` flag was ignored when passed to `dg` CLI commands.\n- [dg] Fixed an issue in `dg api asset-checks` where the command used a non-existent top-level GraphQL resolver path.\n- [ui] Fixed incorrect font rendering caused by a CSS variable name mismatch.\n- [ui] Fixed an issue where the run config editor dialog displayed at an incorrect height.\n- [ui] Fixed an issue where clicking asset selection autocomplete suggestions could cause the input to lose focus.\n- [ui] Fixed an issue where the Users table in Org Settings did not support horizontal scrolling.\n- [dagster-cloud-cli] Fixed GitHub Enterprise authentication for branch deployment CI/CD workflows.\n- [dagster-databricks] Fixed a `TypeError` when `credentials_strategy` was `None`.\n- [dagster-dbt] Fixed a thread-safety issue in concurrent metadata fetching that could cause intermittent errors.\n- [dagster-snowflake-polars] Fixed an issue where dynamic partition keys were not properly escaped.\n\n### Dagster Plus\n\n- [ui] Branch deployments now expose run queue settings in the run queue configuration dialog.","publishedAt":"2026-04-23T18:30:38.000Z","fetchedAt":"2026-04-23T21:00:33.685Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.13.2","media":[],"coverageCount":0},{"id":"rel_L0K8JDoK1OdCCzpRXMpQN","version":"1.13.1","type":"feature","title":"1.13.1 (core) / 0.29.1 (libraries)","summary":"### New\r\n\r\n- Added `PipesCompositeMessageReader` (preview) to support multiple concurrent message streams in a single Pipes session.\r\n- Added `sensor:...","titleGenerated":null,"titleShort":null,"content":"### New\r\n\r\n- Added `PipesCompositeMessageReader` (preview) to support multiple concurrent message streams in a single Pipes session.\r\n- Added `sensor:`, `schedule:`, and `job:` attribute support to the asset selection syntax (e.g., `sensor:my_sensor`, `job:my_job`).\r\n- Added `automation_type:` attribute support to the asset selection syntax, allowing queries like `automation_type:schedule` or `automation_type:sensor`. (Thanks, [@bengotow](https://github.com/bengotow)!)\r\n- State-backed integration components (e.g., `AirbyteWorkspaceComponent`, `FivetranWorkspaceComponent`) now default to `LOCAL_FILESYSTEM` state storage instead of `legacy_code_server_snapshots`.\r\n- [dg] Added `dg api issue create` and `dg api issue update` commands.\r\n- [dg] Added filter support to `dg api issue list`.\r\n- [ui] Improved asset selection autocomplete performance.\r\n- [dagster-dbt] `DagsterDbtTranslatorSettings.enable_source_metadata` now defaults to `True`, enabling upstream asset key remapping based on dbt source table names by default.\r\n\r\n### Bugfixes\r\n\r\n- Fixed a SQL injection vulnerability in several IO managers. We recommend all users upgrade. More details can be found at https://github.com/dagster-io/dagster/security/advisories/GHSA-mjw2-v2hm-wj34.\r\n- Fixed an issue where runs executed via `execute_in_process()` would sometimes fail to display the step timeline in the Dagster UI.\r\n- Fixed a bug where multi-asset definitions containing virtual assets would produce incorrect execution plans.\r\n- [ui] Fixed the tick result button for sensors using dynamic partitions.\r\n- [dagster-aws] `PickledObjectS3IOManager` now defaults the S3 key prefix to an empty string when none is provided. (Thanks, [@aksestok](https://github.com/aksestok)!)\r\n- [dagster-databricks] `PipesDatabricksClient.run_multi_task` and `PipesDatabricksServerlessClient.run_multi_task` now give each submitted task its own message destination by default, fixing chunk-file collisions between concurrent tasks.\r\n- [dagster-dbt] Fixed the dbt Cloud v2 polling sensor and adhoc job to use stable, ID-based identifiers, preventing naming conflicts.\r\n- [dagster-dbt] Fixed the dbt Cloud v2 polling sensor to correctly filter out runs from adhoc jobs.\r\n\r\n### Documentation\r\n\r\n- Added a guide for virtual assets.\r\n- Added documentation for partitioned asset checks.\r\n- Added documentation for the `free_slots_after_run_end_seconds` concurrency configuration option.\r\n- Clarified SCIM provisioning and SSO permission requirements in the authentication documentation.\r\n- Added a guide for migrating Dagster+ from the US to the EU control plane.","publishedAt":"2026-04-17T19:33:16.000Z","fetchedAt":"2026-04-17T20:08:29.323Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.13.1","media":[],"coverageCount":0},{"id":"rel_aSQFP62NqOzBdq4Y19clK","version":"1.13.0","type":"feature","title":"1.13.0 (core) / 0.29.0 (libraries)","summary":"### Major Changes Since 1.12.0\n\n- **AI-assisted development**: Released [dagster-io/skills](https://github.com/dagster-io/skills), a collection of Dag...","titleGenerated":null,"titleShort":null,"content":"### Major Changes Since 1.12.0\n\n- **AI-assisted development**: Released [dagster-io/skills](https://github.com/dagster-io/skills), a collection of Dagster-focused AI skills for coding agents like Claude Code, OpenAI Codex, and others. Expanded `dg api` commands for programmatic inspection of assets, runs, jobs, schedules, and more.\n- **Partitioned asset checks**: Asset checks can now target specific partitions of an upstream asset, aligning data quality logic with how partitioned data is produced and monitored.\n- **State-backed components enabled by default**: Integrations that depend on external metadata (dbt, Fivetran, Airbyte, Tableau, Looker, etc.) now use persisted local state by default, providing a more predictable code location loading experience.\n- **Virtual assets (preview)**: New `is_virtual` parameter on `@asset` and `AssetSpec` for modeling assets like database views that automatically reflect upstream changes without explicit materialization.\n- **20+ new components**: Added or expanded components for dbt Cloud, Spark, Azure (Blob Storage, ADLS2), GCP (BigQuery, GCS, Dataproc), Databricks, Tableau, Looker, Census, Polytomic, and more. Integrations gained richer observability, metadata, and operational support.\n- **Deeper integration support**: dbt Cloud supports partitioned assets; Databricks gained job-level subsetting and auto-cancel on run termination; Fivetran added polling sensors, retry-on-reschedule, and resync support; BI integrations auto-enrich assets with table metadata for cross-system lineage.\n- **Dagster+ improvements**: Organization-level timezone settings, service users for Pro accounts, more resilient code server redeploy behavior, improved agent failure recovery, and expanded insights and alerting workflows.\n\n### Breaking Changes\n\n- Removed deprecated `external_asset_from_spec` and `external_assets_from_specs`. Use `AssetSpec` inputs directly to `Definitions(...)` or `AssetsDefinition(specs=[...])` instead.\n- Removed deprecated single-`AssetKey` `deps` argument support from asset dependencies. Use a sequence of `AssetDep` objects instead.\n- Removed deprecated `get_all_asset_specs` from `Definitions`.\n- Removed deprecated `legacy_freshness_policy` parameter from `@observable_source_asset`.\n- Removed deprecated `auto_observe_interval_minutes` parameter from `@observable_source_asset`.\n- Removed deprecated `legacy_freshness_policies_by_output_name` parameter from `AssetsDefinition`.\n- Removed deprecated `load_component_at_path` from `ComponentLoadContext`. Use `context.load_component` instead.\n- Removed deprecated `build_defs_at_path` from `ComponentLoadContext`.\n- [dagster-airbyte] Removed deprecated `AirbyteState` enum (use `AirbyteJobStatusType` instead) and removed deprecated `legacy_freshness_policy` and `auto_materialize_policy` parameters from `build_airbyte_assets()`.\n- [dagster-looker] Removed deprecated `DagsterLookerResource.build_defs`, `get_asset_key`, `get_dashboard_asset_key`, `get_explore_asset_key`, `get_view_asset_key` methods, and `Type[DagsterLookerApiTranslator]` support from API helpers.\n- [dagster-powerbi] Removed deprecated `PowerBIWorkspace.build_defs()`, translator key helpers (use `get_asset_spec()` instead), and `Type[DagsterPowerBITranslator]` support in `load_powerbi_asset_specs()` (pass an instance instead).\n- [dagster-sigma] Removed deprecated `SigmaOrganization.build_defs()`, `DagsterSigmaTranslator.get_asset_key()` (use `get_asset_spec(...).key` instead), and `Type[DagsterSigmaTranslator]` support in `load_sigma_asset_specs()` (pass an instance instead).\n\n### New\n\n- (Preview) Added support for virtual assets. The `@asset` decorator and `AssetSpec` now accept an `is_virtual` parameter for defining assets that represent views or derived tables that don't need to be materialized. Virtual assets are supported in staleness calculations, execution planning, and declarative automation.\n- Job-level config defaults are now applied when partial config is provided to a run.\n- [dagster-dbt] Added `enable_dbt_views_as_virtual_assets` setting to `DbtTranslatorSettings` for automatically treating dbt views as virtual assets.\n\n### Bugfixes\n\n- Fixed an issue where a sensor targeting a job with `run_tags` and specifying an `asset_selection` in the `RunRequest` would not apply the job's `run_tags` to the resulting run.\n- Fixed a potential error in YAML config snapshot conversion when encountering `None` fields.\n- [dg] Fixed `dg plus deploy configure` generating a GitHub Action that used Docker instead of the PEX build strategy.\n- [dagster-cloud-cli] PR comments in CI are now scoped by deployment name, preventing overwrites across deployments.\n- [ui] Fixed \"Missing\" partition selection for time-based partitioned assets.\n- [ui] Fixed raw log display rendering after `ansi-to-react` library update.\n- [ui] \"Terminate all runs\" dialog now handles extremely large sets of runs more reliably.\n\n### Documentation\n\n- Added Dagster+ agent configuration page for serverless and hybrid deployments.\n- Added data portability documentation page.\n- Reorganized run isolation documentation for hybrid and serverless deployments.\n- Added ELT pipeline example with dlt and Sling.\n\n### Dagster Plus\n\n- Added percent-change comparison type for metric monitor alerts.\n- Added SCIM Groups filter support for `members.value eq` queries.\n- Added MCP server integration providing AI assistants with access to Dagster Cloud operations.\n- Fixed an issue where the Dagster+ Kubernetes agent would emit log noise about `DAGSTER_CLOUD_RAW_GIT_URL` and `DAGSTER_CLOUD_GIT_URL` environment variables when `onlyAllowUserDefinedK8sConfigFields` was set.\n- Fixed incorrect alert type label for metrics alerts.\n- Fixed Databricks connections failing with an \"unable to start warehouse\" error.","publishedAt":"2026-04-09T18:57:35.000Z","fetchedAt":"2026-04-11T14:07:22.048Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.13.0","media":[],"coverageCount":0},{"id":"rel_mVXJ_UKHfDVeQvVfrXMk6","version":"1.12.22","type":"feature","title":"1.12.22 (core) / 0.28.22 (libraries)","summary":"### New\n\n- [dg] `dg` projects can now configure `agent_queue` and `image` in `pyproject.toml` under `[tool.dg.project]`, which are included in the gen...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- [dg] `dg` projects can now configure `agent_queue` and `image` in `pyproject.toml` under `[tool.dg.project]`, which are included in the generated `dagster_cloud.yaml` when running `dg plus deploy`.\n- [dg] Added `dg api job list` and `dg api job get` commands for querying job metadata including schedules, sensors, and tags.\n- [dg] Added `dg api asset-check list`, `dg api asset-check get-executions`, and `dg api asset get-partition-status` commands.\n- [ui] The asset overview page now shows a loading spinner for \"Latest materialization\" while data is loading, instead of a dash.\n- [ui] Removed the legacy asset catalog component and the `flagAssetCatalogSidebar` feature flag. The asset catalog sidebar is now always enabled.\n- [ui] The pipeline snapshot link is no longer shown in the Run Actions Menu for hidden asset group jobs.\n- [dagster-aws] The `EcsRunLauncher` and Dagster+ ECS agent now supply idempotency tokens when creating ECS services and tasks, improving retry behavior after transient failures.\n- [dagster-dbt] `DbtCloudComponent` now supports an option to include a polling sensor for monitoring dbt Cloud job runs.\n\n### Bugfixes\n\n- Fixed `snap_to_yaml` incorrectly removing empty dicts that represent valid config values for `Permissive`, `Map`, and `Noneable` config types.\n- Fixed an issue where resources defined in parent components could incorrectly trigger `DagsterInvalidDefinitionError` during nested component `post_processing` resolution. (Thanks, [@vidiyala99](https://github.com/vidiyala99)!)\n- [dagster-aws] Fixed `PipesECSClient` incorrectly treating a task that failed to start as a successful execution.\n- [dagster-fivetran] Fixed an incorrect connector URL format generated by the Fivetran integration.\n- [ui] Fixed a performance issue where canceling a backfill before any runs executed would unnecessarily fetch the entire asset materialization history.\n- [dg] Fixed `dg plus deploy` not correctly pulling in environment variables when refreshing definitions state for state-backed components.\n- [ui] Fixed ANSI color rendering in run logs.\n- [ui] Fixed a visual rendering issue with the graph depth input field.\n\n### Documentation\n\n- Added a migration guide for moving from sensors to declarative automation.\n- Added documentation for the ECS executor.\n\n### Dagster Plus\n\n- Alert policies can now be muted for a configurable duration. Muted policies do not send notifications and show when they will resume.\n- [dagster-dbt] Added `dg plus integrations dbt download-manifest` command to download dbt manifests from Dagster Plus for local development.","publishedAt":"2026-04-02T17:20:58.000Z","fetchedAt":"2026-04-11T14:07:22.048Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.12.22","media":[],"coverageCount":0},{"id":"rel_DKENaovdflc2tkuc6FNuA","version":"1.12.21","type":"feature","title":"1.12.21 (core) / 0.28.21 (libraries)","summary":"### New\n\n- Removed the `setuptools<82` pin from the `dagster` package.\n- Added support for the `partitions` attribute in asset selection syntax to fil...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- Removed the `setuptools<82` pin from the `dagster` package.\n- Added support for the `partitions` attribute in asset selection syntax to filter assets by partition definition type (e.g., `partitions:\"static\"`).\n- [dagster-spark] Added Spark Declarative Pipeline support in feature preview.\n- [ui] Added a date range picker to the backfill modal for date-formatted partitions.\n- [ui] The \"Report evaluation\" action for asset checks has been moved to a consolidated dropdown menu.\n\n### Bugfixes\n\n- [dagster-dbt] Fixed issue that could cause `DbtProjectComponent`s with custom translation methods to not work with utilities like `build_schedule_from_dbt_selection`.\n- [ui] Fixed asset catalog sidebar not clearing key prefix filters when navigating back to root.\n- [ui] Fixed deployment switcher button text color in Light Mode.\n- [ui] Fixed duplicate \"Catalog\" breadcrumb on asset detail pages.\n- [ui] Fixed lineage graph edges disappearing when zoomed out by increasing the maximum visible edge limit.\n\n### Documentation\n\n- Added cross-account service discovery documentation for ECS agents, including the `service_discovery_role_arn` configuration parameter.\n- Added Snowflake EL ingestion pattern documentation.","publishedAt":"2026-03-26T16:05:17.000Z","fetchedAt":"2026-04-11T14:07:22.048Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.12.21","media":[],"coverageCount":0},{"id":"rel_S-qdxmdKkKXgDP6UOQuTD","version":"1.12.20","type":"feature","title":"1.12.20 (core) / 0.28.20 (libraries)","summary":"### New\n\n- Execution context classes (`OpExecutionContext`, `AssetExecutionContext`, `AssetCheckExecutionContext`) now expose a `multi_partition_key` ...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- Execution context classes (`OpExecutionContext`, `AssetExecutionContext`, `AssetCheckExecutionContext`) now expose a `multi_partition_key` property that returns a `MultiPartitionKey` when the current run is a multi-partition run.\n- Added `Braze` and `Runpod` kind tags. (Thanks, [@dragos-pop](https://github.com/dragos-pop)!)\n- [dagster-databricks] The Databricks job run URL is now rendered as a clickable link in the Dagster UI.\n- [dagster-dbt] Added `DbtCloudComponent` for loading dbt Cloud projects as Dagster assets using the Components API.\n- [dagster-dbt] The `dbt_cloud_assets` decorator now supports partitioned assets via the `partitions_def` parameter.\n- [dagster-fivetran] Added a polling sensor for Fivetran observability, which detects externally-triggered syncs and emits materialization events.\n- [dagster-fivetran] `FivetranWorkspace` now supports a `retry_on_reschedule` option to automatically retry syncs rescheduled by Fivetran due to quota limits, as well as `resync` operations.\n- [dagster-fivetran] The Fivetran translator now includes sync schedule and custom report metadata on connector assets.\n- [dagster-k8s] The Dagster Helm chart and Dagster+ Kubernetes Agent Helm chart now support `k8sApiCaBundlePath` to configure a custom CA certificate path for Kubernetes API communication.\n- [dagster-k8s] Code location server Kubernetes Services now support a `service_spec_config` field for arbitrary Kubernetes Service spec overrides (for example, `clusterIP: None` for headless services).\n\n### Bugfixes\n\n- Fixed an issue where time window partitions with exclusions would sometimes create more runs than needed when using single-run backfills.\n- Fixed a \"Cannot access partition_key for a non-partitioned run\" error that could occur with multi-asset definitions that included non-partitioned assets or asset checks alongside partitioned ones.\n- [dagster-aws] Fixed `s3_pickle_io_manager` failing with dynamic outputs when step keys contain bracket characters in the generated S3 object path.\n- [dagster-aws] Fixed an issue in `PipesEMRServerlessClient` where a custom CloudWatch log group name configured in `monitoringConfiguration.cloudWatchLoggingConfiguration.logGroupName` was ignored, causing log streaming to always use the default `/aws/emr-serverless` log group. (Thanks, [@kchainani-figma](https://github.com/kchainani-figma)!)\n- [ui] Fixed the asset recent updates trend visualization when multiple event types share the same run ID.\n- [ui] Fixed text wrapping and spacing in the asset event detail view for long partition names and run titles.\n\n### Documentation\n\n- Added a troubleshooting guide for Kubernetes agent network connectivity issues, including TCP keepalive configuration recommendations for Helm chart deployments.","publishedAt":"2026-03-19T20:34:40.000Z","fetchedAt":"2026-04-11T14:07:22.048Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.12.20","media":[],"coverageCount":0},{"id":"rel_G0Y2qiDEE8i5UY5vBJu7C","version":"1.12.19","type":"feature","title":"1.12.19 (core) / 0.28.19 (libraries)","summary":"### New\n\n- Added a \"Report Execution\" dialog to the asset checks detail view, allowing users to manually record check evaluation results.\n- Added data...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- Added a \"Report Execution\" dialog to the asset checks detail view, allowing users to manually record check evaluation results.\n- Added database pool configuration options (`--db-pool-recycle`, `--db-pool-pre-ping`, and others) to `dg dev` and `dagster dev`.\n- Added `dg plus config view` command for inspecting the current CLI configuration.\n- [ui] Updated the Usage dialog and Run timeline to display \"Jobless asset materializations\" (previously \"Ad hoc materializations\") with a tooltip describing what is grouped within this category.\n- [ui] Planned run events are now excluded from the event count shown in the run log filter.\n- [dagster-azure] Added component support for `dagster-azure`, including `AzureBlobStorageResourceComponent` and `ADLS2ResourceComponent` for declarative YAML configuration of Azure resources.\n- [dagster-databricks] `DatabricksAssetBundleComponent` is now subsettable at the job level, enabling selective execution of individual Databricks tasks.\n- [dagster-databricks] `DatabricksAssetBundleComponent` now uses the Databricks CLI to resolve variable references to task and job names in bundle templates.\n- [dagster-databricks] Databricks jobs are now cancelled when the corresponding Dagster run is terminated in `DatabricksWorkspaceComponent`.\n- [dagster-dbt] `dagster-dbt` now prefers `dbt-core` for manifest parsing when it is installed.\n- [dagster-gcp] Added `BigQueryResourceComponent`, `GCSResourceComponent`, `GCSFileManagerResourceComponent`, and `DataprocResourceComponent` for declarative YAML configuration of GCP resources.\n- [dagster-gcp] `BigQueryIOManager` now supports a configurable `write_mode` parameter (`truncate`, `replace`, or `append`).\n\n### Bugfixes\n\n- Fixed an issue where auto-run reexecution would attempt to rerun jobs belonging to already-completed or cancelled backfills.\n- Fixed an issue where backfill errors that were subsequently retried would remain incorrectly associated with the backfill.\n- `dg plus pull env` now merges pulled secrets into the existing `.env` file instead of replacing it, preserving any locally-set variables not present in Dagster Plus.\n- [ui] Fixed rendering of newlines in markdown blockquotes in the UI.\n- [dagster-databricks] Fixed a `KeyError` for `run_page_url` in `DatabricksWorkspaceComponent`.\n- [dagster-databricks] Fixed asset mapping in `DatabricksAssetBundleComponent` and `DatabricksWorkspaceComponent` to use job and task key combinations, preventing conflicts when task keys are not unique across jobs.\n\n### Dagster Plus\n\n- The Dagster+ agent now automatically redeploys local code servers that enter a failure state when the control plane expects them to be loaded.","publishedAt":"2026-03-12T20:00:54.000Z","fetchedAt":"2026-04-11T14:07:22.048Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.12.19","media":[],"coverageCount":0},{"id":"rel_2j9Ju_R9UG3Ou4MISExpx","version":"1.12.18","type":"feature","title":"1.12.18 (core) / 0.28.18 (libraries)","summary":"### New\r\n\r\n- Added event type filtering to the asset Recent Updates timeline, allowing users to toggle between Materializations and Observations when ...","titleGenerated":null,"titleShort":null,"content":"### New\r\n\r\n- Added event type filtering to the asset Recent Updates timeline, allowing users to toggle between Materializations and Observations when both event types are present. Filter preference is persisted to local storage.\r\n- `psycopg2-binary` has been removed as a dependency from `dagster-postgres`. If you were previously relying on this transitive dependency, you may need to explicitly add `psycopg2-binary` to your project.\r\n- [ui] The launchpad UI no longer prefills optional resource defaults in the config editor. To see and edit the defaults, click \"Scaffold all default config\".\r\n- [ui] For op jobs in code locations that have reloaded, the launchpad now always shows a message indicating that the config may be stale.\r\n- [ui] Asset health status indicators now distinguish between loading, unknown, and no data states for improved debugging.\r\n- [ui] The asset overview timeline now correctly displays the most recent event without cutting it off.\r\n- [dagster-dbt] `DbtProject` and `DbtProjectComponent` now expose `prepare_project_cli_args` to allow customizing CLI arguments used to generate the manifest.\r\n- [dagster-looker, dagster-omni, dagster-powerbi, dagster-sigma, dagster-tableau] BI integration assets are now automatically enriched with `dagster/table_name` metadata. Additionally, `dagster-tableau` and `dagster-looker` assets now populate `dagster/storage_kind` based on the upstream connection type.\r\n- [dagster-sling] The `sling` package import is now deferred to improve import-time performance.\r\n\r\n### Bugfixes\r\n\r\n- Fixed a bug where Dagster incorrectly called `__enter__` on nested resource attributes annotated with `dagster.ResourceDependency` during parent resource setup. (Thanks, [@danielgafni](https://github.com/danielgafni)!)\r\n- [ui] Fixed text wrapping and layout for long URIs in asset storage metadata section.\r\n\r\n### Documentation\r\n\r\n- Added documentation for custom metrics in Dagster+ Insights.\r\n- Added and enhanced webhook alerting documentation, including a guide for incident.io integration.\r\n\r\n### Dagster Plus\r\n\r\n- Organization-level timezone settings are now supported, allowing organizations to set a default timezone for users who haven't explicitly set a preference.\r\n- [ui] Asset job run data is now included in Job insights.\r\n- [ui] Code locations with loaded but failed agents now display a warning icon with agent status details in a popover.\r\n- [ui] Added run queue time metric visualization to Job insights.\r\n- [ui] Updated Alert policy list style for improved scannability and legibility.","publishedAt":"2026-03-05T21:40:29.000Z","fetchedAt":"2026-04-11T14:07:22.093Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.12.18","media":[],"coverageCount":0},{"id":"rel_jApdzV1kBCDzO9hgperz9","version":"1.12.17","type":"feature","title":"1.12.17 (core) / 0.28.17 (libraries)","summary":"### Bugfixes\n\n- Fix bug with inclusion of built webapp in `dagster-webserver` that caused the Dagster UI to fail to load.","titleGenerated":null,"titleShort":null,"content":"### Bugfixes\n\n- Fix bug with inclusion of built webapp in `dagster-webserver` that caused the Dagster UI to fail to load.","publishedAt":"2026-02-27T19:40:56.000Z","fetchedAt":"2026-04-11T14:07:22.093Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.12.17","media":[],"coverageCount":0},{"id":"rel_4oR1ugx92Cevk4k4Rh8X0","version":"1.12.15","type":"feature","title":"1.12.15 (core) / 0.28.15 (libraries)","summary":"### New\n\n- Pool names can now be any non-whitespace character, instead of requiring alphanumbeic characters, slashes, and underscores.\n- [dagster-aws]...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- Pool names can now be any non-whitespace character, instead of requiring alphanumbeic characters, slashes, and underscores.\n- [dagster-aws] The `EcsRunLauncher` will now retry a task launch when a RunTask API call fails due to a throttling error in an underlying EC2 API call.\n- [dagster-tableau] Tableau workbooks and projects can now be filtered using the `workbook_selector` and `project_selector` in `TableauComponent`.\n\n### Bugfixes\n\n- [ui] Fixed issue where saved launchpad config was not used for single-partition asset materializations.\n- [ui] Fix console error noise during asset lineage navigation.\n- [ui] Fixed an issue where the \"Start X Automations\" and \"Stop X Automations\" menu options on the Automations tab were sometimes incorrectly disabled.\n- [dagster-dbt] The `DbtProject` constructor now correctly accepts strings for the `target_path` parameter.","publishedAt":"2026-02-20T19:10:53.000Z","fetchedAt":"2026-04-11T14:07:22.093Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.12.15","media":[],"coverageCount":0},{"id":"rel_i8myE80XhE83wNlLbWOYl","version":"1.12.14","type":"feature","title":"1.12.14 (core) / 0.28.14 (libraries)","summary":"### New\n\n- `@asset_check` and `AssetCheckSpec` now support a `partitions_def` parameter, allowing checks to execute against specific partitions of the...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- `@asset_check` and `AssetCheckSpec` now support a `partitions_def` parameter, allowing checks to execute against specific partitions of their upstream asset rather than the entire contents. If set, the partition definition must match the definition of the targeted asset.\n- [ui] The \"Select all\" checkbox has been restored to the Automations list.\n\n### Bugfixes\n\n- Fixed performance issue where the partition selector would freeze for 30+ seconds when selecting \"All\" on assets with large (100k+) partition sets. (Thanks, [@ljodea](https://github.com/ljodea)!)\n- Fixed an issue with cron schedules using step patterns (like `*/10` or `*/30`) in the day-of-month field where invalid days weren't properly skipped.\n- [ui] Fixed an issue that could cause incorrect partition statuses to be displayed in the UI.\n- [ui] Partition percentages now round in a more intuitive way.\n- [ui] Row count metadata is now displayed even when set to zero.\n- [dagster-databricks] Fixed an issue where op name generation would occasionally lead to collisions.\n- [dagster-sigma] When building assets for Sigma workbooks that depend on tables unknown to Dagster, an error is logged instead of throwing an exception.\n- [dagster-k8s] Fixed an issue where `PipesK8sClient` would sometimes fail when containers in the `ignored_containers` list failed.\n- [dagster-github] Ensured compatibility with `pyjwt>=2.11.0`,which introduced breaking changes.\n\n### Documentation\n\n- Added an example of censoring PII in run logs.\n- Updated branch deployment docs to include single-agent setup.","publishedAt":"2026-02-05T21:39:54.000Z","fetchedAt":"2026-04-11T14:07:22.093Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.12.14","media":[],"coverageCount":0},{"id":"rel_QuKP-lCXqmPlPxU6iyfLo","version":"1.12.13","type":"feature","title":"1.12.13 (core) / 0.28.13 (libraries)","summary":"### New\n\n- [dagster-polytomic] `PolytomicComponent` has been added and can be used to represent your Polytomic bulk sync schemas as external assets in...","titleGenerated":null,"titleShort":null,"content":"### New\n\n- [dagster-polytomic] `PolytomicComponent` has been added and can be used to represent your Polytomic bulk sync schemas as external assets in Dagster\n- [dagster-fivetran] Added warning log when no Fivetran groups are found to help users troubleshoot permission issues.","publishedAt":"2026-01-30T19:52:06.000Z","fetchedAt":"2026-04-11T14:07:22.093Z","url":"https://github.com/dagster-io/dagster/releases/tag/1.12.13","media":[],"coverageCount":0}],"pagination":{"nextCursor":"2026-01-30T19:52:06.000Z|2026-04-11T14:07:22.093Z|rel_QuKP-lCXqmPlPxU6iyfLo","limit":20},"summaries":{"rolling":{"windowDays":90,"summary":"Dagster shipped major tooling and integration expansions over the past 90 days. Version 1.13.0 introduced AI-assisted development through the new `skills` repository and expanded `dg api` commands, partitioned asset checks that align data quality logic with how data gets produced, and virtual assets (preview) for modeling database views that reflect upstream changes automatically. Meanwhile, state-backed components—used by dbt, Fivetran, Airbyte, Tableau, and Looker integrations—now persist local state by default, reducing code location loading friction. Across the 1.12.x line leading up to 1.13.0, the team added Components API support throughout the platform (dbt Cloud, Azure, Databricks, Polytomic), expanded partition handling in asset checks and asset selection syntax, integrated Databricks and Fivetran observability into the UI, and shifted `dg` from being a Cloud-only CLI to a general-purpose project tool with deployment validation built in.","releaseCount":12,"generatedAt":"2026-04-11T14:07:26.985Z"},"monthly":[{"year":2026,"month":3,"summary":"Dagster focused on expanding asset selection and observability tooling. Partition filtering arrived in asset selection syntax and the UI gained date range pickers for backfills, while execution contexts now expose `multi_partition_key` for multi-partition runs. Component support extended to Azure resources and dbt Cloud projects, and the Fivetran integration added a polling sensor for externally-triggered syncs. A breaking change removed the `psycopg2-binary` transitive dependency from `dagster-postgres`.","releaseCount":4,"generatedAt":"2026-04-11T14:07:29.115Z"}]}}