Skip to content
TrustMyStack, home

dagster

1.13.30
dagster-io/dagster

An orchestration platform for the development, production, and observation of data assets.

Version of dagster-io/dagster you run

CompareView on GitHub
Maintenance
Active494 commits in 3 months · bus factor 8
License
Apache-2.0Permissive · OSI-approved
Security
1 advisory1 high · Scorecard 4.8/10
Supported versions
No scheduleendoflife.date does not track this project

16.4k stars · 2.4k forks · 2.6k open issues · last release 2 days ago · data checked 5 hours ago

OverviewTourReleasesDocker imagesSecurityLogos

Breaking changes

What to check before upgrading, taken from the notes of the last 30 releases.

  • 1.13.26Oct 9, 2026

    Breaking Changes

    • [dagster-dbt] dagster-dbt no longer installs dbt-core. It is now available as the dagster-dbt[dbt-core] extra. Do not install dbt-core into an environment that also has dbt Fusion's dbt PyPI package: both claim the dbt import namespace and overwrite each other's files, and pip reports no error.

Release history

All releases on GitHub
Atom feed/feed/dagster-io/dagster
BadgeLatest version of dagster-io/dagster[![version](/badge/dagster-io/dagster)](/p/dagster-io/dagster)

1.13.30 (core) / 0.29.30 (libraries)

New

  • Dropped support for Python 3.10. Dagster now requires Python 3.11 or later.
  • [ui] The asset catalog and asset graph no longer poll asset health data for assets whose health isn't shown, which reduces load when browsing large workspaces.
  • [dagster-cloud-cli] Added a dagster-cloud deployment copy-materializations command, which copies the latest asset materializations from one deployment to another and keeps their original timestamps.

Bugfixes

  • [dagster-cloud-cli] Fixed Serverless fast deploys failing with No module named ... when the project's code is not installed as a package.

Dagster Plus

  • Users with the "Edit concurrency limits" permission can now edit concurrency limits from the Concurrency settings page.
  • The Dagster+ MCP server now has tools to read schedules, sensors, and their ticks, to start and stop schedules and sensors, and to work with asset partitions, including adding and deleting dynamic partitions.
  • Serverless code locations that take more than 3 minutes to load no longer fail to deploy.
  • Serverless base images are no longer built for Python 3.10. Existing Python 3.10 PEX code locations keep running on the last Python 3.10 base image.
  • Fixed the "Send Sample Alert" button on the alert policy details page not sending Slack alerts.
  • Alert emails and Microsoft Teams alerts now escape customer-provided values such as job names and asset keys, so those values can no longer inject HTML.

Full release notesCompare with previous