Skip to content

LW-474 [CHORE] Sync to llmwhisperer-client 2.10.0 - #21

Open
johnyrahul wants to merge 1 commit into
mainfrom
claude/lw474-bump-client-2-10-0-5edb1d
Open

johnyrahul wants to merge 1 commit into
mainfrom
claude/lw474-bump-client-2-10-0-5edb1d

Conversation

@johnyrahul

Copy link
Copy Markdown

What

Bumps the exact llmwhisperer-client pin to 2.10.0 and re-syncs the vendored LLMWhisperer spec and its provenance to match, per the bump-client-pins skill.

The pin, the spec and provenance.json move in one commit because they are coupled: the CLI derives its flags and help text from the vendored spec, intersected with what the pinned client actually accepts.

The chain

The spec is copied byte-for-byte from specs/llmwhisperer.json at the client's v2.10.0 tag. That tag's tools/gen_sdk.sh records the source as Zipstack/unstract-llm-whisperer @ 9fe7085b44da6ca37e635fba3ab082c725ef8aef — the squash commit of the matching service PR — so that is what provenance.json now records, alongside the new sha256.

Surface change

2.10.0 adds exactly one optional parameter, include_cell_borders, and the spec declares it as a non-internal, non-deprecated query parameter the pinned client accepts. So it derives automatically into whisper extract as a paired flag:

--include-cell-borders / --no-include-cell-borders

tests/derived_flags.json gains that one entry and nothing else — no flag lost, no choice or type narrowed. The snapshot was refreshed deliberately after reading the named difference.

Help text falls through to the client's own docstring, which states that the parameter keys off the uploaded file type (any XLS/XLSX upload, the default form mode included) rather than off mode, so no overlay.toml entry was needed to reword it.

As with the existing --allow-rotated-text, the spec defaults this to true while the client defaults it to None: omitting the flag sends nothing and the server's default applies. The new flag also appears in the --discover full contract.

Verification

  • uv lock + uv sync --extra dev --python 3.12 — lockfile updated (2.9.1 → 2.10.0)
  • uv run pytest -q — 569 passed, 1 skipped
  • uv run ruff check . and uv run ruff format --check . — clean, 38 files already formatted

__version__ is deliberately left alone; release.yml owns the bump at dispatch.

🤖 Generated with Claude Code

Move the exact pin, the vendored spec and its provenance together, as a
client bump has to: the CLI derives its flags from the spec and can only
offer what the pinned client accepts.

The spec is copied byte-for-byte from `specs/llmwhisperer.json` at the
client's v2.10.0 tag, which its `tools/gen_sdk.sh` records as upstream
`Zipstack/unstract-llm-whisperer` 9fe7085b44da6ca37e635fba3ab082c725ef8aef.

The one parameter 2.10.0 adds, `include_cell_borders`, derives into
`whisper extract` as a paired `--include-cell-borders/--no-include-cell-borders`
flag, so `derived_flags.json` gains that entry and nothing else -- no flag
lost, no choice or type narrowed. Its help comes from the client's own
docstring, which states that the parameter keys off the uploaded file type
rather than the mode. Like the existing `--allow-rotated-text`, the spec
defaults it to true while the client defaults it to None, so omitting the
flag sends nothing and the server's default applies.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@greptile-apps

greptile-apps Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

via Greptile

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] The PR appears safe to merge; no actionable defects were found.

Summary

Updates llmwhisperer-client to 2.10.0 and syncs the vendored spec, provenance, and flag snapshot.

  • Whisper extraction lets callers choose whether workbook cell borders appear in text.

No actionable issues found. Tests were not run during this review.

Reviews (1) · Last reviewed commit: "chore: sync to llmwhisperer-client 2.10...." · Reviewed by Greptile

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.

1 participant