chore: fix data designer version#135
Conversation
Greptile SummaryThis PR tightens the Confidence Score: 4/5Safe to merge; the pin is intentional and well-motivated, with only a minor concern about lock file regeneration. The change is minimal and purposeful — pinning a dependency version. The only P2 concern is the lock file revision going backwards, which could indicate lost intermediate changes. No P0/P1 issues present. uv.lock — confirm no dependency changes were dropped during full lock file regeneration (revision 3 → 2). Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[pyproject.toml\ndata-designer>=0.5.7] -->|PR #135| B[pyproject.toml\ndata-designer==0.5.7]
B --> C{uv lock}
C --> D[uv.lock pinned\ndata-designer==0.5.7\nrevision=2]
D --> E[Builds use exactly\nv0.5.7 — no async\ndefault surprises]
Reviews (1): Last reviewed commit: "fix: lock in data designer version" | Re-trigger Greptile |
Summary
Small PR to fix
data-designer==0.5.7instead of>=so we do not suffer from untested consequences of upcoming async defaults in data designer (overwhelming our default model set and leading to failures). Before we upgrade, we need to perform the task of default model selection to spread the load across models, not just pin all rewrite steps togpt-oss-120bwhich overloads the model on build.