Dagster 1.13.13 - Code Server Import Fix

Dagster 1.13.13 was published on 2026 07 09 as a core release, paired with library version 0.29.13. The main operator visible change is a fix for fresh dagster installs that could resolve an incompatible grpcio-health-checking version and break code server imports through a protobuf conflict. This is not a prerelease.

The full release notes and downloads are on the GitHub release page.

The most important fix in Dagster 1.13.13 is in dependency resolution for new environments. The release notes call out a case where a fresh dagster installation could pull an incompatible version of grpcio-health-checking. That package then collided with the resolved protobuf version and broke code server imports.

For platform teams, this is the kind of failure that shows up before orchestration logic gets a chance to run. The deployment can have valid asset code, valid schedules, and valid run config, then still fail because the Python environment cannot import the code server path. In Dagster, that boundary matters because user code is loaded out of process. A dependency conflict there can look like an application level failure even when the root cause is packaging.

This patch release narrows that risk for clean installs. It is most relevant for base image rebuilds, new worker images, fresh virtual environments, and CI jobs that create an environment from scratch rather than reusing a warm cache. Existing pinned environments may not see a change unless they were already hitting the grpcio-health-checking and protobuf mismatch.

Dagster 1.13.13 also fixes an error when viewing tick details for declarative automation runs. The release notes do not describe a scheduler behavior change. The fix is about viewing the details after the tick exists.

That distinction is useful for operators. Declarative automation is often inspected when an asset did not materialize at the expected time, or when a policy fired in a way that needs explanation. If the tick detail page errors, the run history is still present, but the normal debugging path is interrupted. Engineers then fall back to logs, database queries, or event views to reconstruct what happened.

With this fix, the UI path for tick inspection should be less brittle for declarative automation runs. The practical value is in incident review and day two operations. It helps answer whether an automation condition evaluated, which run it produced, and where the next check should happen. The release notes only name the UI error, so this should not be read as a change to automation evaluation semantics.

The one new UI behavior in this release is small but useful: the asset launch dialog now automatically expands the warnings section when alerts are present. This affects the moment before an operator launches assets, not the execution engine itself.

Warnings are easy to miss when they sit behind a collapsed section. In an asset heavy Dagster deployment, the launch dialog is often used under time pressure during backfills, retries, or manual repair work. Expanding the warning section when alerts exist puts the signal in the path of the person taking the action.

This does not remove the need for review. It also does not turn warnings into policy enforcement. It simply changes the default visibility of warnings in the launch flow. That is still a reasonable operator facing change because manual launches are part of many data platform recovery procedures.

The release notes do not list breaking changes or migration steps for Dagster 1.13.13. Treat it as a patch update focused on install reliability and UI inspection paths.

Teams with reproducible build pipelines should still rebuild from a clean dependency cache at least once. That is the fastest way to confirm the grpcio-health-checking and protobuf resolution path that this release fixes. If the environment uses strict lock files, update the lock in the same change as the Dagster version bump so the code server import behavior is tested against the actual production artifact.

For teams already on 1.13.12, the earlier recent Dagster release covered broader Kubernetes and dbt event work. This 1.13.13 release is narrower. Its main value is reducing friction around fresh installs and keeping the UI useful for automation and launch review.