feat(api): update API spec from langfuse/langfuse 74ded7e

[langfuse-bot]

Greptile Summary

Updates caller-facing deprecation notices for unstable evaluator and evaluation-rule APIs to identify September 4, 2026 as the Langfuse Cloud removal date.

• Applies the revised date consistently across typed and raw clients.
• Keeps synchronous and asynchronous API surfaces aligned.
• Does not change request, response, authentication, or transport behavior.

Confidence Score: 5/5

The PR appears safe to merge because it consistently changes only caller-facing deprecation text.

The revised removal date is aligned across typed, raw, synchronous, and asynchronous unstable evaluator surfaces, with no runtime API behavior or contract implementation changed.

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

[github-actions]

@claude review

[claude]

Looks good, purely a string-literal date change in generated code.

What was reviewed: confirmed via diff that all 36 changed lines are identical deprecation-message string literals inside @ typing_extensions.deprecated(...) decorators across evaluation_rules/client.py, evaluation_rules/raw_client.py, evaluators/client.py, and evaluators/raw_client.py; the only edit is the removal date ("November 16, 2026" to "September 4, 2026"). No function signatures, control flow, or other logic touched.

Extended reasoning...

Overview

This PR is an auto-generated update (bot-authored, "update API spec from langfuse/langfuse") touching four generated API client files under langfuse/api/unstable/. The full diff was inspected directly and confirms the description: every change is a string literal inside a typing_extensions.deprecated(...) decorator, updating the endpoint removal date from "November 16, 2026" to "September 4, 2026" across the create/list/get/update/delete methods (sync and async variants) of the evaluation-rules and evaluators clients.

Security risks

None. This is a warning-message text change with no effect on authentication, authorization, data handling, or request/response logic.

Level of scrutiny

Low. The change is mechanical and generated, confined to deprecation warning strings, with no behavioral impact. This matches the class of changes (config tweaks, generated/version-bump style edits) that warrants approval without requiring deeper human review.

Other factors

No bugs were reported by the bug hunting system, and the manual diff read confirms the scope matches the PR description exactly. No CLAUDE.md conventions apply, and the PR timeline shows no outstanding third-party objections to weigh.