-
Notifications
You must be signed in to change notification settings - Fork 2
Comparing changes
Open a pull request
base repository: Zipstack/unstract-python-client
base: v1.5.1
head repository: Zipstack/unstract-python-client
compare: v1.5.2
- 6 commits
- 6 files changed
- 4 contributors
Commits on Jun 23, 2026
-
fix(clone): clone agentic project documents + resolve exported agenti…
…c tools Two gaps surfaced cloning agentic ("Agentic Prompt Studio") projects: 1. Documents were dropped. Agentic projects keep their uploads in their own store (agentic/documents/), separate from Prompt Studio prompt-documents. The files phase only iterates the custom_tool remap, so agentic docs were never cloned. AgenticStudioPhase now clones them per project (download raw bytes from source, skip names already on target, upload to the target project), and counts them in the dry-run plan. 2. Exported agentic tools were skipped in workflows. A workflow tool_instance references a registry id; exported agentic projects register under agentic_studio_registry, but ToolInstancePhase resolved tool_id only via prompt_studio_registry. It now falls back to the agentic registry, so the "Agentic tool API" workflow lands with its tool wired. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011ja9H1rnSXmPUgQtHm8TNSConfiguration menu - View commit details
-
Copy full SHA for 9df7e52 - Browse repository at this point
Copy the full SHA 9df7e52View commit details -
feat(clone): clone agentic verified-data; honour skip strategy for docs
Agentic verified-data ("ground truth manually verified by user") is curated input, not regenerable output, so it must be cloned. AgenticStudioPhase now re-points each source verified-data row to the cloned target document by filename and recreates it (skipping docs absent on target and rows already present). Extracted/comparison data stays uncloned — both regenerate on a re-run + re-verify. Also honour file_strategy="skip" in the new document path, matching the files and lookups phases: under skip, agentic documents are listed and counted as skipped (operator re-uploads), not transferred. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011ja9H1rnSXmPUgQtHm8TNSConfiguration menu - View commit details
-
Copy full SHA for 20d27e9 - Browse repository at this point
Copy the full SHA 20d27e9View commit details -
fix(clone): forecast agentic verified-data as skipped under skip stra…
…tegy Verified data FKs a document; with file_strategy=skip no docs land on target, so a dry-run must predict the rows as skipped rather than as creates that the real run silently drops. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011ja9H1rnSXmPUgQtHm8TNS
Configuration menu - View commit details
-
Copy full SHA for 22e9d93 - Browse repository at this point
Copy the full SHA 22e9d93View commit details -
fix(clone): honour skip strategy in _clone_verified_data at runtime
_plan_children already forecasts verified-data as skipped under file_strategy=skip, but the runtime path lacked the matching guard: on a re-run where documents reached the target by other means, it would create verified rows the plan said it would skip. Add the early-return guard, mirroring _clone_documents. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011ja9H1rnSXmPUgQtHm8TNS
Configuration menu - View commit details
-
Copy full SHA for e35b564 - Browse repository at this point
Copy the full SHA e35b564View commit details -
Merge pull request #23 from Zipstack/fix/clone-agentic-docs-and-tool
fix(clone): clone agentic project documents + resolve exported agentic tools
Configuration menu - View commit details
-
Copy full SHA for d769942 - Browse repository at this point
Copy the full SHA d769942View commit details -
Configuration menu - View commit details
-
Copy full SHA for a35efc1 - Browse repository at this point
Copy the full SHA a35efc1View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.5.1...v1.5.2