feat(api): update API spec from langfuse/langfuse 632aafa

[langfuse-bot]

Greptile Summary

This PR updates the JSDoc comment on the filter field of GetObservationsV2Request to more accurately describe how the matches operator works, auto-generated from the upstream langfuse/langfuse API spec at commit 632aafa.

• The inline field descriptions for input and output are updated from "accelerated token search" to "accelerated indexed literal search" to better reflect the underlying index semantics.
• The matches operator paragraph is expanded to clarify that it performs "indexed literal search with token-boundary pruning," that % and _ wildcards are treated as literal characters (unlike SQL LIKE), and that contains should be used for legacy substring semantics.

Confidence Score: 5/5

This is a documentation-only change with no runtime code modifications; safe to merge as-is.

Only the JSDoc comment block is changed — no TypeScript types, runtime logic, or exports are modified. The updated wording more precisely describes matches operator semantics (literal vs. token, wildcard handling) and is consistent with the examples already in the comment.

No files require special attention.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Client calls GetObservations v2\nwith filter param"] --> B{Filter column?}
    B -->|input / output| C{Operator?}
    B -->|metadata stringObject| D{Operator?}
    B -->|other columns| E[Standard filter applied]
    C -->|= or matches| F["Indexed literal search\n(token-boundary pruning,\ncase-insensitive)"]
    C -->|contains / starts with\nends with / does not contain| G["Rejected unless\naccompanied by = or matches filter"]
    D -->|matches| H["Indexed literal search\n(case-sensitive,\n% and _ are literal)"]
    D -->|other| I[Standard string filter]
    F --> J[Results returned]
    H --> J
    I --> J
    E --> J

Loading

_{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	May 29, 2026 9:13am

[github-actions]

@claude review

[claude]

Auto-generated API spec update — JSDoc comment only.

Extended reasoning...

Overview

This PR is an auto-generated update to a Fern-generated API spec file. The only changes are to JSDoc comment text within GetObservationsV2Request.ts, updating the description of the matches operator from 'token search' wording to 'indexed literal search with token-boundary pruning' and clarifying that % and _ are treated as literal characters (unlike SQL LIKE).

Security risks

None. No executable code paths, types, or runtime behavior are modified. The changes are purely documentation in a generated TypeScript declaration file.

Level of scrutiny

Minimal scrutiny warranted. This is an auto-generated file (header comment confirms 'auto-generated by Fern from our API Definition') and the diff is comment-only.

Other factors

The PR follows the repo's established pattern for API spec updates from the upstream langfuse/langfuse repository. No tests need to change for documentation-only updates.