SDK regeneration

[fern-api]

Automated SDK generation by Fern

---

Action required: 37 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
batch.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
batch/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
batch/raw_client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
client/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
context.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
context/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
context/raw_client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
core/request_option.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph/client/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph/client/raw_client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph/edge/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph/edge/raw_client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph/episode/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph/episode/raw_client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph/node.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph/node/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph/node/raw_client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph/observation/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph/observation/raw_client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph/threadsummary/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
graph/threadsummary/raw_client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
project.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
project/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
project/raw_client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
task.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
task/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
task/raw_client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
thread.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
thread/client/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
thread/client/raw_client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
thread/message/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
thread/message/raw_client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
types.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
user.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
user/client.go	Move the module to /v4 for the v4 SDK line	The new generation changed the same lines you edited
user/raw_client.go	Move the module to /v4 for the v4 SDK line	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-24_20-10-23_950 origin/fern-bot/2026-08-24_20-10-23_950

   Or if you don't have the repo cloned:

   git clone https://github.com/getzep/zep-go.git && cd zep-go && git checkout -b fern-bot/2026-08-24_20-10-23_950 origin/fern-bot/2026-08-24_20-10-23_950

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.

[paul-paliychuk]

Superseded: regenerating from an updated v4 contract. The graph reads are now typed rather than generic JSON objects, so this generation is stale.