Skip to content

SDK regeneration - #805

Open
fern-api[bot] wants to merge 2 commits into
mainfrom
fern-bot/2026-08-31_21-19-03_250
Open

SDK regeneration#805
fern-api[bot] wants to merge 2 commits into
mainfrom
fern-bot/2026-08-31_21-19-03_250

Conversation

@fern-api

@fern-api fern-api Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Automated SDK generation by Fern


✅ Customizations automatically preserved, but 4 files need your attention.

Action required: 4 files with unresolved customization conflicts

The new generation changed code you previously customized. Non-conflicting customizations have been applied automatically. The following files need manual resolution:

File Your customization Why it conflicted
pyproject.toml fix(utils): embed(texts=[]) crashes with IndexError on empty input (#778) The new generation changed the same lines you edited
src/cohere/core/client_wrapper.py fix(utils): embed(texts=[]) crashes with IndexError on empty input (#778) The new generation changed the same lines you edited
pyproject.toml Omit Authorization header when api_key is empty (#795) The new generation changed the same lines you edited
src/cohere/core/client_wrapper.py Omit Authorization header when api_key is empty (#795) The new generation changed the same lines you edited

How to resolve

  1. Check out this branch:
    git fetch origin && git checkout -b fern-bot/2026-08-31_21-19-03_250 origin/fern-bot/2026-08-31_21-19-03_250
    Or if you don't have the repo cloned:
    git clone https://github.com/cohere-ai/cohere-python.git && cd cohere-python && git checkout -b fern-bot/2026-08-31_21-19-03_250 origin/fern-bot/2026-08-31_21-19-03_250
  2. Run: fern replay resolve
  3. Open the conflicting files in your editor — you'll see standard merge conflict markers
  4. Resolve using your editor's merge tools (VS Code, IntelliJ, etc.)
  5. Run: fern replay resolve again to finalize
  6. Push your changes

Your resolved customizations will be remembered on future SDK generations.
If you merge this PR without resolving, your unresolved customizations will conflict again on the next generation.


Note

Medium Risk
Touches core HTTP request construction, Pydantic parsing, and streaming; unresolved Replay conflicts may drop the empty-api-key Authorization behavior until manually merged.

Overview
Bumps the package to 7.1.1 via automated Fern regeneration (Python SDK generator 5.22.1 → 5.29.3), with lockfile updates for pydantic, huggingface-hub, and related pins.

HTTP layer: Requests for endpoints with optional bodies now omit an empty JSON body and strip Content-Type when nothing is sent, including handling of the omit sentinel so “no body” is not sent as {}. quote_path_param percent-encodes path segments so values like / or .. cannot alter routing.

Models & streaming: Pydantic input alias coercion is centralized and cached; HttpResponse exposes the underlying httpx.Response. V2 chat streaming skips SSE events with empty data. Doc examples for async chat_stream / generate_stream no longer await the stream call (iterate the returned async iterator directly).

Before merge: Fern Replay reports unresolved conflicts in pyproject.toml and client_wrapper.py against prior customizations (empty Authorization when API key is empty, version-only patches). Run fern replay resolve so those behaviors are not lost—the generated get_headers still always sets Authorization in this diff.

Reviewed by Cursor Bugbot for commit 2de27c3. Bugbot is set up for automated code reviews on this repo. Configure here.

fern-api Bot added 2 commits August 31, 2026 21:19
Generated by Fern
CLI Version: unknown
Generators:
  - fernapi/fern-python-sdk: 5.29.3
Patches with unresolved conflicts (3):
  - patch-c81e8a75: fix(utils): embed(texts=[]) crashes with IndexError on empty input (#778)
  - patch-41f344bd: feat(client): forward max_retries through Client/ClientV2 constructors (#779)
  - patch-bc495daa: Omit Authorization header when api_key is empty (#795)
    Run `fern-replay resolve` to apply these customizations.
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.

0 participants