feat(api): update API spec from langfuse/langfuse 6603be6

[langfuse-bot]

Disclaimer: Experimental PR review

Greptile Summary

This PR is an auto-generated API spec update (from langfuse/langfuse commit 6603be6) that adds TEXT as a new score data type throughout the Python SDK. It introduces TextScore, TextScoreV1, Score_Text, ScoreV1_Text, GetScoresResponseData_Text, and GetScoresResponseDataText models, and updates both ScoreDataType and ScoreConfigDataType enums with the TEXT value.

• All new types (TextScore, TextScoreV1) follow the established inheritance pattern from BaseScore/BaseScoreV1.
• The discriminated union GetScoresResponseData is correctly extended with GetScoresResponseData_Text using dataType="TEXT" as the discriminator key.
• ScoreDataType.TEXT includes a visit() branch; ScoreConfigDataType.TEXT also adds TEXT (note: CORRECTION remains intentionally absent from config data type, consistent with the pre-existing design).
• All __init__.py index files and __all__ lists are updated consistently across langfuse/api/, langfuse/api/commons/, and langfuse/api/scores/.
• Docstrings in ScoreBody, CreateScoreRequest, and the legacy score_v1 clients are updated to mention text score requirements (string value, 1–500 characters).
• No manually editable code was modified — all changes are in langfuse/api/, which is the auto-generated Fern client zone per CLAUDE.md.

Confidence Score: 5/5

This PR is safe to merge — it is auto-generated from an updated API spec and introduces no manually written logic.

All changes are in the auto-generated Fern client directory. The new TEXT score type follows established patterns exactly (enum values, discriminated unions, model inheritance, init.py exports). No logic regressions, no broken contracts, no missing migrations.

No files require special attention.

Important Files Changed

Filename	Overview
langfuse/api/commons/types/text_score.py	New TextScore model inheriting BaseScore, adds required string_value field (1–500 chars).
langfuse/api/commons/types/text_score_v1.py	New TextScoreV1 model inheriting BaseScoreV1, parallel legacy-API counterpart to TextScore.
langfuse/api/commons/types/score.py	Adds Score_Text discriminated-union member; correctly included in Score type alias.
langfuse/api/commons/types/score_v1.py	Adds ScoreV1_Text variant; correctly included in ScoreV1 union type alias.
langfuse/api/commons/types/score_data_type.py	Adds TEXT enum value and visit() branch to ScoreDataType.
langfuse/api/commons/types/score_config_data_type.py	Adds TEXT enum value and visit() branch to ScoreConfigDataType; CORRECTION intentionally absent.
langfuse/api/scores/types/get_scores_response_data.py	Adds GetScoresResponseData_Text inline class and extends GetScoresResponseData discriminated union.
langfuse/api/scores/types/get_scores_response_data_text.py	New GetScoresResponseDataText class inheriting TextScore with optional trace field.
langfuse/api/ingestion/types/score_body.py	Docstring update only — mentions text scores and 1–500 character constraint.
langfuse/api/legacy/score_v1/types/create_score_request.py	Docstring update only — mentions text score value requirements.

Class Diagram

%%{init: {'theme': 'neutral'}}%%
classDiagram
    class BaseScore {
        +id: str
        +name: str
        +source: ScoreSource
        +timestamp: datetime
        +created_at: datetime
        +updated_at: datetime
        +metadata: Any
        +environment: str
    }
    class TextScore {
        +string_value: str
    }
    class GetScoresResponseDataText {
        +trace: Optional[GetScoresResponseTraceData]
    }
    class Score_Text {
        +data_type: Literal["TEXT"]
        +string_value: str
    }
    class ScoreV1_Text {
        +data_type: Literal["TEXT"]
        +string_value: str
        +trace_id: str
    }
    class GetScoresResponseData_Text {
        +data_type: Literal["TEXT"]
        +string_value: str
        +trace: Optional[GetScoresResponseTraceData]
    }
    BaseScore <|-- TextScore
    TextScore <|-- GetScoresResponseDataText
    note for Score_Text "Used in discriminated union Score"
    note for ScoreV1_Text "Used in discriminated union ScoreV1"
    note for GetScoresResponseData_Text "Used in GetScoresResponseData union"

Loading

_{Reviews (1): Last reviewed commit: "feat(api): update API spec from langfuse..." | Re-trigger Greptile}

[github-actions]

@claude review

[claude]

The issues from the previous review have been addressed: ScoreDataType now includes TEXT, the string-value overloads accept both CATEGORICAL and TEXT, and the experiment layer correctly uses a separate ExperimentScoreType that excludes TEXT. LGTM.

Extended reasoning...

Overview

This PR adds TEXT as a new score data type throughout the Python SDK. Changes span the auto-generated Fern client (langfuse/api/), the high-level SDK types (langfuse/types.py), the client overloads (langfuse/_client/client.py, langfuse/_client/span.py), the experiment layer (langfuse/experiment.py), and a new integration test.

Security risks

No security-sensitive code is touched. The changes are purely additive type-system and data-model updates. No auth, crypto, or permission logic is affected.

Level of scrutiny

The auto-generated Fern client changes in langfuse/api/ are mechanical and follow established patterns exactly. The hand-maintained changes in langfuse/types.py, langfuse/_client/, and langfuse/experiment.py correctly thread TEXT through the type system, and the introduction of ExperimentScoreType cleanly excludes TEXT from the experiment/eval layer (consistent with the documented design intent). The new test in test_core_sdk.py exercises the full round-trip for TEXT scores.

Other factors

My prior review identified two gaps (missing TEXT in ScoreDataType and CATEGORICAL-only overloads) — both are resolved in this revision, and the inline comment was marked resolved. The tenacity dev dependency addition is a minor, appropriate change to support retry logic in the new test.

[claude]

LGTM — previous concerns resolved: and overload signatures now include TEXT, correctly excludes it.

Extended reasoning...

Overview

The PR adds TEXT as a new score data type throughout the Python SDK. It covers: auto-generated Fern client types (, , , , discriminated union updates), public type aliases in , high-level SDK method overloads in and , a new alias that intentionally excludes TEXT, and a new integration test.

Security risks

None. This is a feature addition to score types with no auth, crypto, or permission changes.

Level of scrutiny

Moderate — the PR touches the public SDK API surface but all changes are mechanical and follow established patterns exactly. The auto-generated Fern client files are noise; the meaningful hand-edited changes (types.py, client.py, span.py, experiment.py) are small and correct.

Other factors

My prior review identified that still had the old and the overloads hardcoded . Both gaps are now fixed in this revision. The inline comment was resolved. The only remaining flag is a nit about module-level assignments in the test file, which is a pre-existing anti-pattern that does not affect production code or this PR's correctness.

[claude]

Previous concerns have been addressed: now includes TEXT, overload signatures updated, and correctly excludes TEXT for experiments. LGTM.

Extended reasoning...

Overview\nThis PR adds TEXT as a new score data type throughout the Python SDK. Changes span the auto-generated Fern API layer (new TextScore/TextScoreV1 models, Score_Text/ScoreV1_Text discriminated union members, enum updates) plus manually maintained files (langfuse/types.py, _client/client.py, _client/span.py, experiment.py).\n\n### Security risks\nNone. This is a purely additive data-type extension with no auth, crypto, or permission changes.\n\n### Level of scrutiny\nMy previous review flagged two gaps (missing TEXT in langfuse/types.py and hardcoded CATEGORICAL-only overloads). Both have been fixed in this revision: types.py now exports ScoreDataType with TEXT, ExperimentScoreType correctly excludes TEXT (since text scores are not supported in experiments), and all overloads/casts use Literal["CATEGORICAL", "TEXT"]. The fix is correct and complete.\n\n### Other factors\nAll inline comments from prior reviews are marked resolved. The new test_create_text_score test uses tenacity retries consistent with how similar tests are structured. No outstanding concerns remain.