feat(api): update API spec from langfuse/langfuse 41f5847#1677
Conversation
|
@claude review |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
LGTM, auto-generated Fern SDK update with purely additive API surface changes.
Extended reasoning...
Overview
This PR is an auto-generated update to the Fern-generated API SDK from upstream langfuse/langfuse spec 41f5847. It touches 104 files — all under langfuse/api/ — and the changes are entirely SDK type stubs and client wrappers (every file starts with # This file was auto-generated by Fern from our API Definition). The substantive additions are: a new unstable namespace exposing evaluators and evaluation_rules clients/types, new blob-storage export options (BlobStorageExportFieldGroup, BlobStorageExportSource, an EVERY20MINUTES frequency enum value), a new DeleteLlmConnectionResponse plus llm_connections.delete endpoint, a new CreateScoreSource enum for legacy v1 score creation, and several new optional fields on ObservationV2 (usage_pricing_tier_name, input_price, output_price, total_price, trace_name, tags, release). Docstring-only updates account for the score_configs name validation note and the scores limit documentation.
Security risks
None apparent. All new code is type definitions, lazy-import scaffolding, and HTTP request wrappers around new server endpoints. New fields are all typing.Optional and default to None, so existing call sites are not affected. There is no auth/crypto/permissions logic being modified.
Level of scrutiny
Low. Fern-generated SDK regenerations follow a deterministic template and have been merged routinely (recent commit 4c5eb44 is the same kind of update). The changes are purely additive at the public API surface — no fields were removed or repurposed — so backward compatibility is preserved. The only behavior risk would be in the regeneration template itself, which is not in scope here.
Other factors
No bugs were flagged by the bug hunting system. The PR scope matches the title (single Fern regeneration commit). No outstanding reviewer comments to address.
2 participants
No description provided.