Skip to content

SDK regeneration - #337

Closed
fern-api[bot] wants to merge 3 commits into
v4from
fern-bot/2026-08-24_23-09-44_187
Closed

SDK regeneration#337
fern-api[bot] wants to merge 3 commits into
v4from
fern-bot/2026-08-24_23-09-44_187

Conversation

@fern-api

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

Copy link
Copy Markdown
Contributor

Automated SDK generation by Fern


Action required: 1 file 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
src/zep_cloud/client.py Port the hand-written wrappers to the v4 surface 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_23-09-44_187 origin/fern-bot/2026-08-24_23-09-44_187
    Or if you don't have the repo cloned:
    git clone https://github.com/getzep/zep-python.git && cd zep-python && git checkout -b fern-bot/2026-08-24_23-09-44_187 origin/fern-bot/2026-08-24_23-09-44_187
  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 and others added 3 commits August 24, 2026 23:09
Generated by Fern
CLI Version: unknown
Generators:
  - fernapi/fern-python-sdk: 4.64.1
Patches with unresolved conflicts (1):
  - patch-0a8e75ca: Port the hand-written wrappers to the v4 surface
    Run `fern-replay resolve` to apply these customizations.
@socket-security

Copy link
Copy Markdown

@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
License policy violation: pypi certifi under MPL-2.0

Location: Package overview

From: poetry.lockpypi/httpx@0.28.1pypi/certifi@2026.7.22

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/certifi@2026.7.22. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
License policy violation: pypi certifi under MPL-2.0

Location: Package overview

From: poetry.lockpypi/httpx@0.28.1pypi/certifi@2026.7.22

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/certifi@2026.7.22. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@paul-paliychuk

Copy link
Copy Markdown
Contributor

Superseded: regenerating with Fern Replay reset and the v4 toolchain in CI.

@paul-paliychuk
paul-paliychuk deleted the fern-bot/2026-08-24_23-09-44_187 branch August 24, 2026 23:28
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