Skip to content

SDK regeneration - #127

Closed
fern-api[bot] wants to merge 3 commits into
mainfrom
fern-bot/2026-09-24_16-06-33_976
Closed

fern-api[bot] wants to merge 3 commits into
mainfrom
fern-bot/2026-09-24_16-06-33_976

Conversation

@fern-api

@fern-api fern-api Bot commented Sep 24, 2026

Copy link
Copy Markdown
Contributor

Automated SDK generation by Fern


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

Action required: 16 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
reference.md release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) The new generation changed the same lines you edited
src/smallestai/atoms/__init__.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) The new generation changed the same lines you edited
src/smallestai/atoms/agent_telephony/raw_client.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) The new generation changed the same lines you edited
src/smallestai/atoms/client.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) The new generation changed the same lines you edited
src/smallestai/waves/ops/raw_client.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) The new generation changed the same lines you edited
src/smallestai/waves/analytics/__init__.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) Both the generator and your customization created this file
src/smallestai/waves/analytics/client.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) Both the generator and your customization created this file
src/smallestai/waves/analytics/raw_client.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) Both the generator and your customization created this file
src/smallestai/waves/analytics/types/__init__.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) Both the generator and your customization created this file
src/smallestai/waves/client.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) The new generation changed the same lines you edited
src/smallestai/waves/ops/raw_client.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) Both the generator and your customization created this file
src/smallestai/waves/post_call_analysis/client.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) Both the generator and your customization created this file
src/smallestai/waves/post_call_analysis/raw_client.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) Both the generator and your customization created this file
src/smallestai/waves/voices/client.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) Both the generator and your customization created this file
src/smallestai/waves/voices/raw_client.py release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) The new generation changed the same lines you edited
wiremock/wiremock-mappings.json release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95) 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-09-24_16-06-33_976 origin/fern-bot/2026-09-24_16-06-33_976
    Or if you don't have the repo cloned:
    git clone https://github.com/smallest-inc/smallest-python-sdk.git && cd smallest-python-sdk && git checkout -b fern-bot/2026-09-24_16-06-33_976 origin/fern-bot/2026-09-24_16-06-33_976
  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.

fern-api Bot added 2 commits September 24, 2026 16:06
Generated by Fern
CLI Version: unknown
Generators:
  - fernapi/fern-python-sdk: 5.12.12
Patches applied (6):
  - patch-0c9e9b4e: refactor: rename agent-swarm -> agent-crew across SDK + CLI (4.4.2)
  - patch-566503a1: docs: dedicated MkDocs SDK site (guides, cheatsheet, coding-agent prompt) (#78)
  - patch-8f5588f2: docs(sdk): fix waves TTS method names in reference cheatsheet (#81)
  - patch-a7b7c3b9: feat(errors): actionable messages + PlanNotEntitledError for plan-gated 403s (#87)
  - patch-c273a159: fix: waves endpoints target the waves host (5.10.1) (#97)
  - patch-184bbd0f: feat(cli): stream live call events + build logs (crew observability, phase 1) (#100)

Patches with unresolved conflicts (1):
  - patch-410e0722: release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)
    Run `fern-replay resolve` to apply these customizations.
@crim-app

crim-app Bot commented Sep 24, 2026

Copy link
Copy Markdown

crim doesn't review pull requests automatically here.

Comment crim review on this pull request whenever you want a review.

…ound caller-id) + new atoms clients

Version bump + changelog for the regen off the fixed atoms spec (campaign group-name
restored, PRO-3262). Notes the intended breaking removals/moves.
@abhishekmishragithub

Copy link
Copy Markdown
Collaborator

Closing — stale. This PR-mode regen reproduced the identical 15 errors as #125 despite the atoms spec fix (docs #479) being present in the working tree. Cause: replay: enabled: true in unified/generators.yml served the recorded generation instead of re-reading the edited spec. A --local regen off the same branch DID apply the fix (campaign ops back in atoms/campaigns, agent_telephony clean). Fix needs a fresh (non-replayed) regen — see PRO-3262.

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