Repository navigation
feat(api): update API spec from langfuse/langfuse 180e54f - #2008
langfuse-bot wants to merge 1 commit into
Conversation
|
@claude review |
There was a problem hiding this comment.
Claude Code Review
No review was started: this request came from a bot account. Manual reviews can only be requested by someone with write access to this repository. Ask a maintainer to comment @claude review, or have your automation post the comment from a user account with write access.
Tip: disable this comment in your organization's Code Review settings.
There was a problem hiding this comment.
LGTM. This is a regenerated Fern client that only adds endpoints and fields, and it follows the patterns already in the codebase.
What was reviewed:
- The new
list_organization,upsert_organizationanddelete_organizationmethods, sync and async. Their paths areapi/public/organizations/llm-connections[/{id}], they use GET/PUT/DELETE, the body uses camelCase aliases withomit=OMIT, and they handle 400/401/403/404/405 the same way the existing methods do. - The large async raw_client hunks are just diff alignment. In the final file, the existing async
list,upsertanddeletestill have their original paths and bodies. - Skills
getforwardsinclude_contentas theincludeContentquery param in all four variants. The newSkillFile.contentfield is optional and defaults to None.
Extended reasoning...
The change touches five Fern-generated files under langfuse/api. It adds three org-level LLM connection methods to the sync and async clients, an optional includeContent query param on skills get, and an optional content field on SkillFile. Nothing existing is removed or changed in behavior: the only deleted lines come from the diff realigning the async raw client, and the final file is consistent. On the security side, the client sends a secretKey in the request body, the same way the existing project-level upsert does, and authorization is enforced by the server. CODEOWNERS covers only .github/, the bug hunt ended with exit reason dry_streak and no findings, and there are no prior reviews or objections.
Generated from langfuse/langfuse
mainat 180e54f.

Confidence Score: 5/5
The PR appears safe to merge; no actionable issues were found.Summary
Adds organization-level LLM connection methods and optional inline skill contents.
Reviews (1) · Last reviewed commit: "feat(api): update API spec from langfuse..." · Reviewed by Greptile