Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add docs on version compatibility within a deployment #23734

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/content/about/releases.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,16 @@ While technically the 0.y.z phase of Semantic Versioning is "anything goes", we

---

## Version compatibility wihin a Dagster deployment

Dagster deployments can have multiple versions of Dagster running simultaneously.

A Dagster deployment consists of a set of [code locations](https://docs.dagster.io/concepts/code-locations), as well as _host processes_: the web server and [daemon](https://docs.dagster.io/deployment/dagster-daemon).
- The code locations within a deployment can each depend on a different Dagster version.
- 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.

---

## Python version support

Each Dagster release strives to support the currently active versions of Python.
Expand Down