Files
distributed-execution/pyproject.toml
ILay 35ef45de56 [SIMPL-30451] Pin dagster to 1.12.8, the control plane version
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
2026-08-31 20:26:29 +02:00

46 lines
1.2 KiB
TOML

[project]
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==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",
]
[dependency-groups]
dev = [
"pytest>=8.4.2",
"pytest-cov>=7.0.0",
]
[build-system]
requires = ["setuptools", "wheel"]
build-backend = "setuptools.build_meta"
[tool.setuptools]
package-dir = {"" = "src"}
[tool.setuptools.packages.find]
where = ["src"]
[tool.setuptools.package-data]
distributed_execution = ["*.py"]
[tool.black]
line-length = 120
target-version = ['py312']
[tool.pytest.ini_options]
pythonpath = ["src"]
testpaths = ["tests"]