本页还没有译文
本页 70 段还没译成한국어，下面显示的是英文原文。Versions & Compatibility
还没翻译译自英文（langfuse.com）本页 70 段都还没译
Versioning is key to ensure compatibility between Langfuse Server, SDKs, and custom integrations via the Public API. Thus, we take semantic versioning seriously.
Note
The feature availability matrix below shows what each self-hosted server version supports. For Langfuse Cloud and an overview of current and legacy versions, see Versions & Compatibility.
Scope of semantic versioning
The following changes result in a major version bump as they are considered breaking:
- Infrastructure changes
- Removal of existing Public APIs or removal/changes of existing parameters from Public APIs
The following changes do not result in a major version bump as they are considered internal implementation details:
- Database schemas
- Frontend APIs
Compatibility between Langfuse Server and SDKs
Langfuse Server and SDKs are versioned independently to allow for more flexibility in upgrading components. The compatibility rule: each server major version aims to support the current and the previous SDK major version of each language, and each SDK major requires a minimum server version. We try extremely hard to uphold this rule, but the v4 transition is an exception: it ends support for older SDK majors on a published schedule (see the feature availability matrix).
- Server: Can be upgraded independently of SDK versions within the supported range. Major server upgrades can drop support for old SDK majors; check the feature availability matrix and the upgrade guide before upgrading.
- SDKs: Older SDK majors keep working on newer servers until they are deprecated and removed. New SDK majors require the minimum server versions listed in the feature availability matrix.
We recommend keeping the Langfuse Server up to date to ensure access to all features and security updates.
How Langfuse Cloud is versioned
Langfuse Cloud deploys continuously and always runs the latest Langfuse version. New capabilities are battle-tested on Langfuse Cloud before they ship in a self-hosted release, so Cloud can run ahead of the latest self-hosted version, and some features may be enabled on Cloud before they are available self-hosted.
Consequences:
- On Cloud, server versions are managed for you; only SDK versions and API endpoints matter.
- Breaking removals on Cloud are announced with a migration window and happen on published dates; on self-hosted they only happen in major releases. Cloud removals are tracked in the Langfuse Cloud matrix, self-hosted support in the matrix below.
Feature availability matrix
The matrix below shows what each self-hosted server major version supports: security patches, SDK majors with their minimum server versions, ingestion paths, read APIs, exports, and evaluators. Click a row for details and replacement endpoints.
On Langfuse Cloud, server versions are managed for you; use the Langfuse Cloud matrix instead.
| Client | OSS v2 (End of life) | OSS v3 (Deprecated) | OSS v4 (GA) | Status |
|---|---|---|---|---|
| Server support · Upgrade guide | ||||
| Security patches | No | Through January 31, 2027 | Yes | |
| Python · Upgrade guide | ||||
| Python SDK v5 | Unsupported | Unsupported | ≥ 4.59.0 | GA |
| Python SDK v4 | Unsupported | ≥ 3.63.0 | Full | GA |
| Python SDK v3 | Unsupported | ≥ 3.63.0 | Deprecated | Deprecated |
| Python SDK v2 | Full | Full | Unsupported | Deprecated |
| Python SDK v1 | Full | Unsupported | Unsupported | End of life |
| JS/TS · Upgrade guide | ||||
| JS/TS SDK v6 | Unsupported | Unsupported | ≥ 4.59.0 | GA |
| JS/TS SDK v5 | Unsupported | ≥ 3.63.0 | Full | GA |
| JS/TS SDK v4 | Unsupported | ≥ 3.63.0 | Deprecated | Deprecated |
| JS/TS SDK v3 / v2 | Full | Full | Unsupported | Deprecated |
| JS/TS SDK v1 | Full | Unsupported | Unsupported | End of life |
| Third-party instrumentation · OpenTelemetry docs | ||||
OpenTelemetry/api/public/otel/v1/traces | Unsupported | ≥ 3.22.0 | Full | GA |
Direct scores ingestion/api/public/scores | Full | Full | Full | GA |
SDK scores ingestionscore-create via /api/public/ingestion | Full | Full | Full | GA |
Legacy trace and observation events/api/public/ingestion | Full | Full | Unsupported | Deprecated |
| Read APIs · Public API docs | ||||
Observations API v2 & Metrics API v2/api/public/v2/... | Unsupported | Unsupported | Full | GA |
Scores API v3/api/public/v3/scores | Unsupported | Full | Full | GA |
Deprecated read APIstraces, observations, sessions, scores, metrics, dataset runs | Full | Full | Unsupported | Deprecated |
| Metrics & alerts · Alerts docs | ||||
| Alerts | Unsupported | Unsupported | Full | GA |
| Integrations & exports · Export docs | ||||
| Blob storage export | Unsupported | Traces & observations | Enriched observations | GA |
| PostHog integration | Unsupported | Traces & observations | Enriched observations | GA |
| Mixpanel integration | Unsupported | Traces & observations | Enriched observations | GA |
| Legacy export source (traces and observations) | Unsupported | Full | Deprecated | Deprecated |
| Evaluations · LLM-as-a-judge docs | ||||
| Observation-level evaluators | Unsupported | ≥ 3.153.0 | Full | GA |
| Trace-level evaluators | Full | Full | Deprecated | Deprecated |
Release Notes
Release notes are published on GitHub:
You can watch the GitHub releases to get notified about new releases:
Also, you can subscribe to our mailing list to get notified about new releases and new major versions:
Note
Langfuse OSS updates — get an email when we ship important features and new releases for self-hosted (open source) Langfuse. Self-hosting updates only, no spam.