feat(api): update API spec from langfuse/langfuse 7955a3e

[langfuse-bot]

Greptile Summary

Updates the generated API client to expose deprecation metadata returned by legacy endpoints.

• Adds and exports the Deprecation and ObservationsViewSingle response models.
• Adds optional _deprecation metadata to affected score, trace, session, dataset-run, metrics, and paginated response models.
• Updates the legacy single-observation clients to parse and return ObservationsViewSingle.

Confidence Score: 5/5

The PR appears safe to merge with no actionable failures identified in the generated model, parsing, or export changes.

The new response fields are optional and correctly aliased, the single-observation subtype preserves the prior model contract, and the lazy import mappings consistently expose the added types.

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

Context used:

• Knowledge Base — API Client (langfuse/api/)

[github-actions]

@claude review

[claude]

LGTM — mechanical, auto-generated Fern API client update.

Extended reasoning...

Overview

This PR is an auto-generated update of the Fern-generated API client, syncing it with the langfuse/langfuse OpenAPI spec at commit 7955a3e. It adds a new Deprecation commons type and a new ObservationsViewSingle type (a copy of ObservationsView plus an optional deprecation field), and threads an optional _deprecation field (aliased, default None) through several response models: DatasetRunWithItems, Score_* variants (via a new shared Base class), SessionWithTraces, TraceWithFullDetails, PaginatedDatasetRunItems, PaginatedDatasetRuns, MetricsResponse, ObservationsViews, GetScoresResponse, PaginatedSessions, and Traces. The legacy single-observation get endpoint's return type is switched from ObservationsView to ObservationsViewSingle. All __init__.py changes are the standard Fern-generated lazy-import/export wiring for the new types.

Security risks

None. This is purely additive typed-response modeling for API deprecation metadata (message/replacement/docsUrl/sunsetAt strings). No new request paths, no auth/crypto changes, no user input handling changes. All new fields are optional with safe defaults, and models retain extra="allow" so unknown fields don't break parsing.

Level of scrutiny

Low. This is boilerplate generated code following the exact same pattern already used throughout the SDK (optional aliased field with FieldMetadata, frozen pydantic models). The only manually-notable change is the introduction of the shared Base class for the Score_* variants and the ObservationsView -> ObservationsViewSingle return-type swap on the legacy single-get endpoint, both of which are backward compatible (new optional field, and a subclass with the same fields as before).

Other factors

No CODEOWNERS-restricted paths are touched, no design decisions requiring human input, and the change is self-contained to the generated API client with no hand-written logic. Given this is routine spec-sync tooling output, it's safe to shadow-approve.