Canonical AI event

Dagster+ tools no longer require code location and repository name.

New Dagster release speeds up run dequeuing with concurrency pools. MCP server tools no longer need code location and repository name.

11 Sept 20261 verified claims1 sources1 observations

What happened

The official source reports this update: 1.13.22 (core) / 0.29.22 (libraries). New Run dequeuing is now significantly faster when concurrency pools are in use and many runs are queued, as pool state is read once per dequeue pass rather than repeatedly. In Dagster+, the MCP server's launch_job_run and launch_asset_run tools no longer require a code location and repository name. They are looked up from the job being launched. [ui] The tick timeline now supports filtering to a time window, paging through history, and a live-updating view. [dagster-dbt] Added support for dbt-core 1.12. (Thanks, @jrbasso !) [dagster-looker] Now requires python-liquid>=2.2.1 (previously ).

Why it matters

This official update documents a development concerning 1.13.22 (core) / 0.29.22 (libraries). Its practical significance depends on the scope and evidence stated by the source.

What to watch next

Read the official source update and verify its stated scope, evidence and timing before acting on it.

Connected knowledge