Skip to content

SDK regeneration#781

Open
fern-api[bot] wants to merge 2 commits into
mainfrom
fern-bot/2026-07-20_13-21-57_380
Open

SDK regeneration#781
fern-api[bot] wants to merge 2 commits into
mainfrom
fern-bot/2026-07-20_13-21-57_380

Conversation

@fern-api

@fern-api fern-api Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Automated SDK generation by Fern


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

Action required: 2 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

How to resolve

  1. Check out this branch:
    git fetch origin && git checkout -b fern-bot/2026-07-20_13-21-57_380 origin/fern-bot/2026-07-20_13-21-57_380
    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-07-20_13-21-57_380 origin/fern-bot/2026-07-20_13-21-57_380
  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
Unresolved Fern replay conflicts on version headers may drop prior manual SDK fixes if merged without resolution; the broader regen also changes HTTP client behavior (keepalive, dependency floors).

Overview
This PR updates Fern generation metadata for SDK 7.0.6 (CLI 5.55.0, Python generator 5.20.0) and adds tcp_keepalive generator settings (60s idle, 30s interval, 5 probes), which drive default HTTP transport keepalive in the regenerated client.

.fern/replay.lock records the new generation commit and two unresolved replay patches: prior customizations that only bumped pyproject.toml and client_wrapper.py version / User-Agent strings (from #778 and #779) overlap the same lines the new generation rewrote, so those customizations were not auto-reapplied. Merge or resolve via fern replay resolve before shipping so embed / max_retries fixes are not lost on the next run.

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

fern-api Bot added 2 commits July 20, 2026 13:22
Generated by Fern
CLI Version: unknown
Generators:
  - fernapi/fern-python-sdk: 5.20.0
Patches with unresolved conflicts (2):
  - 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)
    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