j.r/distributed-execution
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[SIMPL-30451] Pin dagster to 1.12.8, the control plane version

Browse Source 
The dependency was previously an unbounded 'dagster', so the build took whatever was current and landed on 1.13.19 against a 1.12.8 control plane. A code location is a gRPC server the webserver and daemon call into, and under k8s_job_executor the step pods share a metadata database schema with them, so the version has to match.

Pinned exactly rather than to the 1.12 line: patch releases can carry schema migrations, and 'close enough' is not a safe position against a shared database. Revisit when the platform upgrades.

17 tests pass and definitions validate on the downgraded stack.

Changelog: fixed
This commit is contained in:
ILay
2026-08-31 20:26:29 +02:00
parent 554c92ec92
commit 35ef45de56
3 changed files with 55 additions and 260 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
pyproject.toml
View File

@@ -3,11 +3,16 @@ name = "distributed_execution"
version = "0.1.0"
description = "Reference implementations and user guide for Dagster distributed execution targets and integration patterns"
requires-python = ">=3.12"
# Pinned to the exact control plane version, not just the 1.12 line. A code
# location is a gRPC server the webserver and daemon call into, and step pods
# share a metadata database schema with them. Patch releases can carry schema
# migrations, so "close enough" is not a safe position against a shared database.
# Revisit when the platform upgrades; the libraries track dagster as 0.28.x.
dependencies = [
"dagster",
"dagster-k8s>=0.27.16",
"dagster-postgres>=0.27.16",
"dagster-webserver>=1.11.16",
"dagster==1.12.8",
"dagster-k8s==0.28.8",
"dagster-postgres==0.28.8",
"dagster-webserver==1.12.8",
"pip>=26.1.2",
"pydantic>=2.0",
]