feat(api): update API spec from langfuse/langfuse 845137b#1700
feat(api): update API spec from langfuse/langfuse 845137b#1700langfuse-bot wants to merge 1 commit into
Conversation
|
@claude review |
There was a problem hiding this comment.
LGTM — auto-generated docstring-only updates from API spec.
Extended reasoning...
Overview
This PR is an auto-generated Fern API spec sync touching only docstrings in 4 files under langfuse/api/scores/ and langfuse/api/scores_v3/. The v2 get_many/get_by_id methods get deprecation notices pointing to v3, and the v3 get_many_v3 docstrings get expanded explanations of the fields parameter and core response shape. No code logic, signatures, URLs, params, or types change.
Security risks
None. The diff is text-only inside Python docstrings — no auth, crypto, request construction, or data handling logic is touched.
Level of scrutiny
Very low. These files are explicitly marked "This file was auto-generated by Fern from our API Definition" and the change is a routine spec sync (the PR title matches the repo's prior pattern, e.g. f1d55fe, da69e63). Docstring-only changes in generated client code carry no runtime risk.
Other factors
No bugs were found by the bug hunting system. The deprecation notices and clarified fields semantics also match what end users would want to see surfaced in IDE tooltips. Safe to approve without human review.
Greptile Summary
This is an auto-generated API spec sync from the upstream
langfuse/langfuserepository (commit845137b). All changes are limited to Python docstrings — no runtime logic, signatures, or imports are modified.ScoresClientandRawScoresClient(getandget_by_id) pointing users toGET /api/public/v3/scoresand noting those endpoints are removed in Langfuse v4+.fieldsparameter descriptions per group (details,subject,annotation), and remove the note requiring Langfuse v4+ (implying the v3 endpoint is now version-agnostic).Confidence Score: 5/5
All changes are docstring-only; no runtime code, signatures, or behavior is altered.
Every diff line is inside a triple-quoted docstring. The deprecation notices and expanded field descriptions faithfully reflect the upstream API spec change, and no imports, logic, or type signatures were touched.
No files require special attention.
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[Client calls scores API] --> B{Langfuse version?} B -->|v3 and earlier| C[GET /api/public/scores\nScoresClient / RawScoresClient] B -->|v4+| D[GET /api/public/v3/scores\nScoresV3Client / RawScoresV3Client] C -->|Deprecated in v4+| E[⚠️ Deprecated\nNo longer available on v4+] D --> F{fields parameter} F -->|not set| G[Returns core fields only\nid, projectId, name, value,\ndataType, source, timestamp,\nenvironment, createdAt, updatedAt] F -->|details| H[+ comment, configId, metadata] F -->|subject| I[+ subject kind/id/traceId] F -->|annotation| J[+ authorUserId, queueId] F -->|unknown name| K[HTTP 400]Reviews (1): Last reviewed commit: "feat(api): update API spec from langfuse..." | Re-trigger Greptile