Add docs on version compatibility within a deployment #23734
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary & Motivation
"The host processes within a deployment are expected to all have the same Dagster version, and that Dagster version is expected to be greater than or equal to the greatest Dagster version used by any code location within the deployment. In Dagster+ deployments, Dagster+ automatically keeps host processes up-to-date, so no user action is require to achieve this. In OSS deployments, users are expected to upgrade their host processes before upgrading the version of Dagster used in their code locations."
How I Tested These Changes