Skip to content

chore: fix data designer version#135

Merged
lipikaramaswamy merged 1 commit into
mainfrom
lipikaramaswamy/chore/fix-dd-version
Apr 27, 2026
Merged

chore: fix data designer version#135
lipikaramaswamy merged 1 commit into
mainfrom
lipikaramaswamy/chore/fix-dd-version

Conversation

@lipikaramaswamy
Copy link
Copy Markdown
Collaborator

Summary

Small PR to fix data-designer==0.5.7 instead 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 to gpt-oss-120b which overloads the model on build.

@lipikaramaswamy lipikaramaswamy requested a review from a team as a code owner April 24, 2026 20:06
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 24, 2026

Greptile Summary

This PR tightens the data-designer version constraint from >=0.5.7 to ==0.5.7 in pyproject.toml and regenerates uv.lock accordingly, guarding against untested async-default changes in upcoming data-designer releases that overload the default model set. The lock file's revision field decreased from 3 to 2, suggesting a full regeneration; verify no prior manual or in-flight lock edits were lost.

Confidence Score: 4/5

Safe 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

Filename Overview
pyproject.toml Pins data-designer from >=0.5.7 to ==0.5.7 to prevent unexpected upgrades with breaking async defaults
uv.lock Lock file updated to reflect pinned data-designer==0.5.7; revision number decremented from 3 to 2, suggesting a full regeneration rather than an in-place update

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]
Loading

Reviews (1): Last reviewed commit: "fix: lock in data designer version" | Re-trigger Greptile

Comment thread uv.lock
@lipikaramaswamy lipikaramaswamy merged commit be8639e into main Apr 27, 2026
8 checks passed
@lipikaramaswamy lipikaramaswamy deleted the lipikaramaswamy/chore/fix-dd-version branch April 27, 2026 18:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants