feat(api): update API spec from langfuse/langfuse 446fe55

[langfuse-bot]

Greptile Summary

This PR syncs the JS SDK's auto-generated API types from the upstream Langfuse server spec (commit 446fe55). No hand-written logic is changed.

• BlobStorageSyncStatus: adds a new "running" status (both union type and const map) to represent an export job that is actively being processed; refines the idle description to clarify it means "no export is queued either".
• CreateBlobStorageIntegrationRequest: tightens the exportStartDate JSDoc to document that the date must not be in the future (with a 27-hour timezone tolerance), matching server-side validation that already existed.

Confidence Score: 5/5

Auto-generated type-only changes; no runtime logic is touched and the const map is complete and consistent with the union type.

Both files are Fern-generated from the upstream API spec. The running status is correctly added to both the union type and the const object, the idle description is clarified, and the exportStartDate comment gains an accuracy improvement. There is nothing here that could introduce a runtime defect in the SDK.

No files require special attention.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Integration Enabled] --> B{Has exported before?}
    B -- No, nothing queued --> C[idle]
    B -- No / Yes, job queued --> D[queued]
    D --> E[running]
    E -- Success --> F[up_to_date]
    E -- Failure --> G[error]
    F -- Next sync overdue --> D
    H[Integration Disabled] --> I[disabled]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Integration Enabled] --> B{Has exported before?}
    B -- No, nothing queued --> C[idle]
    B -- No / Yes, job queued --> D[queued]
    D --> E[running]
    E -- Success --> F[up_to_date]
    E -- Failure --> G[error]
    F -- Next sync overdue --> D
    H[Integration Disabled] --> I[disabled]

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	Jul 3, 2026 8:36am

[github-actions]

@claude review

[claude]

LGTM — auto-generated API spec update adding the 'running' sync status enum value and a doc comment clarification.

Extended reasoning...

Overview

This is an auto-generated PR from the Fern API spec sync bot (commit 446fe55 from langfuse/langfuse). It touches only two auto-generated TypeScript type files under packages/core/src/api/api/resources/blobStorageIntegrations/types/:

• BlobStorageSyncStatus.ts: adds a new running enum value (and updates the docstring describing it).
• CreateBlobStorageIntegrationRequest.ts: appends a documentation note to exportStartDate clarifying the 27h future-date tolerance.

Security risks

None. These are purely type-level additions to auto-generated client SDK code. No runtime logic, auth flow, crypto, or input validation is touched.

Level of scrutiny

Very low. Both files carry the "auto-generated by Fern" header, the changes are additive (new enum member, docstring text), and they match the pattern of other API-spec-sync PRs in this repo (e.g., #847, #844-adjacent). The new Running enum entry preserves the existing const object shape, so no consumers of the type or the const map break.

Other factors

The bug hunter found no issues. The change is mechanical and matches the established auto-generated-spec-update workflow. No CODEOWNERS-sensitive code is touched.