[MISC] Withdraw use_file_history from structure_file, sync spec to unstract#2290 - #31
Merged
Merged
Conversation
`ExecuteRequest` loses `use_file_history`, withdrawn from the published spec as an internal-only option (Zipstack/unstract#2290). The listing's `APIDeploymentSummary` gains `owner_emails`, added upstream since the last sync. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014f9oEEYspPH4fmPULTnLkJ
The generated request no longer carries the field, so the facade could only have raised on it at the call; refusing it at the signature says so up front. The listing fixture gains the owner_emails the spec now requires. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014f9oEEYspPH4fmPULTnLkJ
Contributor
|
…antee Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014f9oEEYspPH4fmPULTnLkJ
praveen-formido
approved these changes
Sep 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
use_file_historyis an internal-only option on the execute request. Zipstack/unstract#2290 withdraws it from the published spec, so this client stops declaring and forwarding it. The kwarg was undocumented, added 2026-08-12 in c291e36, with no known callers.What changed
specs/docstudio-oss.jsonsynced to Zipstack/unstract3851a5866(the head of #2290);SPEC_SOURCEintools/gen_sdk.shrecords that commit and the file's sha256._sdk_docstudioregenerated:ExecuteRequestlosesuse_file_history;APIDeploymentSummarygainsowner_emails, added upstream in UN-3853 [FIX] Attribute platform-key-created resources to the API key's creator unstract#2274 since the last sync (additive, generated model only -- the facade returns listing rows as dicts).structure_file()drops theuse_file_historykeyword, its docstring line and its entry in the request dict.structure_file(use_file_history=...)raisesTypeError; no execute part, send-only name or generated request field isuse_file_history; the listing fixture carriesowner_emails.tests/baseline/is untouched: it vendors the released 1.5.3 wheel, which predates the kwarg, so the parity baseline and its hash do not move.Version
Removing a keyword argument is breaking by semver, which would mean
major(2.0.0). The argument was undocumented, five weeks old and unused as far as we know, sominor(1.8.0) is defensible. Proposed: minor. Chandru decides at release dispatch; nothing here records a version.Before this leaves draft
The
SPEC_SOURCEcommit line will be updated to the squash-merge sha of Zipstack/unstract#2290 once it merges.Tests
uv run pytest tests/: 460 passed.ruff check src/: clean.🤖 Generated with Claude Code
https://claude.ai/code/session_014f9oEEYspPH4fmPULTnLkJ