# Dagster 1.13.11 — 1.13.11 (core) / 0.29.11 (libraries)

- Product: Dagster (https://whatsnew.fyi/product/dagster)
- Vendor: Dagster Labs
- Date: 2026-06-25
- Version: 1.13.11
- Original notes: https://github.com/dagster-io/dagster/releases/tag/1.13.11
- Permalink: https://whatsnew.fyi/product/dagster/releases/1.13.11

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **changed** — The asset catalog page now renders as a single virtualized list so workspaces with many asset groups or code locations no longer freeze the UI when expanding those sections
- **added** — Added a new "insights" option to DbtProjectComponent's include_metadata field, enabling Dagster+ Insights tracking from YAML config
- **added** — Added an optional limit argument and new assetSelectionCount / assetCheckSelectionCount fields to the Run GraphQL type so clients can render a bounded preview of a run's asset/check selection alongside the true totals
- **fixed** — Asset check history is now cleared when an asset or its partitions are wiped; stale entries no longer linger in the Execution History and Partitions views
- **changed** — The run detail page header now displays the asset-check count for asset-job runs, and the count is now read from the execution plan rather than by scanning the full run event log
- **fixed** — The "View asset lineage" item in the run actions menu now correctly scopes to the assets in that run
- **changed** — .with_insights() now logs a warning instead of raising when called against an unsupported adapter

###### New

- [ui] The asset catalog page now renders as a single virtualized list, so workspaces with many asset groups or code locations no longer freeze the UI when expanding those sections.
- [dagster-dbt] Added a new `"insights"` option to `DbtProjectComponent`'s `include_metadata` field, enabling Dagster+ Insights tracking from YAML config.
- [dagster-graphql] Added an optional `limit` argument and new `assetSelectionCount` / `assetCheckSelectionCount` fields to the `Run` GraphQL type, so clients can render a bounded preview of a run's asset/check selection alongside the true totals.

###### Bugfixes

- Asset check history is now cleared when an asset or its partitions are wiped; stale entries no longer linger in the Execution History and Partitions views.
- [ui] The run detail page header now displays the asset-check count for asset-job runs, and the count is now read from the execution plan rather than by scanning the full run event log.
- [ui] The "View asset lineage" item in the run actions menu now correctly scopes to the assets in that run.
- [dagster-dbt] `.with_insights()` now logs a warning instead of raising when called against an unsupported adapter.

###### Documentation

- Added a new page documenting Dagster+ code-location snapshot size limits, with a script you can run locally to estimate snapshot sizes before deploying.
- Documented the "Run concurrency" Insights metric.
- Fixed an invalid `pool` config in the "Preventing concurrent dbt snapshots" `DbtProjectComponent` example.