Repository navigation
SDK regeneration - #193
Merged
Merged
SDK regeneration#193
Conversation
Generated by Fern CLI Version: unknown Generators: - fernapi/fern-cli-generator: 0.54.1
Patches applied (5): - patch-3acf25c9: feat: Adds new say command (#143) - patch-0d14627a: fix: don't send Authorization alongside an explicit API key (#153) - patch-f48516dc: feat: agents graph maps how agents, tools, tests and documents connect (#180) - patch-c375927e: fix: build Apple Silicon releases on macos-15 (1.9.2) (#189) - patch-898a4752: fix: say skill points free plans to pre-made voices (1.9.3) (#190) Patches with unresolved conflicts (10): - patch-809b383f: fix(deps): patch two advisories; keep the verification script - patch-composite-7dd8e976: Customer customizations (composite) - patch-3866acd2: Make intent optional (#150) - patch-68caee9a: feat: add onboard init, connect, check and test for agent-led setup (#154) - patch-d0001ac9: fix: onboard flags that survive npx, and check that the app loads the key (1.5.1) (#159) - patch-ab3cae7d: fix: onboard check finds the key file by name in a monorepo package (1.5.2) (#160) - patch-c6e92222: fix: bump rustls-webpki to 0.103.16 for RUSTSEC-2026-0382 (#174) - patch-ef424569: fix: the browser's approval reaches onboard on Windows (1.7.1) (#167) - patch-3965a566: feat: draw agent workflows in the terminal and export them as Mermaid (#179) - patch-d6249795: feat: onboard waits longer for approval, retries an unreachable token endpoint, and reports how sign-ins end (1.9.1) (#175) Run `fern-replay resolve` to apply these customizations. Patches absorbed by generator (1): - patch-d697e6cf: feat: onboard ends a voice agent project on a link to talk to the agent (1.10.0) (#184) The generator now produces these customizations natively.
Fern replay merged errno, fastrand and gethostname in twice, and left stale 0.1.0/0.0.0 entries for the workspace crates; cargo refused to parse the lock. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kraenhansen
approved these changes
Nov 12, 2026
kraenhansen
left a comment
Member
There was a problem hiding this comment.
Regenerated for v1.11.0. Fix commit 4760428 drops the duplicate Cargo.lock entries; approved by Kræn after reviewing it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated SDK generation by Fern
✅ Customizations automatically preserved, but 11 files need your attention.
Action required: 11 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:
Cargo.lockCargo.lockCargo.lockCargo.lockCargo.lockCargo.lockCargo.lockCargo.lockCargo.lockCargo.lockCargo.tomlHow to resolve
git fetch origin && git checkout -b fern-bot/2026-11-12_12-53-09_741 origin/fern-bot/2026-11-12_12-53-09_741fern replay resolvefern replay resolveagain to finalizeYour 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.