LoginSign Up
← Back to all sparks
D

Dagster

ANALYTICS
Velocity5.0

Data orchestration platform for building and observing data pipelines.

dagster.io ↗

Dagster drops Python 3.10 and lets agents run schedules and sensors through MCP.

orchestrationmcpdbt-fusiondagster-pluspython-support
◆Current state
Dagster's 1.13 line ships weekly and follows two threads. dagster-dbt no longer installs dbt-core and gained a dbt v2 extra for the Fusion engine, while the UI keeps getting phone layouts and faster search and catalog pages. 1.13.30 on November 12 makes Python 3.11 the minimum and widens the Dagster+ MCP server to reading and toggling schedules and sensors and managing partitions.
◆Where it's heading
The Dagster+ MCP server has grown release by release, from launching runs without a code location in September to controlling schedules, sensors and partitions now. Combined with the dbt split, Dagster is trimming legacy dependencies while making the orchestrator something an agent can operate, not just a person in the UI.
◆Prediction
The MCP server still lacks write access to things like backfills and alert policies, so expanding it there is the most visible next step; further Python and dbt version floors are likely to follow the 3.10 cut.

◆Recent moves

  1. 1d ago

    1.13.30: Python 3.11 minimum, more Dagster+ MCP tools

    Python 3.10 support ends, the asset catalog stops polling health it doesn't show, and the Dagster+ MCP server can now read and start or stop schedules and sensors and manage partitions. It continues the steady widening of what agents can do in Dagster+ alongside the dependency cleanup that began with dbt.

    View source ↗
  2. 8d ago

    1.13.29: more mobile layouts, faster search and catalog

    Extends the phone layout to code locations, sensors and schedules and speeds up run logs, global search and the asset catalog, with fixes for table selection and bulk-action permissions. It continues the mobile UI work that began in 1.13.25.

    View source ↗
  3. 14d ago

    1.13.28: dbt v2 extra and retries for failed code locations

    Adds a dagster-dbt[dbt] extra for dbt v2 and a clear error if dbt 2.x sits beside dbt-core, following the split made in 1.13.26. Opt-in retries for code locations that fail to start add to the window's operational work.

    View source ↗
  4. 18d ago

    1.13.27: mobile run details, bounded BigQuery Insights scans

    Run details get a mobile layout, BigQuery Insights stops scanning up to 180 days of job history, and clicking Re-execute twice no longer creates duplicate runs. Small changes that extend the mobile work and tighten cost and safety.

    View source ↗
  5. 1mo ago

    1.13.26: dagster-dbt stops installing dbt-core

    The breaking change of the window: dagster-dbt stops installing dbt-core, which is now an extra. Mixing it with Fusion's dbt package overwrites files with no pip error, so this removes a silent failure at the cost of an install change.

    View source ↗
  6. 1mo ago

    1.13.25: phone layout for the Dagster UI, ECS run resumes

    The UI gets a real phone layout, and ECS run workers can now be resumed by run monitoring. It is the widest user-facing change here.

    View source ↗