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

[langfuse-bot]

Greptile Summary

Updates generated API documentation to move the Langfuse Cloud removal date for unstable evaluator and evaluation-rule endpoints from November 16, 2026 to September 4, 2026.

• Revises deprecation notices across all evaluation-rule operations.
• Revises deprecation notices across all evaluator operations.

Confidence Score: 5/5

The PR appears safe to merge because it only updates deprecation-date documentation and introduces no concrete runtime or build failure.

The changed lines are documentation comments only, and no actionable defect is established by the available repository evidence.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
langfuse-js	Ready	Preview	Aug 27, 2026 5:14pm

[github-actions]

@claude review

[claude]

Looks good — mechanical, generated doc-comment change only.

What was reviewed: confirmed the diff is limited to @ deprecated JSDoc date strings (November 16, 2026 to September 4, 2026) across 5 EvaluationRules and 4 Evaluators client methods; no executable code, types, or method signatures changed. This mirrors an auto-generated API spec sync from upstream langfuse/langfuse.

Extended reasoning...

Overview

The PR is an auto-generated "update API spec" commit touching only two generated client files (EvaluationRules/client/Client.ts and Evaluators/client/Client.ts) under packages/core/src/api/api/resources/unstable/resources/. I ran the diff directly and confirmed every hunk is identical in shape: a single @ deprecated JSDoc line changes the stated Langfuse Cloud removal date from "November 16, 2026" to "September 4, 2026" for the create/list/get/update/delete methods on EvaluationRules and create/list/get/delete on Evaluators. No other text, code, types, or signatures are touched.

Security risks

None. This is a documentation-only change embedded in comments; it has zero runtime effect, does not touch auth, request/response handling, or any executable logic.

Level of scrutiny

Low. The change is mechanical and generated, confined to non-executable comment text, and the diff I inspected exactly matches the PR description's claims. The only judgment call flagged by the earlier analysis — whether shortening the deprecation date is intentional versus an accidental regression — is a content/product decision belonging to the upstream langfuse/langfuse spec, not something this generated-client PR can get wrong in code terms; the client faithfully mirrors whatever date the spec declares.

Other factors

No CODEOWNERS constraints apply, no prior review comments exist to address, and the bug-hunting pass reported no findings. The change is small, self-contained, and follows the established auto-generation pattern for this repo's API client updates, so this is a safe case for approval without requiring further human review.