Langfuse v4.55.0
Langfuse v4.55.0 introduces zero-vulnerability and FIPS Docker images, Google Cloud Storage export targets, batch processing for POST /scores, and enhanced skill management and topic summarization.
Why this signal matters
Langfuse release v4.55.0 brings major infrastructure, evaluation, and observability features: - Docker & Security: Introduces zero-vulnerability base images, FIPS mode, and builds FIPS images using Iron Bank Alpine. - Storage & Ingestion: Adds Google Cloud Storage export targets (service account key or ADC), improves S3 ingestion resilience with extended retries and 503/Retry-After responses during throttling, and prepares OTel per-key metadata decoding for upcoming SDK majors. - Evals & Scores: Updates POST /scores to support batch processing, adds evaluation support for OpenAI decision models, and generates single evaluator execution records. - Skills & Topics: Enhances the Skills module with local/ZIP file imports, rendered previews, version diffing, and draft recovery. Updates Topics to summarize all trace facets in one call and cache prompt prefixes on Bedrock. - Access Control & API: Resolves API key authorization from SystemRoleAssignments and independently gates project/organization presets. - Fixes: Addresses session navigation double URL encoding, worker batch project scoping, ClickHouse billing usage tracking, and evaluator cyclic result handling.
Actionable summary
Langfuse v4.55.0 adds FIPS-mode Docker containers, GCS export via service account/ADC, batch /scores endpoint support, OpenAI decision model evals, and improved OTel per-key metadata decoding alongside various UI and worker fixes.
- Agent usefulness
- 77/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Upgrade to Langfuse v4.55.0 if utilizing self-hosted Docker deployments, particularly if requiring FIPS compliance or zero-vulnerability base images.
- Verify integration with the POST /scores endpoint if migrating to batch processing.
- Ensure S3 ingestion clients properly handle HTTP 503 with Retry-After headers during throughput spikes.
- Configure Google Cloud Storage export configurations if moving trace exports off AWS S3.