Skip to content

SDK regeneration#794

Merged
kraenhansen merged 2 commits into
mainfrom
fern-bot/2026-05-26_13-58-21_090
May 26, 2026
Merged

SDK regeneration#794
kraenhansen merged 2 commits into
mainfrom
fern-bot/2026-05-26_13-58-21_090

Conversation

@fern-api

@fern-api fern-api Bot commented May 26, 2026

Copy link
Copy Markdown
Contributor

Automated SDK generation by Fern


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 [Speech Engine] Add full response to Speech Engine API calls (#793) The new generation changed the same lines you edited
src/elevenlabs/core/client_wrapper.py [Speech Engine] Add full response to Speech Engine API calls (#793) 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-05-26_13-58-21_090 origin/fern-bot/2026-05-26_13-58-21_090
    Or if you don't have the repo cloned:
    git clone https://github.com/elevenlabs/elevenlabs-python.git && cd elevenlabs-python && git checkout -b fern-bot/2026-05-26_13-58-21_090 origin/fern-bot/2026-05-26_13-58-21_090
  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
Large generated diff with API signature changes (Productions create, union renames) and telephony credential fields; two files still conflict with prior Speech Engine (#793) customizations until replay resolve.

Overview
Fern SDK regeneration bumps the package to 2.50.0 (User-Agent / Fern metadata / poetry.lock certifi) and refreshes most generated clients and types from the OpenAPI definition.

Conversational AI gains Exotel telephony: client.conversational_ai.exotel.outbound_call, Exotel phone-number create/list/get/update variants, and related history/transfer types. Phone import docs now include Exotel alongside Twilio and SIP. Agent enable_versioning flags are documented as deprecated/ignored. run_tests accepts optional repeat_count for grouped/summarized reruns. ConvAI tests can set conversation_initiation_source.

Productions breaking-ish API tweaks: orders.create takes an optional CreateOrderRequest body (e.g. sandbox); order item unions rename to OrderItemRequestInput_*; languages list returns LanguagesResponse instead of long RootModel* names.

Broader generated additions include code tools on agents, Verbosity, music MusicGenerationMode, and cleanup of verbose RootModelAnnotatedUnion* exports. Merge conflicts remain in pyproject.toml and client_wrapper.py vs prior Speech Engine customizations (#793)—resolve with fern replay resolve before merge.

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

fern-api Bot added 2 commits May 26, 2026 13:58
Generated by Fern
CLI Version: unknown
Generators:
  - fernapi/fern-python-sdk: 4.42.0
Patches with unresolved conflicts (1):
  - patch-2143cac9: [Speech Engine] Add full response to Speech Engine API calls (#793)
    Run `fern-replay resolve` to apply these customizations.

@kraenhansen kraenhansen left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - Fern regeneration for v2.50.0

@kraenhansen kraenhansen merged commit f3ba614 into main May 26, 2026
5 checks passed
@kraenhansen kraenhansen deleted the fern-bot/2026-05-26_13-58-21_090 branch May 26, 2026 14:08
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